Posted by David Portas on 10/02/06 19:18

crazyone wrote:
> Oh and by the way, the SQL2000 code we use is the following:
>
> exec sp_addlogin N'mynewuser', null, @logindb, @loginlang
>
> PS : @logindb and @loginlang are valid variables that contain correct
> info for this SP to work


Why not just set a sensible password to start with? The same password
for each login if you like (anything must be better than a blank
password). Have you ever had a security audit?

Otherwise I think having two versions of your code may be your only
option.

--
David Portas, SQL Server MVP

Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.

SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--

• Next in forum: Re: Best way to force a varchar column to have no whitespace
• Prev in forum: Urgent requirements ----- Oracle Apps Finance Functional
• Thread view: Re: Blank Password Policy problem

[Reply to this message]