Reputation: 4371
I'll start by saying that I'm fairly new to the idea of deploying applications to the cloud, but I recently downloaded the Azure SDK and wanted to build a sample application to get myself up-to-speed. Here's what I did.
Everything seems to work just fine when I am in debug mode locally--I can create users, log in, and click around. When I deploy my solution, though, I feel like the database is not getting deployed. I understand that SQL Azure works differently from SQL Express, so I have a few questions.
One thing that struck me while I was searching for a solution is that there is not a wealth of good documentation for Azure--all of the tutorials I found are old or targeted at betas. Help!
Edit: The ideal solution to me does not involve opening SQL Server Management Studio to export my schema/data scripts every time I want to deploy. Surely there is a better way than this?
Upvotes: 1
Views: 535
Reputation: 15850
I highly recommend you develop under local SQL server and deploy your changes to Azure via Red Gate tools: v9 beta of the SQL Compare and Data Compare. They are "most excellent" in this regard.
Also, keep an eye on this free tool: http://www.microsoft.com/en-us/sqlazure/datasync.aspx It promises to do a data-sync between local and Azure versions of a SQL database.
Hope this helps
Upvotes: 1
Reputation: 4371
I ended up doing some more research and discussing with coworkers. We came to the conclusion that there is no great way to manage databases as one traditionally would, but you can follow the process outlined below.
This is about the best it is going to be for now. You can alternatively use a Data Layer application, which essentially does the same thing.
Upvotes: 0
Reputation: 1758
Deploying to SQL Azure is no different than it would be when you are deploying to a separate SQL Server machine running SQL Server Standard or Enterprise edition. This is different from deploying to a web server that is also running SQL Server Express, that allows you to package an MDF file as part of the ASP.NET app, but that is by design. There are tools available, but you could also script the changes to the database (either by hand or automatically).
Another possible way of automating the deployment is by leveraging the SQL Azure migration wizard, but that will still require a bit of setting up (it is more geared towards 1-time-only migrations).
Upvotes: 1