Getting example database setup - password problem

Question

Getting example database setup - password problem

DataAnalyst110

Ten Centuries

Points: 1361
More actions
April 18, 2012 at 8:00 am

#392054

I recently purchased this:
http://www.mhprofessional.com/product.php?isbn=0071548084
I'm trying to get the example database setup for running the test examples. However, I'm running into this:
Msg 15116, Level 16, State 1, Line 1
Password validation failed. The password does not meet Windows policy requirements because it is too short.
Being so new to all of this, I'm not sure which password it's talking about. Our infrastructure folks brought up a new test server for me to install this on. I used my domain credentials in the configuration manager. Below is the script. Any thoughts on how or where I could fix this? Thanks again for the newbie help 🙂
/****** Object: Database Galactic Script Date: 5/23/2004 11:18:21 AM ******/
CREATE DATABASE [Galactic]
GO
exec sp_dboption N'Galactic', N'autoclose', N'false'
GO
exec sp_dboption N'Galactic', N'bulkcopy', N'false'
GO
exec sp_dboption N'Galactic', N'trunc. log', N'true'
GO
exec sp_dboption N'Galactic', N'torn page detection', N'true'
GO
exec sp_dboption N'Galactic', N'read only', N'false'
GO
exec sp_dboption N'Galactic', N'dbo use', N'false'
GO
exec sp_dboption N'Galactic', N'single', N'false'
GO
exec sp_dboption N'Galactic', N'autoshrink', N'false'
GO
exec sp_dboption N'Galactic', N'ANSI null default', N'false'
GO
exec sp_dboption N'Galactic', N'recursive triggers', N'false'
GO
exec sp_dboption N'Galactic', N'ANSI nulls', N'false'
GO
exec sp_dboption N'Galactic', N'concat null yields null', N'false'
GO
exec sp_dboption N'Galactic', N'cursor close on commit', N'false'
GO
exec sp_dboption N'Galactic', N'default to local cursor', N'false'
GO
exec sp_dboption N'Galactic', N'quoted identifier', N'false'
GO
exec sp_dboption N'Galactic', N'ANSI warnings', N'false'
GO
exec sp_dboption N'Galactic', N'auto create statistics', N'true'
GO
exec sp_dboption N'Galactic', N'auto update statistics', N'true'
GO
if( ( (@@microsoftversion / power(2, 24) = 8) and (@@microsoftversion & 0xffff >= 724) ) or ( (@@microsoftversion / power(2, 24) = 7) and (@@microsoftversion & 0xffff >= 1082) ) )
exec sp_dboption N'Galactic', N'db chaining', N'false'
GO
use [Galactic]
GO
SET NOCOUNT ON
/****** Object: Login GalacticReporting Script Date: 5/23/2004 11:18:21 AM ******/
if not exists (select * from master.dbo.syslogins where loginname = N'GalacticReporting')
BEGIN
declare @logindb nvarchar(132), @loginlang nvarchar(132) select @logindb = N'Galactic', @loginlang = N'us_english'
if @logindb is null or not exists (select * from master.dbo.sysdatabases where name = @logindb)
select @logindb = N'master'
if @loginlang is null or (not exists (select * from master.dbo.syslanguages where name = @loginlang) and @loginlang <> N'us_english')
select @loginlang = @@language
exec sp_addlogin N'GalacticReporting', N'gds', @logindb, @loginlang
END
GO

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Jared SSC Guru Points: 61793 More actions · Answer 1

Not knowing the product, I am guessing it is trying to script a user and the password it is creating does not meet your requirements. You may want to call the vendor of that app.

Jared
CE - Microsoft

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 2

DataAnalyst110 (4/18/2012)
/****** Object: Login GalacticReporting Script Date: 5/23/2004 11:18:21 AM ******/
if not exists (select * from master.dbo.syslogins where loginname = N'GalacticReporting')
BEGIN
declare @logindb nvarchar(132), @loginlang nvarchar(132) select @logindb = N'Galactic', @loginlang = N'us_english'
if @logindb is null or not exists (select * from master.dbo.sysdatabases where name = @logindb)
select @logindb = N'master'
if @loginlang is null or (not exists (select * from master.dbo.syslanguages where name = @loginlang) and @loginlang <> N'us_english')
select @loginlang = @@language
exec sp_addlogin N'GalacticReporting', N'gds', @logindb, @loginlang
END
GO

The bold is the line it's complaining about. That sets the password to 'gds', which does not match windows complexity requirements. You can either rewrite that as a CREATE LOGIN statement that sets pasword policy off or, what may be easier, use a more complex password not 'gds'. 8 characters, upper and lowercase, at least one number or non-alphanumeric character

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

