March 27, 2013 at 8:12 am
I'm working in a rather locked down environment, and would rather avoid adding a DB if I can. I'm thinking of using the CheckDB procedure created by Gianluca Sartori[/url] to run a weekly DBCC CheckDB against all DBs on the servers.
Other than the normal "don't use the system DBs for user stuff" is there any potential issues?
Although I am going to check, and see if I can create a DB for these sort of tools, and if so, use that instead.
Thanks,
Jason
March 27, 2013 at 8:15 am
Good idea in my mind, Jason. I generally have a utility database from which those types of things run.
March 27, 2013 at 8:23 am
You can do it. I prefer to avoid master for the reason of having one more database to check for objects when migrating to a different server (for example). But in a pinch, master works.
Another I have sometimes used, when in a pinch, is msdb.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 27, 2013 at 8:37 am
Cool, thanks to both of you!
Jason
March 27, 2013 at 8:52 am
You could easily use master for that. Especially given that you must use master for some procedures anyway. Moreover, it's much easier from SQL2005 on to distinguish your objects from the base system objects, because system objects are owned by 'sys', while yours are owned by 'dbo'.
SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply