SQLServerCentral / SQL Server Security Skills / Testing Center / database acess / Latest Posts

RE: database acess

Jeff Gray — Fri, 13 Apr 2007 06:44:00 GMT

Shailesh,

Change the sa password on the server. Then give the developers access only to what they need via a different identity. Either a trusted connection via domain security or a different sql user.

RE: database acess

P Jones — Fri, 13 Apr 2007 02:37:00 GMT

As above plus re-consider why you need individual instances on PCs and how on earth you can keep them all patched up to the same standard. Centralised servers are so much easier to maintain.

RE: database acess

Bulent Gucuk — Thu, 12 Apr 2007 13:57:00 GMT

Stop using Sa and implement Windows authentication using Windows Groups or windows accounts. By using groups and group membership there will be less SQL login /user administration.

RE: database acess

Steve Jones - SSC Editor — Thu, 12 Apr 2007 07:41:00 GMT

Stop using saNo other way. Use a limited user, even a standard one, that has rights, like db_owner to particular databases.

database acess

shailesh-425946 — Thu, 12 Apr 2007 00:44:00 GMT

I have multiple databases created in sql2000 and my server is on a network where client machines also has their own sql server instances with databases and we all are using a standard username of "sa" and password :microsoft"

This allows all the users over the network to register each one's sql server on their own local machines and access all databases

Now I want to block certian users from accessing certain databases on my server, kindly anybody help me doing this?