Database Reference
In-Depth Information
■
Note
As mentioned previously, you're now paying for this Windows Azure service. You must first suspend your
service (by clicking Suspend) if it's running; however, that alone doesn't stop you from accruing charges. You must
also click the Delete button under both your staging and production environments. On the same page is a Delete
Service button; it releases your service altogether and doesn't affect how you're billed.
Now that the code has been tested in staging, go back to the service management page (shown
earlier in Figure 9-18) and click the center icon ( ) to promote your code to production. A confirmation
message comes up. This operation swaps both environments (production and staging); you can expect
to wait a few minutes while the swapping takes place. Once in production, the URL you registered
previously works.
You may have noticed that you haven't changed any database settings between staging and
production. Staging and production environments refer only to Windows Azure services, not the SQL
Azure database running behind the scenes.
As a result all versions of your ASP.NET application (when run locally, in staging or in production)
point to the same SQL Azure database by default, unless you specifically change your configuration
settings in each environment (see Figure 9-20). You also need to make sure your firewall configuration is
correctly set, or you may have a surprise when publishing your web application in the cloud.
Figure 9-20.
Summary of deployment scenarios
