Comments on: Scheduling Database Backups with SQL Server Express http://www.devtrends.com/index.php/scheduling-database-backups-with-sql-server-express/ developing trends in information technology Fri, 06 Aug 2010 22:32:02 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: aaron http://www.devtrends.com/index.php/scheduling-database-backups-with-sql-server-express/comment-page-1/#comment-236 aaron Tue, 09 Mar 2010 04:50:26 +0000 http://www.devtrends.com/?p=458#comment-236 James, Thank you for the post, I've updated the example to reference [FULL PATH TO SQL BACKUP FILE] instead. The original intent was to delete the .bak file prior to running the script again. -Aaron James,
Thank you for the post, I’ve updated the example to reference [FULL PATH TO SQL BACKUP FILE] instead. The original intent was to delete the .bak file prior to running the script again.
-Aaron

]]> By: James http://www.devtrends.com/index.php/scheduling-database-backups-with-sql-server-express/comment-page-1/#comment-235 James Mon, 08 Mar 2010 15:44:59 +0000 http://www.devtrends.com/?p=458#comment-235 <b>@ECHO OFF del "[FULL PATH TO SQL FILE]" osql -S [SERVER]\[INSTANCE] -U [USERNAME] -P [PASSWORD] -i "[FULL PATH TO SQL FILE]"</b> If you <b>del "[FULL PATH TO SQL FILE]"</b> surely it won't be there when you address it with the next line. Shouldn't it be something more like delete the old backup file then point osql at the script to create the new one? @ECHO OFF
del “[FULL PATH TO SQL FILE]”
osql -S [SERVER]\[INSTANCE] -U [USERNAME] -P [PASSWORD] -i “[FULL PATH TO SQL FILE]“

If you del “[FULL PATH TO SQL FILE]“ surely it won’t be there when you address it with the next line. Shouldn’t it be something more like delete the old backup file then point osql at the script to create the new one?

]]>