SQL Source Control v7 is now available on the Frequent Updates channel featuring:
Let’s explore these features:
1) Better Git Support
Git is a very popular version control system. We’ve been supporting Git for a while, but there were authentication problems when trying to push or pull to a Git repository on TFS/VSTS (now called Azure DevOps), which required some users to leave SSMS when working with Git. This has now been fixed and you don't have to leave SSMS to push or pull anymore.
In addition, the changes we made now mean that SQL Source Control support Git Hooks. Users can setup pre and post Git Hooks to comply with their own policies and rules. Some users setup hooks to require comments or require check-ins to be associated with a story or bug ID. In previous versions of SQL Source Control, we just ignored these, which means users weren’t complying with the policies created. This is now enforced in SQL Source Control v7.
If you are using Git, you will need Git for Windows on your machine that has SQL Source Control installed. If you do not have it, you will be notified when linking new databases or trying to Commit/Get Latest/View History on databases already linked to Git. The notification will have information to download and install it.![]()
We are excited that this work is responding to feedback on our UserVoice site and we can close these soon:
2) Pre/Post Deployment Scripts
Pre and Post deployment scripts give you additional flexibility when you are automating your database deployments. We used to ask users to manage their own scripts outside of our tools and orchestrate this via their release management system, which took more time to setup. Now, you can do everything right in SQL Source Control and it will be picked up in manual deployments with SQL Compare or automated deployments with SQL Change Automation.
@SERVERNAME to customize where the scripts run and have different SQL statements for different environments. This can be useful for managing permissions and adding different users into roles in different environments or handling data that is different across the environments.
There are some great examples about using Pre and Post deployment scripts in our documentation.
This was available in the v6.3 release on the Frequent Updates channel and feedback has been good so far. We’d love to hear more if you’ve had a chance to try it. If not, try it now. ![:)]( ":)")
3) SSMS 2018 Preview Support
SQL Source Control will work in the latest SSMS 2018 preview release. Keeping up with the latest IDEs is an important part of our product development.
Configure Frequent Updates
You can configure Frequent Updates in the SQL Source Control Help menu within SSMS. Once set, just Check for Updates in the SQL Source Control Help menu.
As always, please give this version a try, especially if you are using Git so we can test out this upgrade experience on more “real world” machines. We look forward to hearing your feedback.
When will the full release of SQL Source Control v7 be?
It depends on how many people try this version and what type of feedback/issues we receive, but we hope it will be within a few weeks. At that time, we can really start shouting, blogging, tweeting about it and we hope you will too.
Hi Friends,
SQL Source Control v7 is now available on the Frequent Updates channel featuring:
Better Git support
Pre/Post deployment scripts
SSMS 2018 Preview support
Let’s explore these features:
1) Better Git Support
Git is a very popular version control system. We’ve been supporting Git for a while, but there were authentication problems when trying to push or pull to a Git repository on TFS/VSTS (now called Azure DevOps), which required some users to leave SSMS when working with Git. This has now been fixed and you don't have to leave SSMS to push or pull anymore.
In addition, the changes we made now mean that SQL Source Control support Git Hooks. Users can setup pre and post Git Hooks to comply with their own policies and rules. Some users setup hooks to require comments or require check-ins to be associated with a story or bug ID. In previous versions of SQL Source Control, we just ignored these, which means users weren’t complying with the policies created. This is now enforced in SQL Source Control v7.
If you are using Git, you will need Git for Windows on your machine that has SQL Source Control installed. If you do not have it, you will be notified when linking new databases or trying to Commit/Get Latest/View History on databases already linked to Git. The notification will have information to download and install it.![]()
We are excited that this work is responding to feedback on our UserVoice site and we can close these soon:
2) Pre/Post Deployment Scripts
Pre and Post deployment scripts give you additional flexibility when you are automating your database deployments. We used to ask users to manage their own scripts outside of our tools and orchestrate this via their release management system, which took more time to setup. Now, you can do everything right in SQL Source Control and it will be picked up in manual deployments with SQL Compare or automated deployments with SQL Change Automation.
@SERVERNAME to customize where the scripts run and have different SQL statements for different environments. This can be useful for managing permissions and adding different users into roles in different environments or handling data that is different across the environments.
There are some great examples about using Pre and Post deployment scripts in our documentation.
This was available in the v6.3 release on the Frequent Updates channel and feedback has been good so far. We’d love to hear more if you’ve had a chance to try it. If not, try it now.![:)]( ":)")
3) SSMS 2018 Preview Support
SQL Source Control will work in the latest SSMS 2018 preview release. Keeping up with the latest IDEs is an important part of our product development.
Configure Frequent Updates
You can configure Frequent Updates in the SQL Source Control Help menu within SSMS. Once set, just Check for Updates in the SQL Source Control Help menu.
As always, please give this version a try, especially if you are using Git so we can test out this upgrade experience on more “real world” machines. We look forward to hearing your feedback.
When will the full release of SQL Source Control v7 be?
It depends on how many people try this version and what type of feedback/issues we receive, but we hope it will be within a few weeks. At that time, we can really start shouting, blogging, tweeting about it and we hope you will too.