Best way to manage SQL Server on developer, test, staging, and production environments through Visual Studio 2013 -


i've read article on ms blog , on here on stackoverflow , this article

they shed light on scenario, feel may missing something...

the third article above nicely explains possible way deploy database versions including schema , data... oriented deploying production.

i looking streamline deploying dbproj's developer db instances , test, staging , production.(all sql2012 std. edition)

on developer instances, may few versions off... have contractors leave , may couple of dev cycles before new contractor tries deploy.

also, how schema on target clean itself? know can turn off restrictions remove schema objects, on developer workstation instances logins different other environments , not want deleted!!! second article has clues not work when tried it. have 1 application role across environments , depending on environment right login placed in there.

i have sense may have propose changing our schema, may not fly the other leads.

i appreciate hearing has tried , true process in place can cover seamless deployment 4 environments described above.

thanks!

you might interested in deployment manager , sql source control red gate (full disclosure - work red gate).

the approach these 2 products use keeping development environments in sync is:

  • developers edit local database make changes (or edit shared db across whole team)
  • developers can synchronized database existing source control repository (e.g. svn/git/tfs) using sql source control
  • other team members can update databases repository, , changes applied local database.

deployment manager works ci server allow automated deployment of version of database set of predefined environments. example might want automated deployment integration environment after every commit. deployments out test/staging/production environments push button deployments when required.

under hood it's red gate sql compare comparison technology compare versioned database state target database state. means development database can updated latest state, if older head revision, or new member joining team.

you can include filters within packages/repository exclude objects (for examples users, roles, keys, specific schemas). means can deploy same version/package each environment, , won't interfere these objects.

my colleague has written great intro blog post videos if you're interested in more info.


Comments

Popular posts from this blog

python - Subclassed QStyledItemDelegate ignores Stylesheet -

java - HttpClient 3.1 Connection pooling vs HttpClient 4.3.2 -

SQL: Divide the sum of values in one table with the count of rows in another -