Comments
Sort by recent activity
Hi @..., Thanks for letting us know. I haven't seen this issue personally but am sorry to hear it's happened to you. The survey has finished up, and a release to remove the survey has gone out to the SQL Source Control "Frequent Updates" channel. If you enable frequent updates, I think you will be able to upgrade to a version where the banner goes away. If you're already on frequent updates or the banner blocks you from updating, please let us know. Kendra / comments
Hi @...,Thanks for letting us know. I haven't seen this issue personally but am sorry to hear it's happened to you. The survey has finished up, and a release to remove the survey has gone out to t...
Hi Dan, To clarify— the two products I mention are alternatives to SQL Source Control. SQL Source Control doesn’t have the functionality for managing data in this way. Hope this helps, Kendra / comments
Hi Dan,To clarify— the two products I mention are alternatives to SQL Source Control. SQL Source Control doesn’t have the functionality for managing data in this way.Hope this helps,Kendra
Update -- I added an example to the page on Filtering itself which describes how to do this - https://documentation.red-gate.com/display/sca4/Filtering Hopefully that helps others in the future. / comments
Update -- I added an example to the page on Filtering itself which describes how to do this - https://documentation.red-gate.com/display/sca4/FilteringHopefully that helps others in the future.
Hi @nharris18, There are two configuration changes you might wish to make: 1) Add a filter file to exclude users. This will prevent SQL Change Automation from scripting users out from the database. I've attached a sample SQL Compare file if that saves you time. 2) Set the project option SyncOptionIgnoreUsersPermissionsAndRoleMemberships to True (default is False / do not ignore these) in your sqlproj file. This will prevent SQL Change Automation from scripting out GRANT scripts for users who are members of roles. If you don't want the users scripted, you probably also don't want their role permissions scripted. Hope this helps and I'll have a look at the documentation to see if there's a sensible place to add this which might show up for folks in search results when they hit this question. Kendra / comments
Hi @nharris18,There are two configuration changes you might wish to make:1) Add a filter file to exclude users. This will prevent SQL Change Automation from scripting users out from the database. I...
Hi @Danr, We don't recommend SQL Source Control for large static data tables. At the heart of the challenge is that data comparison gets slower as the tables you are comparing get larger and wider. This can lead for the plugin to need to use a lot of CPU and memory and also cause the user to wait longer periods for the comparison to complete. For larger static data tables, SQL Change Automation has a "seed data" option which can work well in many scenarios. SQL Change Automation is available as part of the SQL Toolbelt. If you don't have the SQL Toolbelt, you could implement a similar methodology to the seed data option with Flyway if desired. Hope this helps, Kendra / comments
Hi @Danr,We don't recommend SQL Source Control for large static data tables. At the heart of the challenge is that data comparison gets slower as the tables you are comparing get larger and wider. ...
Hi EKelly, I believe that page is the main documentation we have on the offline method for static data. This morning I've just added an example post-deployment script approach for offline static data to the documentation, and linked to it from the main static data page. Does this help? Thanks for this note, and further feedback is very welcome. Cheers, Kendra / comments
Hi EKelly,I believe that page is the main documentation we have on the offline method for static data.This morning I've just added an example post-deployment script approach for offline static data...
Hi @Dylan01p , We recommend using dedicated development databases with SQL Change Automation. If you do need to use a shared development database, we recommend disabling the programmable objects feature. We have some more information documented here: https://documentation.red-gate.com/sca/getting-started/system-requirements/development-database-environment-configuration Hope this helps, Kendra / comments
Hi @Dylan01p ,We recommend using dedicated development databases with SQL Change Automation. If you do need to use a shared development database, we recommend disabling the programmable objects fea...
Hi @Koenraad.Dendievel, Thanks for letting us know about your use case. This enhancement is up for consideration and I've updated the request with the use case info you provided. It's just up for consideration and not something we're actively working on presently, but understanding customer impact definitely helps us. Kendra / comments
Hi @Koenraad.Dendievel,Thanks for letting us know about your use case. This enhancement is up for consideration and I've updated the request with the use case info you provided. It's just up for co...
Hi @Awen , I definitely recommend changing the operation to "Build a SQL Source Control project", if that's what you're actually doing. The build task for SQL Change Automation projects has a check to validate three part names. That can be disabled by making changes in the SQL Change Automation project configuration file -- but you can't do things like that for SQL Source Control as it doesn't even have that file. Hope this helps, Kendra / comments
Hi @Awen ,I definitely recommend changing the operation to "Build a SQL Source Control project", if that's what you're actually doing.The build task for SQL Change Automation projects has a check t...
Hi @sam_alexander, We don't recommend using SQL Source Control to apply changes to QA/Staging/Production environments. If you need to deploy changes manually to these environments, we recommend using SQL Compare to do this. I am curious if you were aware that SQL Compare could help with this, if you don't have it installed, if it seemed like SQL Source Control might do the same thing, or if there was another reason? Thanks in advance, Kendra / comments
Hi @sam_alexander,We don't recommend using SQL Source Control to apply changes to QA/Staging/Production environments.If you need to deploy changes manually to these environments, we recommend using...