Comments
Sort by recent activity
abushpg said:
Victoria W said:
Hi all I'm delighted to announce that our tools now support SSMS 20. You can update your Redgate tools here: https://download.red-gate.com/installers/SQLToolbelt/2024-03-28/
The new installer isn't allowing me to proceed. It is allowing me to update SQL Multi Script, but SSMS Integration Pack is not available. On this PC, I started from a fresh Windows installation last week (bad timing). I only installed SSMS 20, and then I installed SQL Toolbelt from installer version 3.4.0.2912, which I downloaded on 3/22/2024. So I don't have a previous version of SSMS or the SSMS Integration Pack installed. [image] [image]
I have this same issue - I am working on a new PC with only SSMS v20 installed - I have grabbed all the latest versions of RedGate SQL Toolbelt installers I can find:
SQLSourceControl_7.7.9.18623 - this does work to install with SSMS v20
SQL ToolBelt Installer version 3.4.0.2912 - this does not allow me to install the SSMS Integration Pack as it states I need an earlier version of SSMS
[image] [image] Is there a version of the SSMS Integration Pack that I can download that will work with SSMS v20? / comments
abushpg said:
Victoria W said:
Hi allI'm delighted to announce that our tools now support SSMS 20.You can update your Redgate tools here:https://download.red-gate.com/installers/SQLToo...
This ended up being an issue related to Git commits. When committing and pushing the changeset, it was adding line terminations. The line terminations are being detected by Redgate SQL Change Automation as a change. Not sure of the internals of how this get detected, but it identified every single programmable object as a change. The workaround for this is to add a .gitattributes file to your project (or use global settings if that is not a problem for your other projects) with the following in it: * -text Problem was resolved after re-creating the project and the repo. This was never an issue with DLM, so it appears that some of the change detection logic is more sensitive. / comments
This ended up being an issue related to Git commits. When committing and pushing the changeset, it was adding line terminations. The line terminations are being detected by Redgate SQL Change Aut...
Another thing that is happening, after I see the "deploy", and hit refresh (above is incorrect, it shows deploy in #12 without hitting refresh, I can't seem to edit above), even if I re-open the project and try, I get a Script Validation Failed error for a programmable object which does not fail up to this point (when building and/pr refreshing, only after it detects a change to deploy), it fails with Invalid Object name, for a table object that exists in the Schema-Model (and is not filtered). / comments
Another thing that is happening, after I see the "deploy", and hit refresh (above is incorrect, it shows deploy in #12 without hitting refresh, I can't seem to edit above), even if I re-open the pr...
@Greg_Smulko - yep thanks, I found it. Thanks for the response! / comments
@Greg_Smulko - yep thanks, I found it. Thanks for the response!
I would also add, if you have PowerShell 5.0 installed this is part of it. Also, you can manually install the SQL Change Automation component from SQL Toolbelt if installing PowerShellGet or upgrading to 5.0 is not an option. / comments
I would also add, if you have PowerShell 5.0 installed this is part of it. Also, you can manually install the SQL Change Automation component from SQL Toolbelt if installing PowerShellGet or upgra...
For what it's worth, if you right mouse click on the DB project in solution explorer, it does NOT do this, but if you use the route Project->DatabaseXYZ Properties it does. Seems like it might be a bug? / comments
For what it's worth, if you right mouse click on the DB project in solution explorer, it does NOT do this, but if you use the route Project->DatabaseXYZ Properties it does.Seems like it might be a ...
Failed to follow-up, latest version fixed issue, thanks. / comments
Failed to follow-up, latest version fixed issue, thanks.
For Visual Studio, I'm using 2017 Professional 15.8.5 which is the latest, and for SSDT, I'm pretty sure that SSDT is not a requirement for RedGate SQL Automation because it's a completely different project type (and it was not installed), but I went ahead and installed Data storage and processing (SSDT is a stand-alone installation, but the recommended integrated installation is Data storage and processing below). No difference. Curious if you looked to see if you see > 1 of these groups also. [image] / comments
For Visual Studio, I'm using 2017 Professional 15.8.5 which is the latest, and for SSDT, I'm pretty sure that SSDT is not a requirement for RedGate SQL Automation because it's a completely differen...
I also ran into this error. Closing VS and creating a new project again with the same settings resulted in it working, so not sure what was causing it. VS and this extension seems to utilize resources more than expected... / comments
I also ran into this error. Closing VS and creating a new project again with the same settings resulted in it working, so not sure what was causing it. VS and this extension seems to utilize reso...