April 1, 2003 at 12:50 pm
I have a standalone, "classic ASP" (not .Net) application that we have recently conveted from an MS Access back end to a SQL Server/MSDE back end. One of the capabilities the Access version had was a "Backup/Restore" feature. This was a simple thing - copy and zip it for backup, unzip and copy over the existing DB for restore. This was often ued to take a DB from one machine to another to quickly get another instance of the app up and running in the case of a new install or when multiple changes were made to a DB. You know the drill.....
Now, however, we have gone to a SQL Server implementation. With SQL Server, backup is not a problem, but I am looking for strategies to perform a restore, either a restore to a brand new instance of SQL Server or to replace an existing copy of the DB. I would also like to somehow be able to do this from within the app - but I dont think that is possible because I am connected to the existing DB thru a COM component when in the app.
Any hints or strategies would be very much appreciated.
basehitter10
April 1, 2003 at 1:21 pm
Don't know much about ASP, but if executing a restore sentence directly is a problem I think you could create a stored procedure with the restore sentence that you need and execute that stored procedure.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply