What are the challenges you face when working across database platforms? Take the survey

SQL Backup Jobs - Not Running...

sqlsmartiesqlsmartie Posts: 2
edited September 17, 2006 3:13AM in SQL Backup Previous Versions
Our systems have the following configuration:
- SQL Backup 4.6
- SQL Server 2005, Express Edition SP1
- Windows 2003, Standard Edition SP1

We are currently evaluating SQL Backup for use in our environment for full, nightly backups as well as log shipping. The SQL Backup price is very reasonable for the capabilities and features it offers.

In investigating the software we liked the fact that it has a “SQL Backup Agent” – in other words, some type of Windows service that is awake and “doing its thing”. However, the problem that we have run into is the following – it seems as though in order to execute a scheduled job, we need to have Microsoft’s “SQL Server Agent” (not to be confused with Red Gate’s agent) installed. As you can see, with SQL 2005 Express Edition, this is simply not possible.

The following posts seem to point to the fact that Microsoft’s SQL Server Agent is required:
http://www.red-gate.com/messageboard/vi ... php?t=2256
http://www.red-gate.com/MessageBoard/vi ... php?t=3338

This begs the question, what exactly is Red Gate’s SQL Backup Agent doing? The only thing we can think of is that it’s the service under which the backup/compression is performed – rather than being an actual agent which wakes up from time to time in order to perform any potential jobs.

Can you confirm this and, if so, could you offer any potential solutions – short of purchasing SQL Server 2005, Standard Edition?

Thank you.



  • Options
    peteypetey Posts: 2,358 New member
    Yes, SQL Backup's Agent is the application that performs the backup/restore tasks when ran using the extended stored procedure. It is done this way for security reasons (see http://www.red-gate.com/messageboard/viewtopic.php?t=2899).

    If you want to schedule tasks, you could use the Windows Scheduler (on WinXP, it's on Start > Programs > Accessories > System Tools > Scheduled Tasks). You have a choice of using the extended stored procedure or the command line interface (sqlbackupc.exe) of SQL Backup.

    If using the extended stored procedure, you could use either osql or sqlcmd to connect to SQL Server to call the extended stored procedure, or the ADO objects if you choose to use Windows scripting (e.g. http://www.red-gate.com/messageboard/viewtopic.php?t=2938).

    Differences between the extended stored procedure and command line interface:

    - progress of backups/restores ran using the extended stored procedure can be monitored using the sqbstatus extended stored procedure

    - the extended stored procedure provides more information re the outcome of the tasks

    - the command line interface does not require the SQL Backup Agent service to be running

    - you can set up complex scripts using the extended stored procedure

    - when using the command line interface, the user running it must be a member of the SQL Server sysadmin fixed server role. When using the extended stored procedure, the user needs only to have the relevant backup/restore rights. Only the SQL Backup Agent service user needs to be a member of the SQL Server sysadmin fixed server role.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
Sign In or Register to comment.