Comments
Sort by recent activity
The drop is probably unavoidable but I wouldn't expect the deployment to fail, can you please give us more details regarding the error you have received? / comments
The drop is probably unavoidable but I wouldn't expect the deployment to fail, can you please give us more details regarding the error you have received?
I understand, I'm afraid that DROP and CREATE is the closest option available currently in SQL Compare. If you wish to, you can suggest that as an improvement on our Uservoice site at https://redgate.uservoice.com/forums/141379-sql-compare / comments
I understand, I'm afraid that DROP and CREATE is the closest option available currently in SQL Compare.If you wish to, you can suggest that as an improvement on our Uservoice site at https://redgat...
I think that "DROP and CREATE" option can help you achieve that: https://documentation.red-gate.com/sc/setting-up-the-comparison/setting-project-options#Settingprojectoptions-AddDROPandCREATEforrerunnablescripts / comments
I think that "DROP and CREATE" option can help you achieve that: https://documentation.red-gate.com/sc/setting-up-the-comparison/setting-project-options#Settingprojectoptions-AddDROPandCREATEforrer...
Hi Nemeth, You can use SQL Data Compare options in the Azure DevOps addon, have you already tried that? / comments
Hi Nemeth,You can use SQL Data Compare options in the Azure DevOps addon, have you already tried that?
Hi, Yes, you can use a filter file that excludes synonyms. For more details please see: https://documentation.red-gate.com/sc/using-the-command-line/switches-used-in-the-command-line#Switchesusedinthecommandline-/Filter / comments
Hi,Yes, you can use a filter file that excludes synonyms.For more details please see: https://documentation.red-gate.com/sc/using-the-command-line/switches-used-in-the-command-line#Switchesusedinth...
Hi, I would recommend that you use SQL Change Automation for SSMS, this will create a migration script with every commit, and you have the option of using SQL Source Control as a source. Please note that this will not incur any extra cost for you as these tools are included both in the SQL Toolbelt and Redgate Deploy suite. Kind Regards, / comments
Hi,I would recommend that you use SQL Change Automation for SSMS, this will create a migration script with every commit, and you have the option of using SQL Source Control as a source.Please note ...
Yes, this is possible and your chosen method is broadly correct. The only thing you need to be aware is that when you've installed the first Web Server, SQL Monitor recorded the thumprint of that original Web Server on a file and it will only accept connections from that Web Server from then on. As a result of that if you just follow your steps you will run into an error when you first attempt to connect the new Web Server to the Base Monitor: The Web Server isn't authorized to access this Base Monitor To avoid this error before adding the new Web Server you should delete the RedGate.SqlMonitor.AuthorizedClients.config file from the SQL Base Monitor (detailed instructions here: https://documentation.red-gate.com/sm/troubleshooting/error-messages/the-web-server-isn-t-authorized-to-access-this-base-monitor ) / comments
Yes, this is possible and your chosen method is broadly correct.The only thing you need to be aware is that when you've installed the first Web Server, SQL Monitor recorded the thumprint of that or...
Yes, it should work Here are more detailed instructions on how to add a second base monitor: https://documentation.red-gate.com/sm/installation-and-setup/multiple-base-monitor-installations/installing-multiple-base-monitors / comments
Yes, it should workHere are more detailed instructions on how to add a second base monitor:https://documentation.red-gate.com/sm/installation-and-setup/multiple-base-monitor-installations/installin...
Hi, I'm afraid that the only way to commit using SQL Source Control is interactively in SSMS, it's not possible to automate commits. Depending on your Version Control System it might be possible to commit to a Working Folder (this part would need to be done manually) and then use that Version Control System's command-line tool to do an automated commit. You might be able to automate further, using the SQL Compare Pro command line: this could allow you to automatically update the Working Folder (you'd still need a third-party tool to interact with the Version Control System). Please note that this option might require a SQL Change Automation license. Kind Regards, / comments
Hi,I'm afraid that the only way to commit using SQL Source Control is interactively in SSMS, it's not possible to automate commits.Depending on your Version Control System it might be possible to c...
Hi Peterpj, All that should be possible using our tools. You should start by migrating the schema, you can use SQL Compare for this task. If you want to make the schema in the target 100% identical to the source, this should be straightforward: usually it's just a case of comparing, making sure that all objects are selected for deployment and then deploying. Please note that if you are using default options, a different column order in a table, by itself, will not cause SQL Compare to consider the source and target different, so if column order is important, you should enable the "Force Column Order" option in the project options. If you don't want to drop any tables that only exist on the target, you can do so quickly, by unticking the tables correct group in the Comparison screen:[image] [image] SQL Compare and SQL Data Compare map tables automatically using the table name, however you can override this . Kind Regards, / comments
Hi Peterpj,All that should be possible using our tools.You should start by migrating the schema, you can use SQL Compare for this task.If you want to make the schema in the target 100% identical to...