December 16, 2013 at 3:41 pm
I have instructed our DBAs to create standard SQL Server maintenance plans for all our SQL Servers using the Maintenance Plan Designer.
Check DB Integrity
Rebuild Indexs
Maintenance Cleanup
History Cleanup
They are concerned that some of the SQL Servers in our environment that act as a backend to third party applications may already have built in maintenance within the application itself.
Is this a legit concern? If so, would it matter?
December 16, 2013 at 4:15 pm
It's certainly possible, and yes, it would matter. For example, you may have an application that knows it has issues with statistics, so as part of the install it creates a statistics maintenance routine to do UPDATE STATISTICS FULL SCAN on a regular basis. Then, you guys run your maintenance routine through the wizard, which almost definitely will do a sampled scan of the statistics, taking the good set of statistics created by the third party product and making them less good.
A standardized approach to maintenance is fine, but you need to allow for deviations as necessitated by the different hardware and software you're running.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 16, 2013 at 4:19 pm
Edit --
Some vendors provide the custom maintenance for thier applications , if not the In--house DBA should implement the maintenance and check with Vendor to see if there is any issues with the maintenance created by in-house DBA.
The point is to all databases should have maintenance performed.
I used to have bunch of third party apps in our environment but only few of them have custom maintenance from the app side. the best way is to check with app team or vendor to see what are maintenances being perfomed from the app side and rest can be done on the dB side.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply