Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
cr8nk
Yak Posting Veteran
77 Posts |
Posted - 2008-11-04 : 17:01:04
|
Hi all,I have a set of administraton related objects (procedures, views and functions) that will assist in performing backups and other maintenance related tasks. My question for the group is: are people putting their own administrative objects into msdb or a seperate database specifically for DBA functions? I only have 5 procedures, 2 views and 2 functions. This could potentially grow as time goes on. I don't want to create a new database for so few objects, but I also don't like muddying up a system database. Does anyone have any sage advice?thanks,Creighton |
|
tfountain
Constraint Violating Yak Guru
491 Posts |
Posted - 2008-11-04 : 17:06:17
|
In short, create your own database. This gives you more flexibility and if MS decides to do something with a system database later you won't need to deal with any possible issues. |
|
|
cr8nk
Yak Posting Veteran
77 Posts |
Posted - 2008-11-04 : 19:00:19
|
I have been leaning that way. Thanks for the input. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
saurabhsrivastava
Posting Yak Master
216 Posts |
Posted - 2008-11-05 : 12:48:03
|
Not only what's said in above post, when you upgrade from one version to another it will be a big hassel. |
|
|
|
|
|