Re: SQL password complexity
- From: "Dan Guzman" <guzmanda@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 13 Apr 2006 06:59:01 -0500
In Transact-SQL, a semicolon is an optional *statement* delimiter. This
shouldn't cause problems as long as the value is properly enclosed in
quotes:
EXEC sp_password NULL, 'new;password', 'DevLogin'
You are right that a semicolon can prematurely terminate the statement when
the value isn't properly enclosed in single quotes:
EXEC sp_password NULL, new;password, 'DevLogin'
However, the OP indicated that the password change was successful so the
problem is likely due to confusion in the connection string.
--
Hope this helps.
Dan Guzman
SQL Server MVP
<m.bohse@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1144834023.511273.294970@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
A semicolon in SQL functions as batch separator just like the word GO.
I assume that's what causing the problem for your developers. SQL
server will probably see the password as part of two separate commands.
Markus
.
- Follow-Ups:
- Re: SQL password complexity
- From: Bry
- Re: SQL password complexity
- References:
- SQL password complexity
- From: Bry
- Re: SQL password complexity
- From: m . bohse
- SQL password complexity
- Prev by Date: Re: SQL password complexity
- Next by Date: Re: dbo with user name in "users"
- Previous by thread: Re: SQL password complexity
- Next by thread: Re: SQL password complexity
- Index(es):
Relevant Pages
|