SQL Backup 10 - extra bits

RichardMGreen

Hi all

We're just testing SQL Backup 10 after years of using a home-grown backup routine.
The new tool seems better but.....
Our homegrown routine does some things that SQL Backup doesn't seem to (unless I'm missing something.

What we need it to do is:-
concurrent backups (multiple databases at a time)
Rebuild/reorganise indexes (based on amount of fragmentation and number of pages)
Update statistics

Is the above list possible?

On the good news side, SQL Backup is faster and uses less disk space (our sweet-spot seems to be compression level 3 for speed/disk space).

Regards

Richard

Eddie D

Hi,
Thank you for your forum post.

Sadly SQL Backup will not perform the following:

• Rebuild/reorganise indexes (based on amount of fragmentation and number of pages)
• Update statistics

For concurrent backups, you will need to create the jobs individually to run concurrent backups.

For example, you have 10 databases that you wish to backup.  You can create:

• Single job that will backup all 10 databases, but this will backup each database in turn.
• Create two jobs, where each job backs up 5 databases meaning that you will have two databases at a time backing up at a time.
• Or create further backup jobs where the 10 databases are split across all the jobs created.
• Finally create 10 jobs, 1 per database. 

The only thing you will need to be aware off is the amount of free continuous memory available in SQL Server's mem-to-leave memory space, which is used by SQL Server to execute Extended Stored Procedure tasks.  SQL Backup when performing backup and restore tasks, is executing Extended Stored Procedures.

Whilst SQL server has greatly improved the management of the mem-to-leave area in SQL Server 2012 and later versions, it backup or restore task will require continuous block of free memory space, which can become exhausted.

Many Thanks
Eddie

RichardMGreen

Thanks @Eddie D