DataAnalyst110 Ten Centuries Points: 1361 More actions · Answer 3

GilaMonster (4/18/2012)
DataAnalyst110 (4/18/2012)
/****** Object: Login GalacticReporting Script Date: 5/23/2004 11:18:21 AM ******/
if not exists (select * from master.dbo.syslogins where loginname = N'GalacticReporting')
BEGIN
declare @logindb nvarchar(132), @loginlang nvarchar(132) select @logindb = N'Galactic', @loginlang = N'us_english'
if @logindb is null or not exists (select * from master.dbo.sysdatabases where name = @logindb)
select @logindb = N'master'
if @loginlang is null or (not exists (select * from master.dbo.syslanguages where name = @loginlang) and @loginlang <> N'us_english')
select @loginlang = @@language
exec sp_addlogin N'GalacticReporting', N'gds', @logindb, @loginlang
END
GO
The bold is the line it's complaining about. That sets the password to 'gds', which does not match windows complexity requirements. You can either rewrite that as a CREATE LOGIN statement that sets pasword policy off or, what may be easier, use a more complex password not 'gds'. 8 characters, upper and lowercase, at least one number or non-alphanumeric character

That got it! Thanks so much. Does the bolded line basically mean create login 'GalacticReporting' with a password of 'gds' (which I've changed per your suggestion) and assign them to the following variables (@logindb, @loginlang)? That last part is the area I'm fuzzy on. Either way, thanks again. The script completed.

Jared SSC Guru Points: 61793 More actions · Answer 4

Take a look here at the sp_addlogin stored proc. It shows you the parameters.

Jared
CE - Microsoft

Grant Fritchey SSC Guru Points: 398890 More actions · Answer 5

GilaMonster (4/18/2012)
DataAnalyst110 (4/18/2012)
/****** Object: Login GalacticReporting Script Date: 5/23/2004 11:18:21 AM ******/
if not exists (select * from master.dbo.syslogins where loginname = N'GalacticReporting')
BEGIN
declare @logindb nvarchar(132), @loginlang nvarchar(132) select @logindb = N'Galactic', @loginlang = N'us_english'
if @logindb is null or not exists (select * from master.dbo.sysdatabases where name = @logindb)
select @logindb = N'master'
if @loginlang is null or (not exists (select * from master.dbo.syslanguages where name = @loginlang) and @loginlang <> N'us_english')
select @loginlang = @@language
exec sp_addlogin N'GalacticReporting', N'gds', @logindb, @loginlang
END
GO
The bold is the line it's complaining about. That sets the password to 'gds', which does not match windows complexity requirements. You can either rewrite that as a CREATE LOGIN statement that sets pasword policy off or, what may be easier, use a more complex password not 'gds'. 8 characters, upper and lowercase, at least one number or non-alphanumeric character

No, if you look a little higher in the code you can see those varaibles being declared and set, just below the BEGIN line.

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning

DataAnalyst110 Ten Centuries Points: 1361 More actions · Answer 6

SQLKnowItAll (4/18/2012)
Take a look here at the sp_addlogin stored proc. It shows you the parameters.

Thanks Jared. That's helpful.

DataAnalyst110 Ten Centuries Points: 1361 More actions · Answer 7

Grant Fritchey (4/18/2012)
GilaMonster (4/18/2012)
DataAnalyst110 (4/18/2012)
/****** Object: Login GalacticReporting Script Date: 5/23/2004 11:18:21 AM ******/
if not exists (select * from master.dbo.syslogins where loginname = N'GalacticReporting')
BEGIN
declare @logindb nvarchar(132), @loginlang nvarchar(132) select @logindb = N'Galactic', @loginlang = N'us_english'
if @logindb is null or not exists (select * from master.dbo.sysdatabases where name = @logindb)
select @logindb = N'master'
if @loginlang is null or (not exists (select * from master.dbo.syslanguages where name = @loginlang) and @loginlang <> N'us_english')
select @loginlang = @@language
exec sp_addlogin N'GalacticReporting', N'gds', @logindb, @loginlang
END
GO
The bold is the line it's complaining about. That sets the password to 'gds', which does not match windows complexity requirements. You can either rewrite that as a CREATE LOGIN statement that sets pasword policy off or, what may be easier, use a more complex password not 'gds'. 8 characters, upper and lowercase, at least one number or non-alphanumeric character
No, if you look a little higher in the code you can see those varaibles being declared and set, just below the BEGIN line.

Oh, o.k. I see it now. Sometimes it feels like I'll never get the hang of this. Thanks to all for your patience!