Comments
Sort by recent activity
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...
Any update on this? It's still extremely slow. Just ran it and it took just over 11 minutes to complete. And, I have pre/post validation removed (because it fails looking for #temp tables created in a stored procedure). / comments
Any update on this? It's still extremely slow. Just ran it and it took just over 11 minutes to complete. And, I have pre/post validation removed (because it fails looking for #temp tables creat...