the tough situation for a SQL server DBA

[maswien]

I'm a new DBA, our company have many SQL server installed and have applications running on these servers. When these SQL server get setup, we don't have a DBA yet, Microsoft just make SQL Server looks to easy to play, so any guy may want install it and play it by themself. So now, I'm the DBA, so many SQL Servers have their own security setup and just add me to the sysadmin list, that's it. I'm sure all these need to be changed, like some applications hard coded SA and password, I can't disable this account and can't even change the password, I can't gurantee that only me know the password for the sysadmin, do you guys have any advice for me? thanks, I feel stress.

 

[maswien]

Any idea will be helpful, thanks

 

[SQLBill]

Just document what you find about security issues and provide the documentation in writing to your bosses.

Maybe they can approve/force the changes.

When you document it, don't just say "this is a problem". Say why it's a problem. Provide solutions.

-SQLBill

Posting advice: FAQ481-4875

 

[maswien]

Thank you very much Bill! It's so much pain to take somebody's left over, things will be much easier if plan it in the beginning, now I know how important that a DBA involves in the original database design.