April 2, 2009 at 10:25 am
SA (4/2/2009)
Best practices analyzer is usually run when you're ready to go to Production. That will be your baseline.Once you, are in Production, you would need to run it to ensure there have been no changes to the configurations. I usually run it post an application install where the app requires elevated privileges on the database to install. Just another sanity check to ensure no unnecessary changes were made to the environment.
I would use this tool as a starting point and as you get more acquainted with SQL Server you could then write your own health checks or use a third party tool for this as well.
Thanks SA! So let me take this way:
1.) Install the SQL Server.
2.)Perform necessary steps through the SAC manager like assigning a port, protocols
3.) Make sure you turned off all the unnecessary services that you are not willing to use.
4.)Run the logins script
5.)Restore all the User databases
6.)Run the SQL Server best practices analyzer?
and also how do you assign port 1433 is it done by default during the installation?
April 2, 2009 at 10:29 am
1433 is the default port SQL Server is listening on. You could change the port for it to listen to another static port or have it set to dynamically select a port.
Please keep in mind changing the default port will in most cases have implications in the way users / applications connect to your database instance.
You also want to look at the monthly Microsoft Security Bulletins to see if there are any security vulnerabilities that are out there that you may have to patch.
April 2, 2009 at 10:38 am
So, you should manually look at the security bulletins for an update is that waht every DBA does? so lets say they have released a patch for the month and is it compulsary that you ahve to apply all the required patches? Or do you select the patches that you want to apply?
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply