Comments
Sort by recent activity
The push button and branch name is a feature implemented only for Git. You can only use the dedicated model when using Git as your source control system in SQL Source Control. / comments
The push button and branch name is a feature implemented only for Git. You can only use the dedicated model when using Git as your source control system in SQL Source Control.
We are aware of some performance issues when using Git in the latest releases that we would like to address. I invite you to contact our support team and if possible to provide details of your schema. This can really help us with the investigation. Thanks / comments
We are aware of some performance issues when using Git in the latest releases that we would like to address. I invite you to contact our support team and if possible to provide details of your sche...
It's hard to reply without details, unfortunately. If you have a support contract, please get in contact with support and with a proper NDA we can maybe look at your issue in more detail? Make sure you have a valid primary key in the tables you want to add. If I understand correctly the same rows in the same table are added and same not. So the obvious question is, is there anything special about the excluded rows? Also, keep in mind, this feature is designed to support only a limited amount of static data (also known as lookup or reference data). Source-controlling very large static data tables might cause SQL Source Control to time out. / comments
It's hard to reply without details, unfortunately. If you have a support contract, please get in contact with support and with a proper NDA we can maybe look at your issue in more detail?Make sure ...
Unfortunately, at the moment there is not a way to do it. Running Invoke-DatabaseTests always does a build before running the tests. / comments
Unfortunately, at the moment there is not a way to do it. Running Invoke-DatabaseTests always does a build before running the tests.
To deploy using PowerShell you can use the following cmdlets:
New-DatabaseReleaseArtifact - to create the database release artifacts
Use-DatabaseReleaseArtifact - to run the update script against the target database
You can find information on how to use them at the following address: https://documentation.red-gate.com/sca3/automating-database-changes/automated-deployments / comments
To deploy using PowerShell you can use the following cmdlets:
New-DatabaseReleaseArtifact - to create the database release artifacts
Use-DatabaseReleaseArtifact - to run the update script against...
Hi everyone, I am glad to inform you that in the latest release of SQL Source Control 6.2.2.7785 this problem has been fixed. We now ship the missing dll with SQL Source Control. Thanks for your patience. / comments
Hi everyone,I am glad to inform you that in the latest release of SQL Source Control 6.2.2.7785 this problem has been fixed. We now ship the missing dll with SQL Source Control.Thanks for your pati...
We are aware of the issue and we are sorry for the inconvenience. We are working to ship a new version soon that embed with SqlParser library in it. The workaround, for now, is to manually install the dll in the GAC that you can get at this address https://docs.microsoft.com/en-us/sql/relational-databases/server-management-objects-smo/installing-smo?view=sql-server-2017 / comments
We are aware of the issue and we are sorry for the inconvenience. We are working to ship a new version soon that embed with SqlParser library in it. The workaround, for now, is to manually install ...
Could you please contact our support team and raise this as an issue? It's likely that we are going to need more information on your database folder in order to investigate it. Thanks / comments
Could you please contact our support team and raise this as an issue? It's likely that we are going to need more information on your database folder in order to investigate it. Thanks
The latest version of SQL Source Control 6.2.1.7693 contains a fix for this problem. Thanks for raising the issue. / comments
The latest version of SQL Source Control 6.2.1.7693 contains a fix for this problem. Thanks for raising the issue.
This is indeed a bug and we can reproduce it. We'll try to get a fix out soon. In the meantime, you can use the previous version (6.1.8.758) where this problem is not present. Thanks for your patience / comments
This is indeed a bug and we can reproduce it. We'll try to get a fix out soon.In the meantime, you can use the previous version (6.1.8.758) where this problem is not present.Thanks for your patience