Im exploring the idea of both CI and 2014 Availability groups in DEV at the moment. current prod environment is 2008 with some legacy 2005 that needs uplifting before a move to 2014 in prod is implemented. so I have a little time to explore the options in dev. I think ill stick with traditional deployment into the prod environment.I'm ok with SSDT database project and TFS for source code control, but it then starts to get tricky.What would be best practice to set up a shared SQLdev & UAT environment that utilised CI into an AlwaysOn Activity group.Do you need to build to each node on check in and if so how do you handle data persistence across the nodes which will be different as data is replicated across the nodes from primary.Is it enough to Suspend data movement between nodes update primary and then resume data movement and can this be scripted? How are Object changes like new fields to tables and new procs deployed?Ive not seen this discussed in CI threads I've read to date. (any pointers appreciated)
↧