September 25, 2013 at 5:20 am
Hi,
I have a SQL Server event alert that fires after a database restore using error ID 18267. This works fine when using a local path, but not if a UNC path is specified in the script. Has anybody out there come across this before? I need to track restore activity and fire a SQL Agent job after each successful restore.
I've trawled and the only error ids I can see related to successful restore are:
4356 - Restore is complete on database '%ls'. The database is now available.
18267 - Database was restored: Database: %s, creation date(time): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). Informational message. No user action required.
18268 - Log was restored. Database: %s, creation date(time): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message. No user action is required.
18269 - Database file was restored. Database: %s, creation date(time): %s(%s), file list: (%s), number of dump devices: %d, device information: (%s). This is an informational message. No user action is required.
None of these fire when restoring from UNC path.
Thanks,
Chris
September 25, 2013 at 6:18 am
Update: It appears that something has broken my alerts. Drop and create them and all works fine...
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply