December 20, 2008 at 2:03 am
I have read recommendations / best practices from BooksOnline for some of the topics below, but I am more interested in what is practical and what is actually being implemented in your production environment. Thank you for any comment you can provide in advance. 🙂
-do you delete BUILTIN\Administrator account from SQL? why or why not?
-do you disable sa account from SQL? why or why not?
-do you use maintenance plan? why or why not?
-do you use one service account to run all SQL services on one SQL server?
-do you use third party enterprise SQL backup tools? why or why not?
-do you assign local and sysadmin rights to service account that runs the SQL service? why or why not?
December 22, 2008 at 4:17 am
fan.eddy (12/20/2008)
-do you delete BUILTIN\Administrator account from SQL? why or why not?
Surely I remove the Built\In admins. Why should I give Windows admins sysadmin permission in SQL Server?
fan.eddy (12/20/2008)
-do you disable sa account from SQL? why or why not?
Yes, the sa account should not be used and the best way to insure that is by disabling the account. As second best option I sometimes only rename it.
fan.eddy (12/20/2008)
-do you use maintenance plan? why or why not?
Less and less. Maintenance plans are rather inflexible. By using my own scripts and procedures I can get much better results. For example reindex or reorganize depending on the fragmentation.
fan.eddy (12/20/2008)
-do you use one service account to run all SQL services on one SQL server?
Usually I choose to use one domain account for all services.
fan.eddy (12/20/2008)
-do you use third party enterprise SQL backup tools? why or why not?
It depends. I'm working for different customers all the time and sometimes we use third party tools. It mainly depends on the size of the databases (compression) or special requirements like backup encryption.
[font="Verdana"]Markus Bohse[/font]
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply