Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Git workflow with SQL Server databases (SSDT)

Our simplified structure is:
                      / developer1_database
SQL Server -- developer2_database
                      \ main_database <-- report server

developerX_database - database that is used only by single developer, he is free to deploy anything and anytime there.
main_database - currently the database that is automatically updated with every push to develop branch. REPORTS that are under testing are pointed to that database.

This is more or less the vision how do we see the process is supposed to be look like:

* Dev creates feature branch
* Dev push changes to feature branch
* Dev create pull request to develop branch
* Other devs approve pull requests
* Release manager merge feature to develop branch
* Relase manager initiate build that would test the changes and output deploy script
* Release manager reviews output script and run it on prod
* Release manager merges changes to master branch

Now we have problems/questions:
1) We would like to have clean pull requests only, the best way would be that before we merge it to develop it is supposed to be buildable and all tests passed. How and where to test it?
2) We would like to allow the business to test report before it merged into the develop database. This process can take time so the "feature" version of the database state must exist somewhere. Where? If we use "developer" database for that then he will not be able to switch to another feature as he will just nuke all his changes from previous feature when he would deploy the new one.


0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

222 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you