Restoring From a Local Backup

I have been developing my app using ASP.Net 3.5, Visual Studio 2008 and SQL Server 2005 on my home computer. I am now ready to "go live". I have created a backup of my local database and would like to restore it to discountasp.net's database server. I know from previous backup/restore experience that SSMS is pretty picky about the location of the MDF and LDF files prior to backup/restore. If you have a comprehensive description of how to successfully "publish" an updated copy of a local database to discountasp.net using backup/restore and SSMS please reply and tell me your procedure.

Thanks,

 

I just noticed that "restore database" in SSMS fails instantly.

Well, we have a "restore database" from a .bak file tool on our control panels. We also have an "attach database" tool for use with MDF files. Will either of these work with files I can create on my local SQL Server instance?

 

Hi,
I use the DASP backup and retore features alot, for several years now.
Have not however tried to use it from a local backup...
I don't even know if the format is the same, but Support will be able to tell you.
Salute,
Mark

 

OK, I will ask support. Once I figure it out I will report back here.

 

So, the answer is simple:

1. Create a backup in SSMS.
2. Upload the .bak file to your webspace via FTP.
3. Use the "restore database" tool in your control panel and point it to the .bak file.

Easy Peasy!!

 

Very cool, I had hoped a local BU would work but never tested it.

 

Hi,
Contact Support from your Control Panel.
I'm 99% certain that they are not going to allow usaccess to the SQL Server boxes files.
There are several methods you can use however. (Taken Support gives you this same response.)

1. Create scripts for your data and objects, then execute them on the remote SQL DB.
2. Use the Import/Export wizards in SSMS.
3. Export your data locally to an Express DB, the use the Attach DB feature on-line in your Control Panel.

Note: If you use the Import/Export wizard try to check the additional features like "Optimize for many rows".
Salute,
Mark

 

Verified that it's working great. Now, if only they would support the "incremental backup" option so that it didn't completely wipe out the database but instead only applied updates I make in my dev environment. I suspect I will need to use scripts for this once the site is officially "launched" so as not to obliterate accumulated data. If someone could submit this as a feature request / bug report that would be sweet.

 

We'll see how successful my site is first before I invest in any tools like that!