Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

ADMIN Database Expand / Collapse
Author
Message
Posted Tuesday, November 04, 2008 11:40 PM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Thursday, April 17, 2014 11:45 PM
Points: 582, Visits: 1,975
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
Post #597113
Posted Thursday, November 06, 2008 7:16 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 1:46 PM
Points: 5,849, Visits: 12,585
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.


---------------------------------------------------------------------

Post #598100
Posted Thursday, November 06, 2008 7:51 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Friday, March 14, 2014 3:15 PM
Points: 804, Visits: 935
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."
Post #598152
Posted Thursday, November 06, 2008 8:03 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Saturday, April 12, 2014 11:40 AM
Points: 2,795, Visits: 8,297
I do backups daily ....... better safe than sorry.


Post #598171
Posted Thursday, November 06, 2008 11:49 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, April 15, 2014 6:00 PM
Points: 141, Visits: 291
I agree, set it for simple

The more you are prepared, the less you need it.
Post #598428
Posted Thursday, November 06, 2008 11:52 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Saturday, April 12, 2014 11:40 AM
Points: 2,795, Visits: 8,297
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.


Post #598433
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse