November 4, 2008 at 11:40 pm
Hi,
Most dba's use the admin database to keep their backup,restore and maintenance scripts instead of master database. So Iwould like to create a admin database. Could you plz suggest me how this database should be created relating to sysdatabases and user databases.
Thanks
November 6, 2008 at 7:16 am
its certainly a good idea to have a database for your own use to store your code in and any data you might use as a part of your day to day maintenance activities.
create and treat it like any other user database though I would suggest the only maintenance needed on it is backups and simple recovery mode should suffice.
---------------------------------------------------------------------
November 6, 2008 at 7:51 am
Include all the stored procs that you would use in the maintenance jobs and the once with notification too. Simple recovery would be enough and if you don't update it very often then a weekly backup would do.
Use this database as reference for all the jobs that you use for maintenance purpose.
Thanks!!
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
November 6, 2008 at 8:03 am
I do backups daily ....... better safe than sorry.
November 6, 2008 at 11:49 am
I agree, set it for simple
The more you are prepared, the less you need it.
November 6, 2008 at 11:52 am
But if you're doing a lot of work in the database, either go FULL with T-log backups like a Production DB, or do more frequent FULLs while the work is going on. Just like any other DB, decide how much work you can offord to lose.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply