master..sqlbackup takes 5 minutes to fail if files missing!
dylanbeattie
Posts: 5 Bronze 1
I'm running the following command, which is one of a whole batch of commands generated by a migration script:
In this case, there's no backup file - Y:SQL-BACKUPDataFULL_(local)_mydb_*.sqb doesn't exist.
The problem is - the job takes five minutes to fail, which makes it quite time-consuming to debug restore batches! Is there some way I can specify a more aggressive timeout? I'm restoring files from local SSD storage so not concerned about network latency or anything.
Thanks,
-D-
EXECUTE master..sqlbackup '-SQL "RESTORE DATABASE [mydb] FROM DISK = ''Y:SQL-BACKUPDataFULL_(local)_mydb_*.sqb'' WITH REPLACE, PASSWORD = ''*****'', RECOVERY, MOVE ''mydb'' TO ''E:Program FilesMicrosoft SQL ServerMSSQL10_50.MSSQLSERVERMSSQLDatamydb.MDF'', MOVE ''mydb_log'' TO ''E:Program FilesMicrosoft SQL ServerMSSQL10_50.MSSQLSERVERMSSQLDatamydb_log.LDF''"'
In this case, there's no backup file - Y:SQL-BACKUPDataFULL_(local)_mydb_*.sqb doesn't exist.
The problem is - the job takes five minutes to fail, which makes it quite time-consuming to debug restore batches! Is there some way I can specify a more aggressive timeout? I'm restoring files from local SSD storage so not concerned about network latency or anything.
Thanks,
-D-
Comments
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8