How can we help you today? How can we help you today?
bbaker

Activity overview

Latest activity by bbaker

Currently we have seven SQL maintenance plans with 20-30 databases in each plan. Maintenance Plan 1 runs in Monday and does a full backup, Plan 2 runs on Tuesday and does a full backup, Plan 3 runs on Wednesday etc. Then every day we do incremental backups for all 7 plans. The reason for breaking up the backups so much is to limit the amount of time that the database backups run. I.E. We don't want a database backup consuming all the server resources for hours and hours at a time (even if it is during less busy hours). As an application service provider, our customers access our systems all hours of the day (and night) thus any prolonged hit in performance has to be kept to a minimum. Based on what you said below about the syntax it sounds like we would still be manually writing and maintaining 7 different backup queries per server. So for instance BACKUP DATABASES [database1,database 2,.....database20] TO DISK BACKUP DATABASES [database21,database 22,.....database40] TO DISK BACKUP DATABASES [database41,database 42,.....database60] TO DISK Think about how painful maintaining database lists would become using this approach. To make things even more painful, our databases have a naming convention: customer#_X_shortname. (For example A0001_S_redgate) Try typing 200 of those without making a mistake! It would take forever to get them all typed in. I suppose we could somehow export a list of names, reformat it, and break it up but it’s still going to be a major headache to maintain. On the other hand if you have a GUI with a list of databases with checkboxes it becomes much easier. So for instance: [X] A0001_S_redgate [X] A0001_T_redgate [X] A0002_S_microsoft [ ] A0002_T_microsot [X] A0003_S_netscape [X] A0003_T_netscape [X] A0004_S_sun [X] A0004_T_sun You can quickly tell in the list above that A0002_T_microsoft is not being backed up. And it’s super easy to just go through and add or remove databases. That’s what we are looking for not some clumsy hand written stored procedure. / comments
Currently we have seven SQL maintenance plans with 20-30 databases in each plan. Maintenance Plan 1 runs in Monday and does a full backup, Plan 2 runs on Tuesday and does a full backup, Plan 3 runs...
0 votes
Easy Multiple Database Backups
This really seems like a great solid product but I am baffled by the lack of easy multiple database backups. From what I gather it’s possible to backup multiple databases using a specialized stor...
3 followers 10 comments 0 votes