Separate databases for Staging and Production?
i downloaded "windows azure platform training kit - august 2009 ", contains bunch of labs , presentations on sql azure.
i'm still struggling "register ctp", have theoretical question.
let's suppose web , worker roles run 100% on windows azure (nothing on-premise).
since database schema , data change between versions, experience need 2 separate databases staging/qa , production.
once connect sql azure , create database , login/user account need create 2 databases - 1 staging , 1 production? or moment create 1 database, azure portal creates 2 automatically?
if have create 2 separate databases myself, charged staging database? example, if choose $99/10 gb option, charged $198?
i'm still struggling "register ctp", have theoretical question.
let's suppose web , worker roles run 100% on windows azure (nothing on-premise).
since database schema , data change between versions, experience need 2 separate databases staging/qa , production.
once connect sql azure , create database , login/user account need create 2 databases - 1 staging , 1 production? or moment create 1 database, azure portal creates 2 automatically?
if have create 2 separate databases myself, charged staging database? example, if choose $99/10 gb option, charged $198?
hi emmanuel,
when create a database, (and charged for) 1 database.
if want have two separate databases - 1 staging , 1 production, you need provision two databases. in case charged 2 databases.
stan
program manager, sql azure
when create a database, (and charged for) 1 database.
if want have two separate databases - 1 staging , 1 production, you need provision two databases. in case charged 2 databases.
stan
program manager, sql azure
Microsoft Azure > Azure SQL Database
Comments
Post a Comment