Comments
Sort by recent activity
Thank you both for your replies. Pushing all the branches through our DevOps process does indeed seem to solve this, although I have not finished thinking this through. For example, suppose branch Issue1 is pushed into our Test environment and is approved for Production. Do we just deploy that branch, or do we go back and merge the changes into master and repeat the Test/Production cycle? Either way this will require some coordination between developers but that is the case even without an automated DevOps solution. / comments
Thank you both for your replies. Pushing all the branches through our DevOps process does indeed seem to solve this, although I have not finished thinking this through. For example, suppose branch ...
@Jessica R Thanks for your reply. After I saw this I realized that although I upgraded from DLM Automation to SQL Change Automation on our build server, our PowerShell script was still running the old DLM cmdlets. Once I changes to the new versions everything started working. / comments
@Jessica R Thanks for your reply. After I saw this I realized that although I upgraded from DLM Automation to SQL Change Automation on our build server, our PowerShell script was still running the ...
That worked. Thanks! / comments
That worked. Thanks!
Thank you for your question but this issue was resolved through a support ticket. The solution was to run the version of SQLCompare that appears in the DLM Automation folder. This does not require a logged in user for license validation. / comments
Thank you for your question but this issue was resolved through a support ticket. The solution was to run the version of SQLCompare that appears in the DLM Automation folder. This does not require ...
Mikiel, Thanks for your reply. Our big issue was that branching is too slow and difficult under TFS, but we are moving to Git and hope to develop a good branching strategy going forward. Regards, Tom / comments
Mikiel,Thanks for your reply. Our big issue was that branching is too slow and difficult under TFS, but we are moving to Git and hope to develop a good branching strategy going forward.Regards,Tom
This turned out to be missing DLLs on the developer's machine. We worked around this by installing Visual Studio 2013. / comments
This turned out to be missing DLLs on the developer's machine. We worked around this by installing Visual Studio 2013.
This turned out to be a configuration error in my CI step. IgnoreUsersPermissionsAndRoleMemberships is the default. After changing this all is well. / comments
This turned out to be a configuration error in my CI step. IgnoreUsersPermissionsAndRoleMemberships is the default. After changing this all is well.
I believe I sorted this out. The solution (obvious now) is to do the schema validation in a database instance that includes the external dependencies. / comments
I believe I sorted this out. The solution (obvious now) is to do the schema validation in a database instance that includes the external dependencies.
David,
Thank you for this. I am not sure how this happened because I did use the installer, but I installed the .Net Framework using the link provided and the problem is solved.
Tom / comments
David,
Thank you for this. I am not sure how this happened because I did use the installer, but I installed the .Net Framework using the link provided and the problem is solved.
Tom
Thanks Alex! I should have figured that out. Installing the tSQLt objects in the Dev database and committing them to source control did the trick. / comments
Thanks Alex! I should have figured that out. Installing the tSQLt objects in the Dev database and committing them to source control did the trick.