Evil Kraig F (2/13/2014)
...I'll have to try to sit in on Steve's talk one day, but I want to see the nuts and bolts of the final produced product. I want to know what % of weekly dev time is put into maintaining the scripts allowing for CI not to break things on its way through. I want to see exactly what's produced for a series of changes on the same object by multiple developers, and see if it's an intelligent result.
The slide deck that's provided in the link doesn't go into these details, and I've always found that's where the devil lives in CI for databases. We have to persist, the front end doesn't. Almost all CI I've seen for front end code actually has exception rules for ini files, which is what "they" persist.
Always welcome. The way we do CI is mainly with calls to SQLCompare, so that you can go from vX to vY, no matter where x and y are.
The index/schema thing is interesting. For sure that's something I'll have to look more into. I haven't been too worried about indexes, but they certainly need to be handled.