November 5, 2010 at 5:13 am
Hi
I'm about to implement a few SP and views that I will use for monitoring/managing one of my SQL Server installations. I do not want to place these in one of the user databases, but instead one of the system databases. Which one is it considered to be best practice to generate these kind of things in? MSDB or Master, or any other databases?
/Andy.l
November 5, 2010 at 5:32 am
This was removed by the editor as SPAM
November 5, 2010 at 5:42 am
So I should do it like that, even though the views query the DMV in the systemdatabases?
/Andy.l
November 5, 2010 at 6:01 am
This was removed by the editor as SPAM
November 5, 2010 at 7:29 am
I've done both in the past.
In some organisations we've added a 'SystemDB' which is used for general purpose logging, supplementary backup info, capturing occasional profiler traces etc. For views and procs which extend or combine DMVs, I favour deploying them to the master database. As you mentioned, thats where the base DMVs and other 'system wide' queries reside so its a logical place to store your extended system wide code.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply