Software

Ask something
Discussion Locked

SQL 2000 Security - Good or Bad

0 helpful
2 replies

by len_v

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I worked for 3 yrs happily on SQL7. Now on SQl 2K I have to deal with major issues relating to database security and User security. The Jobs I schedule to run fail because of insufficient permissions, and the admins are francit. They cannot cope with the chaos in User access permissions. All this fuss about security makes me wonder - is it a weakness in SQL 2K, rather than a strength? Could this become the big flaw in SQL 2K, rather than the big advantage? How can we resolve this? SQL is setup to allow mainly Windows 2K Logins. Should we rather use SQL Login security to avoid the chaos?

Where do we go from here to find a solution?

Len

2 replies

by tlbroadbent2

The security model didn't change drastically between SQL 7 and SQL 2000. I don't understand why admins would be frantic and jobs would be failing. We recently converted and encountered no such problems.

Did the admins implement a different security policy or upgrade improperly? Were permissions changed? Did the admins change the account that SQL Agent runs under? Changes like this may account for the difficulties you have experienced. I don't believe there was any change in SQL Server that would cause these problems.

Terry

by rgreene

I went directly to SQL Server 2000, with experience in Oracle, SQLBase, Access and several other desktop databases. The security seems comprehensive and well designed.

To keep things manageable, create database roles for granting/denying rights,then drop users or groups into those roles. The users can be either Windows users (if you are in a 2000 domain) or SQL Server users.

Regarding your application logons not working since converting from 7, they may be attempting to use Integrated Security (SPPI - the technology behind single logon in Win2k Server domains). In other words they may be attempting to connect with the user's Windows user/pwd even though you supplied a SQL user/pwd in the connect string. How are the application connections being made? Try to debug from this angle...

This discussion is closed to new replies.