Comments
Sort by recent activity
@Sujay For those still affected by this issue, could you please include the link to download SQL Prompt version 10.4.7. / comments
@Sujay For those still affected by this issue, could you please include the link to download SQL Prompt version 10.4.7.
Just tested SQL Prompt 10.6.2. Result: Visual Studio 2017: Error still present Visual Studio 2019: Appears to load OK - at least enough to appear in the menu. Did not test further before reverting back to version 10.4.7 These tests are done on the same computer. / comments
Just tested SQL Prompt 10.6.2.Result: Visual Studio 2017: Error still present Visual Studio 2019: Appears to load OK - at least enough to appear in the menu. Did not test further before reverting b...
SQL Prompt 10.5.6.17542 still has not resolved the issue [image] / comments
SQL Prompt 10.5.6.17542 still has not resolved the issue
I can confirm that if I revert to version 10.4.7, the problem goes away. / comments
I can confirm that if I revert to version 10.4.7, the problem goes away.
Thanks for the work-around. In my case, data sets are small, and therefore removing and attaching the FK is of little consequence. And I guess this would would generally be true for any data that has been included as Data Tables in SCA I do see it as a work-around - since the automatically generated script generated by SCA did not work, and failed it's own verification. I consider this a fairly trivial case. Data2 depends on Data1. (Directly in this case with a FK relationship). Data1 has no dependencies on Data2. => Generate new Data1 records before applying updates to Data2 I was not expecting this to be beyond the compare engine used by SCA. / comments
Thanks for the work-around. In my case, data sets are small, and therefore removing and attaching the FK is of little consequence. And I guess this would would generally be true for any data that...
Since there have been no other comments, I guess it's fairly safe to assume that I'm the only one experiencing this. I try again, assuming it's something on my side .... / comments
Since there have been no other comments, I guess it's fairly safe to assume that I'm the only one experiencing this. I try again, assuming it's something on my side ....
MayaMalakova said:
TheoL said:
Does this mean those on Toolbelt Essentials essentially lose this functionality completely (for new projects)?
We left a backdoor for those that really want to continue using it - you can set AlwaysEnableMigrationsPage to True in the UI options in %LOCALAPPDATA%\Red Gate\SQL Source Control 7\RedGate_SQLSourceControl_CommonUI_UIOptions.xml
Unless the feature actively maintains inter-operability with future versions of SQL Compare and SQL Change Automation, then this is only a temporary solution. / comments
MayaMalakova said:
TheoL said:
Does this mean those on Toolbelt Essentials essentially lose this functionality completely (for new projects)?
We left a backdoor for those that reall...
Does this mean those on Toolbelt Essentials essentially lose this functionality completely (for new projects)? / comments
Does this mean those on Toolbelt Essentials essentially lose this functionality completely (for new projects)?
@DanC I have found the cause: For performance, I use "Only load suggestions for certain databases/schemas" option. My freshly installed SQL Express 2017 was not in the list. The fact it was SQL Express 2017 was not related to the cause. It turns out the if the database is not included in the server/database list for connections, then the Find Invalid Objects does not work. It would be a sensible UI enhancement to notify the user that this is the case instead of allowing the attempt, then just showing a progress bar that appears to get stuck at about 10%. / comments
@DanC I have found the cause:For performance, I use "Only load suggestions for certain databases/schemas" option. My freshly installed SQL Express 2017 was not in the list. The fact it was SQL Ex...