How can we help you today? How can we help you today?
David E
Hi, Its possible to use filters in most Redgate products to achieve this. You can specify a filter to include only objects in a certain schema and only these will be compared and deployed. In SQL Compare you can set up a number of projects targeting the same database but different scripts folders and specify the appropriate filter with each. If these scripts folders are then targeted by DLM Automation the appropriate filter files will be picked up and used during deployment. Unfortunately SQL Source Control only allows linking each database to one repository, and therefore will only allow a single filter to be specified. This means that it might not be the best fit if you have multiple repositories referencing the same database. ReadyRoll does allow linking multiple projects (and therefore repositories) to the same database but does not yet support filter files. An alternative would be to filter the pending changes table on each import and only select those items under the schema for the current repository. There is support for excluding certain objects so that they never appear in the pending changes list, but this may take a while to configure for each micro service. / comments
Hi, Its possible to use filters in most Redgate products to achieve this. You can specify a filter to include only objects in a certain schema and only these will be compared and deployed. In SQL C...
0 votes
Hi, We are aware with an issue with the latest frequent release of SQL Compare and integration with SQL Source Control. We are aiming to release fix for the issue you have described shortly. David / comments
Hi, We are aware with an issue with the latest frequent release of SQL Compare and integration with SQL Source Control. We are aiming to release fix for the issue you have described shortly. David
0 votes
Hi Zippy, In versions of Data Compare before 12 all actions you performed on the mappings and selections screen were recorded and stored to the project file in order. Every selection and deselection of a checkbox was recorded and stored. The previous "Select None" button would be recorded as one of these actions. These were all replayed in order each time the project file was loaded, which would result in some cases of having exceptionally long times to complete the mappings step, or in the worst case, errors if objects had been removed or renamed. As part of the changes we made in V12 to simplify how mappings and table selections work, we made the decision to calculate the minimal set of actions required to get the project in to the desired state and only record this in the project file. This removed the need to record everything that had ever happened on this screen to the file. In this process we choose to use "deselect item" actions as our way of recording the tables that had been selected as this was what would happen in V11 if you have never pressed the "Select none" button. In making this decision we removed the workflow that you have described. This latest option has been designed to restore that workflow and record "select item" actions instead. I can see how this would be seen as a regression of functionality and that projects still saved in the old format should be loaded into V12 with the option set appropriately - I will see if we can find a way to populate the option based on the actions in the V11 project file. Unfortunately for projects that have been used in V12 already this information will have been lost as part of the above minimal actions calculation. These will no longer contain the "select none" action that indicates which behavior was being used in the V11 file. David / comments
Hi Zippy, In versions of Data Compare before 12 all actions you performed on the mappings and selections screen were recorded and stored to the project file in order. Every selection and deselectio...
0 votes