|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Saturday, March 16, 2013 4:03 PM
Points: 14,
Visits: 336
|
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: 2 days ago @ 7:35 AM
Points: 515,
Visits: 1,016
|
|
| Run the performance dashboard reports and have a look at long running queries and missing indexes.
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Tuesday, November 27, 2012 9:47 AM
Points: 1,
Visits: 14
|
|
This is a good check-list - thanks very much.
It sounded like you suggested deliberately causing a problem to get buy-in from your users (...sending out hundreds of thousands of emails). Perhaps I misunderstood this bit. Abusing trust is never a good long-term strategy.
Thanks
J
|
|
|
|
|
UDP Broadcaster
      
Group: General Forum Members
Last Login: Wednesday, January 02, 2013 12:15 PM
Points: 1,443,
Visits: 711
|
|
Most of this looks pretty good but this could be a recipe for disaster:
"Drop obsolete objects"
It's sometimes not straightforward how and when objects are used. before dropping something you need to be sure it's really not used.
It's quite possible you could drop a sproc or table thats only used periodically (once a month or once a quarter). This could create major problems for you a few months out!
Just my 02c... 
Mark
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Wednesday, February 13, 2013 8:52 PM
Points: 20,
Visits: 17
|
|
I am stunned that the list does not include "Run CHECKDB" (or at least find out when it last ran).
The free but unsupported RML Utilities released by the Microsoft SQL Server PSS engineers can be used to analyze a Profiler trace. That can tell you what is running and how often.
This would be a good spot to plug Red-Gate's SQL Doc tool (no, I'm not a RG employee!). This might not be free but it is a good way to acquaint yourself with a new database.
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Today @ 11:07 AM
Points: 3,576,
Visits: 5,117
|
|
1) I agree with Mark about Drop obsolete objects. It is virtually impossible to find and properly scan all code that might run against any given database that might access a particular object. Just don't go there.
2) I fire up ApexSQL Doc first thing and get it going creating a full blow set of documentation about the database.
3) I check quite a few configuration options such as statistics settings, auto-close/auto-shrink, recovery mode, growth increments, etc.
Best,
Kevin G. Boles SQL Server Consultant SQL MVP 2007-2012 TheSQLGuru at GMail
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Tuesday, July 19, 2011 4:53 AM
Points: 299,
Visits: 56
|
|
We never delete anything in one go!!! What we do is change its name by prefixing XXX to its name, and then later delete all the XXX's. As we run a weekly system, we can delete the XXX's for most of our system after a fortnight. For the monthly and quarterly bits, we just wait a bit longer!!!
Rgds,
Steve
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Today @ 11:07 AM
Points: 3,576,
Visits: 5,117
|
|
stevecurtis3 (6/22/2009) We never delete anything in one go!!! What we do is change its name by prefixing XXX to its name, and then later delete all the XXX's. As we run a weekly system, we can delete the XXX's for most of our system after a fortnight. For the monthly and quarterly bits, we just wait a bit longer!!!
Rgds,
Steve
But how can you know that object A is a daily/weekly/monthly/quarterly/yearly/etc object? If this is a database you have no prior knowledge of (heck, even if it is) you run a significant risk IMNSHO.
Best,
Kevin G. Boles SQL Server Consultant SQL MVP 2007-2012 TheSQLGuru at GMail
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Monday, November 19, 2012 1:31 PM
Points: 29,
Visits: 108
|
|
I like this article a lot...just the right number of topics to get someone started on a newly inherited database (or even someone new to DBA work themselves).
In line with other posters who remark about what's missing from the list, I would suggest they post their own "new DB to-do" lists so everyone can get a diverse view of this topic. Also, I'm putting together my own list called "Things to Do When You Inherit Replication"....which brings with it some very specific needs.
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Thursday, April 14, 2011 7:04 AM
Points: 20,
Visits: 177
|
|
| Great list. I would throw in "review security privileges"
|
|
|
|