User profile for David E

Hi Bob, In DLM Automation 2.1 we introduced the ability to install the DLMA Powershell cmdlets via the Powershell Gallery. This should provide a much easier way of installing DLM Automation for scenarios such as the one you have described above. It is possible to install the module for the current user by calling the following code. This makes use of the PowerShellGet functionality built into PowerShell 5. Install-Module DLMAutomation The Powershell Gallery listing for DLM Automation can be found here. / comments

Hi Bob,In DLM Automation 2.1 we introduced the ability to install the DLMA Powershell cmdlets via the Powershell Gallery. This should provide a much easier way of installing DLM Automation for scen...

0 votes

Hi, We've done some investigation and believe we've found what was causing the issue. We've just released version 2.0.27 of the DLM Automation 2: Build extension which should fix this. Please let us know if there are any further problems. / comments

Hi,We've done some investigation and believe we've found what was causing the issue. We've just released version 2.0.27 of the DLM Automation 2: Build extension which should fix this. Please let us...

0 votes

Hi, Based on the error message it appears that .Net Framework 4.6 is missing on the server you are using. You can download and install the required framework from: http://go.microsoft.com/fwlink/?LinkId=671729. The installer for DLM Automation should have detected if all the prerequisites were installed so it looks like something strange has happened here. Was installation on the servers done by running the installer or copying the files from your local machine? / comments

Hi, Based on the error message it appears that .Net Framework 4.6 is missing on the server you are using. You can download and install the required framework from: http://go.microsoft.com/fwlink/?L...

0 votes

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 Matt, Thanks for letting us know about this. It appears we've got the bindings on these text boxes set up incorrectly, and they're only updating on change of focus rather than each key press. I've just made a change to fix this, and it should be in our next frequent update. / comments

Hi Matt, Thanks for letting us know about this. It appears we've got the bindings on these text boxes set up incorrectly, and they're only updating on change of focus rather than each key press. I'...

0 votes

Thanks for your post, Are there other differences in the two table definitions? Does this table show as "in both , but different" in the upper comparison grid? The logic to determine if objects are shown as different or identical in the upper grid is aware of the options you have selected. If you were to select this object to be deployed you should see no change being deployed to the constraint name. If you are seeing changes in the deployment script, we have a bug that we should investigate in more detail. The lower pane of SQL Compare will show a textual difference between the two objects as they would be returned from SQL Server. This view is not aware of the option you have provided as it performs a naive text comparison. This does seem like one of the cases where we could avoid scripting out the constraint names to avoid this confusion. I'll have a look and see if there are any improvements we can make. / comments

Thanks for your post, Are there other differences in the two table definitions? Does this table show as "in both , but different" in the upper comparison grid? The logic to determine if objects are...

0 votes

Hi Rob, Unfortunately there are no functions within the product to help move these across. I think the "find-replace" approach you describe should work, just make sure to apply your transformation to both the "UnmapTables" and "MapTables" actions as well as any column actions that specify the table name. Let us know how you get on. / comments

Hi Rob, Unfortunately there are no functions within the product to help move these across. I think the "find-replace" approach you describe should work, just make sure to apply your transformation ...

0 votes

Hi tschlarm, We believe this has been resolved in SQL Data Compare 12.3.2. It appears that in some cases when deploying from right to left we were getting the INSERT/UPDATE/DELETE selections confused. This was caused by the work to remove the re-comparison step when changing deployment direction. Please let us know if this latest release resolves the issue and if you see any other strange behavior. / comments

Hi tschlarm, We believe this has been resolved in SQL Data Compare 12.3.2. It appears that in some cases when deploying from right to left we were getting the INSERT/UPDATE/DELETE selections confus...

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

This should now be resolved in 12.2.4, which we have released today. / comments

This should now be resolved in 12.2.4, which we have released today.

0 votes

How can we help you today?

David E

Comments