In architecting a database server system , an important aspect is the assumption of a 24 x 7 database server environment .
The 24 x 7 model is becoming more prevalent – not only in ecommerce , but also in 9-5 businesses – who require access to database servers throughout the 24 hr period – to deal with ETL , reconciliation and a full range of summarisation\pruning tasks
It is becoming difficult to define the traditional maintenance window .
Some areas in which online utilities are now defined. And should be considered in managing a 24 x 7 (or close as possible) system
a)Statistics optimisation – whether commited as a regular job or as AUTO UPDATE
b)Index Reorganisation and Creating Indexes – regular maintenance and requests from developers to create\adjust indexes
c)Backups
d)Bulk Loading -
e)Monitoring/Tuning/Resource Management – queries consume resources. Use tools to identify inefficient queries. Various methods are available in SQL server – consider Profiler, DMV
Source:Jack Vamvas (http://www.sqlserver-dba.com)This is only a preview. Your comment has not yet been posted.
As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.
Having trouble reading this image? View an alternate.
Posted by: |