Comments posted to this topic are about the item The Road to Database CI
Steve Thompson-454462 - Tuesday, May 16, 2017 10:52 PM
Thanks for the article! Just wondering if you also use SSIS/SSAS/SSRS and have to integrate those into your CI workflow? If so, how's it going?
gbritton1 - Wednesday, May 17, 2017 8:55 AM
Thanks for reading and really good question. I'm sorry to say that the short answer is no: even though we do use SSIS quite a bit, we didn't dedicate the resources needed to operationalize those deploys to the same degree that we did db schema. We've started putting our greenfield projects into Git, but haven't done anything about automating deploys through Bamboo. There were a coupe of reasons, including the fact that we really only have one SSIS engineer right now, so there weren't many issues with tracking changes; and that our roadmap has us pivoting away from encapsulating ETL logic within SSIS. With that said, I do think that any shop that's serious about CI and has SSIS (or SSRS/SSAS) dependencies should most definitely look into building a process around them.
This is a great view into how you approach database CI. Thank you!
How do you manage code reviews after code is deployed to the Development environment?
Data Wrangler - Thursday, May 18, 2017 5:29 PM
Thanks, Data Wrangler! I'm glad you liked it.
Generally, the engineer will generate a Pull Request for his/her feature branch against the Test branch; our definition of done for Test says that you need at least one approval before you can merge (Bitbucket can be set up to enforce this). This is a bit of a departure from standard GitFlow where you'd promote Dev in its entirety. But because our dbs are shared across several apps, and our Product Owners don't always approve an entire Sprint's worth of work for immediate release, we need to promote at a feature granularity.
Steve Thompson-454462 - Thursday, May 18, 2017 5:54 PM
That sounds like just the approach we should use, and we happen to have Bitbucket Server. We too, have databases shared by multiple applications, so we'll probably go with feature branches. Now if only we can get our hands on Red Gate SQL Source Control--it's been a struggle budget-wise recently.
Data Wrangler - Thursday, May 18, 2017 7:00 PM
I feel you on the budget issues. Highly recommend the Redgate tools if you can swing it, but if you can't you could look into Flyway. It's migration-based instead of state-based which I feel takes a bit of getting used to, but it is open sourced (we use it for our Postgres repos).
This was removed by the editor as SPAM
This is a very interesting article. As far as I know, none of our SQL objects are in source control. Well, except for what we, the developers, write in order to create tables and views. But there's no migration, nothing. All that's there is the latest CREATE TABLE or CREATE VIEW command.
I've got a question about Red Gate's SQL Source Control. Does it work with TFVC? Personally, I prefer to use Git, but my employer has settled on TFVC, so either SQL Source Control works with TFVC or it won't be considered.
The world's most well-known online payment system.
Here is new Cash Out Methods and also learn how to spam!!!
Cloned Card And Dumps + Pin
Text or call for more details:
Wickr : kenkylian
wsApp : +13476882381
Long term deal and bulk orders are welcome
Viewing 10 posts - 1 through 9 (of 9 total)