Timeline for Managing static (or reference) data between different environments?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 11, 2018 at 5:13 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Oct 24, 2016 at 12:41 | comment | added | EnterTheCode | I've been using a trial version of Red-Gate SQL Source Control and I enjoy it, but I don't think it will be a realistic option due licensing required for each developer. | |
| Oct 23, 2016 at 14:24 | comment | added | Dan Guzman | Are you also using Red-Gate SQL Source control? That would allow developers use Data Compare to commit their own data changes into source control that are ready for deployment to other environments since only they will know what's ready and what's not. You can then use source control as the source for your build/deploy process for both schema and data. | |
| Oct 23, 2016 at 0:05 | comment | added | Aaron Bertrand | Well it certainly wouldn't make me any more willing to use MERGE. Whether you could use a method like mine depends on whether blocking the tables is more disruptive than adding disabling/re-enabling foreign keys and using delete instead of truncate. | |
| Oct 22, 2016 at 22:53 | comment | added | EnterTheCode | @AaronBertrand I read through your articles, and it appears that this method will not work when foreign key constraints exists on these tables? (95% of them are foreign keyed to user response related tables.) Also, the majority of these changes are UPDATE (modifying identifiers or labels) and INSERTS for new data, while DELETE statements are rare. Would this alter your stance? | |
| Oct 22, 2016 at 14:16 | comment | added | Aaron Bertrand |
Also, I would strongly caution against MERGE - virtually everything you can do with MERGE you could do before MERGE, and I find the older methods safer and more reliable..
|
|
| Oct 22, 2016 at 14:15 | comment | added | Aaron Bertrand | Determining which data is correct seems like it will either require a human to intervene and make subjective decisions no matter what, or that you add columns to reference tables that indicate whether this row is ok to push live or not. If you're just going to assume all changes are accurate, I've built a fairly easy to implement mousetrap for that: part 1 | part 2. | |
| Oct 22, 2016 at 14:14 | answer | added | Martin Smith | timeline score: 2 | |
| Oct 22, 2016 at 13:58 | review | First posts | |||
| Oct 22, 2016 at 15:02 | |||||
| Oct 22, 2016 at 13:58 | history | asked | EnterTheCode | CC BY-SA 3.0 |