Re: Not using SA - Then what?
From: lindawie (lindawie@my-deja.com)
Date: 05/31/02
- Next message: Gary: "SQL Server 7.0 in a Windows 2000 domain"
- Previous message: Sue Hoegemeier: "Re: Not using SA - Then what?"
- In reply to: Chris Beardsley: "Not using SA - Then what?"
- Next in thread: Chris Beardsley: "Re: Not using SA - Then what?"
- Reply: Chris Beardsley: "Re: Not using SA - Then what?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "lindawie" <lindawie@my-deja.com> Date: Fri, 31 May 2002 08:35:09 -0700
Chris,
> I have read that people should not be using SA for anything. How then
> do I have multiple developers/managers login to enterprise manager
> etc but have all the objects owned by dbo (we each have diff NT
> logins)? If SA is stored in clear text in some situations, wouldn't
> all uid/pswrd combo's appear in clear text?
>
> We have wrestled with people making and therefore owning objects, and
> causing headaches in the past...
Change the SA password and don't give it to anyone.
You can add developers to the db_owner role and use Windows
authentication.
Any objects they create will be owned by dbo.
A much better approach is to have developers write scripts to create all
objects and then you execute the scripts either in Query Analyzer or
in batch using osql.
Linda
- Next message: Gary: "SQL Server 7.0 in a Windows 2000 domain"
- Previous message: Sue Hoegemeier: "Re: Not using SA - Then what?"
- In reply to: Chris Beardsley: "Not using SA - Then what?"
- Next in thread: Chris Beardsley: "Re: Not using SA - Then what?"
- Reply: Chris Beardsley: "Re: Not using SA - Then what?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
