Settings and activity
16 results found
-
285 votes
Thanks to everyone for submitting feedback on this in the form of both voting and comments.
Currently, SQL Source Control does not have strong support for Azure SQL Database: as folks have noted in this item, AAD support, particularly with multi-factor authentication, is desired. Currently SQL Source Control does not work at all with Azure SQL Database with MFA enabled.
An additional issue worth mentioning is that pains with SQL Source Control performance may be worse than interacting with Azure SQL Database due to latency.
We would like to improve the user experience and support for Azure SQL Database, and doing so almost certainly involves addressing both of these issues. This is an area we are beginning to investigate more fully.
Mickey Stuewe supported this idea · -
3 votesMickey Stuewe shared this idea ·
-
19 votesMickey Stuewe shared this idea ·
-
105 votesMickey Stuewe supported this idea ·
-
89 votesMickey Stuewe supported this idea ·
-
11 votesMickey Stuewe supported this idea ·
-
29 votesMickey Stuewe supported this idea ·
-
153 votesMickey Stuewe supported this idea ·
-
104 votesMickey Stuewe supported this idea ·
-
131 votes
An error occurred while saving the comment Mickey Stuewe supported this idea · -
28 votesMickey Stuewe supported this idea ·
-
14 votesMickey Stuewe supported this idea ·
-
47 votesMickey Stuewe supported this idea ·
-
636 votes
Hi everyone. I have merged some User Voice items on this topic of “filtered” static data, as there was significant overlap. I want to share our current guidance on handling scenarios where you need to version a subset of the columns and/or rows in the table.
With SQL Source control, the best option at this point is to use a post-deployment script for this purpose.
SQL Source Control introduced pre- and post- scripts in v6.3.
A post-deployment script gives you a good amount of flexibility over exactly which rows or columns of data you want to include in your project. Example post-deployment scripts for static data are here: https://documentation.red-gate.com/soc7/common-tasks/working-with-pre-post-deployment-scripts/static-data
If you make heavy use of Static Data, we have stronger support for this in SQL Change Automation.
SQL Change Automation:
- Supports column filtered static data tables in the SCA plugin in SSMS
- Supports multiple post-deployment scripts, in case there is…
Mickey Stuewe supported this idea · -
14 votesMickey Stuewe supported this idea ·
-
168 votesMickey Stuewe supported this idea ·
I would like to merge Table scripts as well.
Use Case: A teammate added a Trigger and modified a field in a table and checked it in. I just got done adding documentation to all the columns (with SQL Doc :-) ) and would like to check my changes in too. Now I need to merge the two.