SQL Source Control

https://documentation.red-gate.com/display/SOC5/SQL+Source+Control+5+documentation

SELECT DB_NAME(DatabaseID) AS DatabaseName ,
       UserName ,
       *
FROM   dbo.RG_AllObjects_v4
WHERE  UserName IS NOT NULL
ORDER BY EntryDateTime ASC

EntryDateTime是第一次加入dbo.RG_AllObjects_v4中的时间，后面每一次修改是更新modify date。

删除操作之后，第二次再添加的话，会重新加一条新的记录

SELECT *
FROM dbo.RG_AllObjects_v4
ORDER BY ModifyDate DESC,
         EntryDateTime ASC;

SELECT *
FROM dbo.RG_AllObjects_v4
WHERE ObjectName = 'DeleteAllData';

Working with migration scripts

What are migration scripts?

To deploy changes from version control, the SQL Compare engine generates a deployment script. This is based on the differences between the state in version control and the target database. Migration scripts in version control can define how the SQL Compare engine generates specific sections of this deployment script.

Migration scripts are necessary to avoid data loss when making certain schema changes. To achieve this, the migration script intervenes to make data changes occur at the right point of the deployment.

In most cases, you only need to write SQL for the data changes in the migration script. Schema changes are committed separately and deployed as normal.

To learn more, see Migration script examples.

Deploying migration scripts

SQL Compare 11 or later can generate deployment scripts with migrations using the following source/target types:

Source:

• Scripts folder
• Source control

Target:

• Live database
• Scripts folder

We recommend using SQL Compare to deploy changes to production, as you have the opportunity to review the deployment script before it's deployed. For a full walkthrough of the deployment process using SQL Compare, see Migration script examples.

It is possible to use the Get latest function in SQL Source Control to deploy these changes, however we don't recommend linking your production database directly to source control.

Dependencies

When you create a migration script that includes uncommitted schema changes, SQL Source Control automatically includes any dependencies. Deselecting any of these dependencies during the deployment stage will cause the deployment to fail.

Static data

Migration scripts do not work with static data. See Static data and migrations.

Deploy a database from source control

To deploy a database from source control to a server, use SQL Compare Pro, or the SQL Server Management Studio Integration Pack add-in.

Deploying with SQL Compare

To deploy with SQL Compare:

1. Open SQL Compare.
2. Select a version from source control.
   For full instructions, "Selecting a version from source control" on the Setting data sources page (SQL Compare documentation).
3. Run the comparison.
4. Open the Deployment Wizard and deploy the version.
   For full instructions, see Deploying data sources (SQL Compare documentation).

sql source control在client 和server之间进行还原

1.建立2个分支local 和master

2.确保没问题的，提交在master分支上，测试的可以提交在local上

3.local和master分支，是可以fast-forward。master在前，local在后

4.通过切换分支，切换到local分支，可以将local上的代码，apply到server上

最后2个存储过程是新增的。当前切换到local分支，可以在右上角确认

5.切换到master分支，可以undo changes之前apply到server上的代码

其中第1个和第2个存储过程是新增的，所以现在还原，是删除操作

其中第4和第5，都是在get latest界面进行操作

Client和Server之间进行处理，detach本地的数据库，将服务器上的数据库备份好之后，restore到本地

假设服务器的分支提交为C1,C2,C3,然后还有没有提交的修改

假设本地分支的提交为C1,C2,C3,C4,C5。

restore服务器数据库到本地后，本地的数据库的实际内容变成C1,C2,C3以及未提交的修改。

那么restore到本地之后，在commit的选项卡上，会发现，sql source control 会认为C5才是正确的版本，然后C3和C5之间的差异，会变成一次modify。

这次modify相当于，把C5修改回C3了，所以要让本地的数据库，同步到C5的修改，需要做一次undo changes。

同时维护2个分支

Filter的优先级最高

如果在get latest的tab中看到filter的话，优先apply filter。否则会导致一些意外的问题

升级

如果在Management Studio看到sql source control升级提示的话，

首先需要切换到国外的代理，然后再点击升级按钮。否则是无法升级成功的

object changed by unknown

https://documentation.red-gate.com/soc6/troubleshooting/object-changed-by-unknown

By default, SQL Source Control reads information about who made changes from the default trace and saves it in tempdb. However, because tempdb is reset when the server is restarted, information about who made a change is eventually lost.

Fix

To stop the information being lost, you can create a database to log changes instead of tempdb.

https://documentation.red-gate.com/soc6/configuring/log-changes-to-shared-databases

Step 1: Creating the change log database

Step 2: Editing the config file

SELECT DB_NAME(DatabaseID) AS DatabaseName,
       *
FROM   dbo.RG_AllObjects_v4;

上面的配置有时候会失效，不管怎么操作都是unknown。可能是服务器上的sql server的服务有问题导致的，只需要重新启动一下sql server的服务，就可以正常记录user是谁。

sql source control对应的git repository目录更换了，需要批量替换

echo %userprofile%\AppData\Local\Red Gate\SQL Source Control 7\LinkedDatabases.xml

C:\Users\clu\AppData\Local\Red Gate\SQL Source Control 7\LinkedDatabases.xml

ignore pattern

ignore user,role, and schema

https://www.cnblogs.com/chucklu/p/9466382.html