Settings and activity
8 results found
-
633 votes
Hi,
We just added this capability to Flyway, which is our x-database, x-OS cloud- and Git-first Database DevOps solution for versioning and deploying database changes. You can learn more about this feature in Flyway at https://documentation.red-gate.com/fd/working-with-data-138347109.html#Workingwithdata-Controllingstaticdata.
You can also import your SQL Source Control repos into Flyway while keeping your Git history. Learn more about moving to Flyway and importing your project at https://documentation.red-gate.com/fd/transitioning-from-other-redgate-tools-164167855.html.
If you have any questions, please comment below or reach out to us at DatabaseDevOps@red-gate.com.
Thank you!
Stephanie Herr
Product Manager - Database DevOps
Marcin
supported this idea
·
-
200 votes
Kendra
responded
While SQL Source Control does not currently provide a simple way to right click and ‘Undo’ static data changes on the ‘Commit’ screen as suggested, there is a workaround which may help some users.
If you wish to revert the static data in the table to a previous version which you have committed, you can do this by viewing the history of commits for the object in SQL Source Control, and then launching SQL Data Compare to update the database.
Please note that this workaround requires a license for Data Compare. More detail on how to do this are here: https://documentation.red-gate.com/soc/common-tasks/update-to-a-revision-from-source-control
Marcin
supported this idea
·
-
104 votesMarcin
supported this idea
·
-
35 votes
An error occurred while saving the comment -
17 votes
-
15 votes
-
10 votes
-
13 votes
An error occurred while saving the comment Marcin
commented
I have the same problem, but I could divide it on two topics:
First is connected with option "Force binary collation", if I switch off this option then comparison result is correct (although the data are identical)
Second is connected with some characters: #, $, + (these values are primary key values).
In such case a conflict is shown). Both comparison sites contain following statements:INSERT INTO <table1> (<columns>) VALUES (N'#', N'Hash', NULL)
INSERT INTO <table1> (<columns>) VALUES (N'$', N'Dolar', NULL)
INSERT INTO <table1> (<columns>) VALUES (N'+', N'Plus', NULL)(Database collation: SQL_Latin1_General_CP1_CI_AS)
This is not only problem of SQL Source Control, our build server uses SQL Comparer and SQL Data Comparer command line tools to build nightly our development server and it failed when I switch on the option "Force binary collation".
This issue is crucial for us because TFS server is located in another country then a developing team. Please give us a feedback when such functionality can be included in SQL Source Control.