SQL Server 2008 Administration Best Practice

Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso-para-margin-right:0in; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;}

SQL Server 2008 Administration Best Practice

By : Kasim Wirama, MCDBA, MCITP

 

SQL Server 2008 is the recent version of SQL Server and comprehensive database engine platform. To use it effectively, here are best practice points that are worth to your organization which uses SQL Server 2008. Some points here are applicable to previous version of SQL Server.

·         Use scripting utility on SQL Server Management Studio (SSMS) to transform administration task into transact SQL script.

·         If SQL Server box is dedicated only for database, it’s better to let SQL Server dynamically manages minimum and maximum of memory allocation. If it is not dedicated, it is recommended to specify minimum and maximum memory allocation for SQL Server.

·         Windows authentication provides robust security mechanism so it is preferable than SQL Server authentication.

·         Use change tracking feature to make sure accountability and compliance on your database..

·         Consider to use compression feature to reduce storage utilization.

·         Use SQL auditing feature to capture failed and successful logins.

·         Don’t use automatic database shrink for it will degrade performance and speed up your database fragmentation.

·         Choose and implement correct recovery model for user and system databases. Not all of them needs full recovery model so review this requirement accordingly.

·         Locate database files, transaction log files and operating system files on separate physical volume for performance and availability.

·         Use filegroup for logically grouping database files.

·         Get used to use built-in reports in management studio. Try to create your own report if none of them don’t satisfy your reporting needs.

Automating your tasks using SQL Server Agent. You will get familiar with job and its job steps.
Share this post: | | | |
Published Tuesday, March 17, 2009 1:23 AM by Kasim.Wirama
Filed under:

Comments

No Comments
Powered by Community Server (Commercial Edition), by Telligent Systems