Comments
Sort by recent activity
For build servers - you will need to use the sqlcompare.exe located in the DLM Automation installation location - typically C:\Program Files (x86)\Red Gate\DLM Automation 2\SC.
DLM Automation is meant to be the build side tool (so it does not ask for an email address when you use it and it can be used by automated processes) - and it is included in the Toolbelt installer available here.
DLM Automation also includes a number of PowerShell cmdlets and CI system plugins (including a plugin for VSTS) which you can use to build and release.
Do let me know if you have any issues with that!
Warmly, / comments
For build servers - you will need to use the sqlcompare.exe located in the DLM Automation installation location - typically C:\Program Files (x86)\Red Gate\DLM Automation 2\SC.
DLM Automation is me...
Hey Ravin,
I recommend using Filters in SQL Source Control to remove Users from the deployment so that they are not dropped - or at least filter out that specific User so that it can deploy successfully.
I hope that helps! / comments
Hey Ravin,
I recommend using Filters in SQL Source Control to remove Users from the deployment so that they are not dropped - or at least filter out that specific User so that it can deploy success...
Hey Bernie,
Thanks for contacting us!
It creates recovery tables when you make a schema change that affects data, such as adding a column in the middle of a table, renaming a table, or changing a data type on a column.
I'd have to see the full deployment script/build log to do a full diagnosis but that is a good starting point.
I'll reach out to you via email for more info.
Kindly, / comments
Hey Bernie,
Thanks for contacting us!
It creates recovery tables when you make a schema change that affects data, such as adding a column in the middle of a table, renaming a table, or changing a d...
Hey Eric,
I've followed up with you for further troubleshooting in Ticket #92996 - I look forward to working with you there!
Warmly, / comments
Hey Eric,
I've followed up with you for further troubleshooting in Ticket #92996 - I look forward to working with you there!
Warmly,
Hey Joakim,
This may be an issue with recognizing nested UDF dependencies - I've reached out to you via email for more info.
Kind Regards, / comments
Hey Joakim,
This may be an issue with recognizing nested UDF dependencies - I've reached out to you via email for more info.
Kind Regards,
Hey Derek,
Thanks for posting!
When you do a build - it creates all of the objects to a created database on the specified SQL Server instance - that sql server instance needs to have all of the cross database and linked server dependencies available or else the build will fail.
Because of that, customers often use a QA or Dev server to do the build - and they have static copies of other databases there so that the build can find all of the required dependencies.
If that is not the issue - would you mind sending in the full build log as well as a screenshot of the build definition?
Kind Regards, / comments
Hey Derek,
Thanks for posting!
When you do a build - it creates all of the objects to a created database on the specified SQL Server instance - that sql server instance needs to have all of the cro...
Hey DLyes,
It looks like my option was only in VSTS - I think you will need to do one class for each run of SQL Test, so that it runs every test in that class - not necessarily one test per run.
I'll ping some colleagues to confirm.
EDIT: Confirmation - the Test step (using the Invoke-DlmDatabaseTests PowerShell cmdlet) in DLM Automation simply uses the tSQLt.Run stored procedure which only accepts one class per run.
This does sound like an excellent candidate for future work, so I recommend you create this idea and vote on our UserVoice page here.
Do let me know if you have any other questions or issues!
Warm Regards, / comments
Hey DLyes,
It looks like my option was only in VSTS - I think you will need to do one class for each run of SQL Test, so that it runs every test in that class - not necessarily one test per run.
I'...
Hey DLyes,
Thanks for contacting us!
There are multiple ways to set this up - if you never want to run certain tests - you can remove them from the database, then commit that change to the repository so that they will never run.
Barring that, you should be able to Link to the "Run only specified class/test" and put in the names of the classes and tests in a comma separated format. [image] [image] [image]
Let me know if you have any issues with that!
Warmly, / comments
Hey DLyes,
Thanks for contacting us!
There are multiple ways to set this up - if you never want to run certain tests - you can remove them from the database, then commit that change to the reposito...
Hey kjmcsd,
Thanks for contacting us!
We have an excellent piece of documentation on this - if that does not help, do let me know.
Warm Regards, / comments
Hey kjmcsd,
Thanks for contacting us!
We have an excellent piece of documentation on this - if that does not help, do let me know.
Warm Regards,
Hey Tom,
Thanks for contacting us!
This is an issue that we have considered, but currently there is no work planned for it.
I recommend you write and post your idea to our Uservoice page.
Do let me know if you have any other issues!
Kind Regards, / comments
Hey Tom,
Thanks for contacting us!
This is an issue that we have considered, but currently there is no work planned for it.
I recommend you write and post your idea to our Uservoice page.
Do let me...