I have to install RedGate's SQLAgent on a production machine that can not have any downtime unless it is scheduled. Does installation of SqlAgent ever cause SQLServer to be restarted? or server reboots?

thanks,
jasen
jasenf
0

Comments

3 comments

  • petey
    By RedGate's SQLAgent, I assume you are referring to the SQL Backup Agent service.

    No, you never need to restart the SQL Server service, nor reboot Windows, when you install the SQL Backup Agent. Neither do you need to restart SQL Server nor reboot Windows during an upgrade of the SQL Backup Agent service.

    However, you may need to restart the SQL Server service when upgrading the SQL Backup extended stored procedure library. This happens when the SQL Server process does not release the library correctly, thus locking the file and preventing it from being overwritten. This is a common occurrence if you are running SQL Server 2000, and is rare on SQL Server 2005 or 2008.

    Note that so far, then has been minimal changes to the stored procedure library for the same major version releases e.g. 6.0, 6.1, 6.2, 6.3. All or most of the changes are in the SQL Backup Agent and also the GUI.
    petey
    0
  • jasenf
    Thanks for the quick reply!! Is there anyway to know if SQL has a lock on these extended sp.'s??
    jasenf
    0
  • petey
    Is there anyway to know if SQL has a lock on these extended sp.'s??
    To really know, try to replace the extended stored procedure library file (xp_sqlbackup.dll) in the SQL Server Binn folder, after running DBCC xp_sqlbackup(FREE).
    petey
    0

Add comment

Please sign in to leave a comment.