Hello. I bring home the bacon in a team of 4 dba's. In order to save passing sa passwordsaround I'm going to add a Windows assort on each server and add this groupinto SQL Server as a memeber SysAdmin role. I can also add the serviceaccount into this role (we use the same service account for the server andthe server agent - is this bad?). If I still want to store the sa password who is best to do that or should Inot reach just set it to a different strong password on a regular basis andforget it since I'm not goin gto use it. How about storing othe rlogin \paswords?ThanksAdam
I did what you suggested as a matter of cover... I would just as soon thatthe other sysadmin's login with their Windows Authority and explain to themthere is no difference between logging in as a system admin or using the sapassword. If they have the sysadmin status what difference does it alter whether theyknow the sa password or not? I'd actually like to hear your take on this asI am struggling with it myself. Why should the sa password be known byanyone other than myself and perhaps the network administrator or my directsuperior? I haven't found a really GOOD reason yet but there are lots of"what if's" to claim with.--Regards,Jamie"Adam Sankey" wrote:
> Hello. I work in a team of 4 dba's. In request to save passing sa passwords> around I'm going to add a Windows group on each server and add this group> into SQL Server as a memeber SysAdmin role. I can also add the function> be into this role (we use the same service be for the server and> the server agent - is this bad?).>> If I still want to store the sa password who is best to do that or should I> not reach just set it to a different strong password on a regular basis and> forget it since I'm not goin gto use it. How about storing othe rlogin \> paswords?>> Thanks> Adam
Hi Jamie. I was change surface thinking that I might not store the sa password at all. Just set it to a strong password and then drop about it since everyone isusing windows authentication or a different sql login to acces the server. Atthe moment I'm storing the password on my pc in an encrypted password safethat only I undergo the pass key. Adam"thejamie" wrote:
> I did what you suggested as a be of cover... I would just as soon that> the other sysadmin's login with their Windows Authority and explain to them> there is no difference between logging in as a system admin or using the sa> password.>> If they have the sysadmin status what difference does it alter whether they> know the sa password or not? I'd actually like to hear your take on this as> I am struggling with it myself. Why should the sa password be known by> anyone other than myself and perhaps the network administrator or my direct> superior? I haven't found a really GOOD reason yet but there are lots of> "what if's" to contend with.> --> Regards,> Jamie>>> "Adam Sankey" wrote:>
> > Hello. I bring home the bacon in a team of 4 dba's. In order to save passing sa passwords> > around I'm going to add a Windows group on each server and add this assort> > into SQL Server as a memeber SysAdmin role. I can also add the service> > account into this role (we use the same service account for the server and> > the server agent - is this bad?).> >> > If I still be to store the sa password who is best to do that or should I> > not reach just set it to a different strong password on a regular basis and> > forget it since I'm not goin gto use it. How about storing othe rlogin \> > paswords?> >> > Thanks> > Adam
Forex Groups - Tips on Trading
Related article:
http://www.techtalkz.com/microsoft-sql-server/171650-storing-password.html
comments | Add comment | Report as Spam
|