sql server 2000 security polocies implementation

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

General SQL Server Forums

New to SQL Server Administration

sql server 2000 security polocies implementation

Author

Topic

sunsanvin
Master Smack Fu Yak Hacker

1274 Posts

Posted - 2011-06-28 : 09:11:53

Hi Experts,
i know we can not do security polocies in sql server 2000, but i heard that it is possible through some scripts. can you please look with the below requirement and help me in this

We have a requirement in SQL server 2000 and is as follows:

1) Password should be of minimum of 14 character length.
2) Password should contain alphanumeric characters.
3) Password should get locked for 3 wrong attempts.
4) Password should get expired for every 120 days.

Can you please provide us the scripts to acieve this

Arnav
Even you learn 1%, Learn it with 100% confidence.

sunsanvin
Master Smack Fu Yak Hacker

1274 Posts

Posted - 2011-06-28 : 17:29:15

Experts,
kindly provide me solution for this. your gudance is most helpful

Arnav
Even you learn 1%, Learn it with 100% confidence.

robvolk
Most Valuable Yak

15732 Posts

Posted - 2011-06-28 : 17:55:00

SQL Server 2000 doesn't support any of the things you mentioned, unless you only use Windows Authentication. Then you could have a Windows policy to enforce them. SQL logins however can't be enforced in that manner. You'll have to upgrade to at least SQL 2005 in order to do that.

sunsanvin
Master Smack Fu Yak Hacker

1274 Posts

Posted - 2011-06-28 : 18:12:43

Thanks Robvolk for the reply,
can you please provide me some links to support that? client is arguing that with some scripts, it is possible. kindly provide me some links to support this.

Arnav
Even you learn 1%, Learn it with 100% confidence.

robvolk
Most Valuable Yak

15732 Posts

Posted - 2011-06-29 : 00:00:13

I don't have any links besides this one:

http://msdn.microsoft.com/en-us/library/ms161959(v=SQL.90).aspx

Your client is confused. They are probably thinking of SQL 2005 when security policies were introduced. They're free to argue it's possible to do in SQL 2000, let them demonstrate it first. IMHO it's easier and faster to simply upgrade the SQL version, especially considering that SQL 2000 is no longer supported by Microsoft.

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources