Comments
Sort by recent activity
Hello @rdaunce, Thanks for sharing your feedback. I've confirmed that running /MakeScripts just creates a copy of the source. Essentially copying the scripts folder and pasting yields the same results. If you do decide to upgrade to a later version of SQL Data Compare, /MakeScripts will no longer create copies of the file as you've noted. Although, the workaround is to run a copy command or manually copying the directory over. Please don't hesitate to let me know if you have any questions or concerns. Kind regards, David Dang Support Engineer / comments
Hello @rdaunce,Thanks for sharing your feedback.I've confirmed that running /MakeScripts just creates a copy of the source. Essentially copying the scripts folder and pasting yields the same result...
Hello @rdaunce, Thanks for your patience. As a quick follow up, I've confirmed with our development team that the old SqlDataCompare.exe /makescripts would have created a copy of the original folder and changes to the command line in later versions has likely caused a regression in this functionality. Is there a specific use case for this as it seems like copying the folder would be equivalent to the old /makescripts? In addition, I hope the workaround of either copying the folder or using an older version of SQL Data Compare would work for you. Please don't hesitate to reach out if you have any other questions. Kind regards, David Dang Product Support Engineer / comments
Hello @rdaunce,Thanks for your patience. As a quick follow up, I've confirmed with our development team that the old SqlDataCompare.exe /makescripts would have created a copy of the original folder...
Hello @rdaunce, Unfortunately, I was not able to reproduce this issue on my end. When running the /MakeScripts option with SQL Data Compare, does the directory contain any object creation scripts or does it create an empty directory? Does the directory contain any newly created files while SQL Data Compare is running from command line? If you add /LogLevel:Verbose, this will generate a log file at C:\Users\<user name>\AppData\Local\Red Gate\Logs\SQL Data Compare that may provide answers as to why the scripts are not created. Can you please send over this log file? Kind regards, David Dang Product Support Engineer / comments
Hello @rdaunce,Unfortunately, I was not able to reproduce this issue on my end. When running the /MakeScripts option with SQL Data Compare, does the directory contain any object creation scripts or...
Hello @davidf, Thanks for your question. Depending on the operations that are being performed by the script we may need to drop and recreate indexes or constraints. If you can provide an example, I may be able to provide more information on why specifically in your case this is occurring. Thank you, David Dang Product Support Engineer / comments
Hello @davidf,Thanks for your question. Depending on the operations that are being performed by the script we may need to drop and recreate indexes or constraints. If you can provide an example, I ...
Hi @davidf, SQL Compare can only create deployment scripts using a source against a target. If you are able to run a comparison between your database (source) and your customer's database (target), then you should be able to create a deployment script that will replace what your customers may have added to the table. I hope this answer helps you out! Don't hesitate to let me know if you have any other questions. Kind regards, David Dang / comments
Hi @davidf, SQL Compare can only create deployment scripts using a source against a target. If you are able to run a comparison between your database (source) and your customer's database (target),...
Hello @davidf, Unfortunately, you can't filter on index differences on SQL Compare. It has to be done on a table level since the indexes are part of the table. If you are okay with deploying all table differences (which would include the indexes), you can deploy "source only" and "in both but different" differences. Kind regards, David David Product Support Engineer / comments
Hello @davidf,Unfortunately, you can't filter on index differences on SQL Compare. It has to be done on a table level since the indexes are part of the table. If you are okay with deploying all tab...
Hello AdrianG, Thanks for your post! SQL Source Control automatically refreshes the list of changes in the commit and get latest tabs. In order to improve performance, you'd have to add in the option yourself to disable auto refresh. For example, your UI Options .xml file might look like: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <!----> <UIOptions version="1" type="UIOptions"> <CloseProgressDialogsOnCompletion>True</CloseProgressDialogsOnCompletion> <ShowTabOnSSMSStart>False</ShowTabOnSSMSStart> <AssemblyVersion>7.2.4.11418</AssemblyVersion> <PostAddToolTipDismissed>True</PostAddToolTipDismissed> <PostConflictInteractiveHelpShown>True</PostConflictInteractiveHelpShown> <PreviouslyLinked>True</PreviouslyLinked> <DisableAutoRefresh>True</DisableAutoRefresh> </UIOptions> I hope this answer helps you out! Don't hesitate to let me know if you have any other questions. / comments
Hello AdrianG,Thanks for your post!SQL Source Control automatically refreshes the list of changes in the commit and get latest tabs. In order to improve performance, you'd have to add in the option...
Hello @theDeveloper, If you were running SQL Prompt 9 (which had support for SSMS 2014, as described here) then updated to SQL Prompt 10 (which does not have support for SSMS 2014, as described here), that might be the reason why the extension is not appearing for you. Please uninstall the existing SQL Prompt, double check to make sure SSMS 18 is already installed, and then reinstall the latest version of SQL Prompt here. I hope this answer helps you out! Please do update me if you are still having any issues. @lorens, Can you provide me with your SSMS and SQL Prompt versions? It sounded like SQL Prompt previously worked for you, can include additional details of when this was no longer the case? Do you still see the SQL Prompt tab inside SSMS? / comments
Hello @theDeveloper,If you were running SQL Prompt 9 (which had support for SSMS 2014, as described here) then updated to SQL Prompt 10 (which does not have support for SSMS 2014, as described here...
Hi @FIRTHRO, Thanks for your post! Can you provide me with your SQL Prompt version? Per our release notes, this was a bug that should have been fixed as of SQL Prompt 10.3.2+. If you are on an older version of SQL Prompt, you can update by selecting SQL Prompt > Help > Check for Updates. I hope this answer helps you - please let me know if it does! Thank you, David Dang Product Support Engineer / comments
Hi @FIRTHRO,Thanks for your post! Can you provide me with your SQL Prompt version?Per our release notes, this was a bug that should have been fixed as of SQL Prompt 10.3.2+. If you are on an older ...
Hi @fpdave100, Thanks for reaching out! You've mentioned SP, are you referencing stored procedure? Also, can you help to clarify what you are trying to achieve with SQL Compare or what is the exact issue? Regarding the command DropAndCreateForReRunnableScripts (Legacy aliases: DropAndCreateInsteadOfAlter), SQL Compare replaces ALTER statements with CREATE or DROP statements so I'm not sure if there will be any impact running against CREATE statements. / comments
Hi @fpdave100,Thanks for reaching out! You've mentioned SP, are you referencing stored procedure? Also, can you help to clarify what you are trying to achieve with SQL Compare or what is the exact ...