Comments
Sort by recent activity
I found a workaround for this... If anyone is interested..
I changed sql backup to not "auto" name the backup file... It now names it as today.sqb
once it's copied down to the local machine on a folder named "today" - the sql restore runs with the script I created to restore today.sqb in the folder "today".. Then a batch file creates a folder named as the date. the batch file then copies the today.sqb from the "today" folder into this new %date% folder. Then a script runs later to delete the old copy in the today folder. This way the sql restore script can use a static database name but still keep the database up to date with different backups.
This wouldn't really be a problem for anyone (doing the scripts and everything) if they didn't need to keep the backups for a few months back in time like we do.. / comments
I found a workaround for this... If anyone is interested..
I changed sql backup to not "auto" name the backup file... It now names it as today.sqb
once it's copied down to the local machine on a fo...
Thank you - that is what I was afraid of. / comments
Thank you - that is what I was afraid of.