Comments
Sort by recent activity
You say "on the second time of deployment".
Have you tried to redeploy the same release against the same DB twice?
You should note that a DlmDatabaseRelease includes a specific upgrade script (in your case, I imagine it inserts some data). If you run the release twice it will try to run that upgrade script twice. This should be caught in the pre-deployment drift check (unless you have disabled it) and the deployment should be aborted.
If you want DLM Automation to generate a script on the fly to just make it match your source you should use the sync cmdlet instead. The idea of a DlmDatabaseRelease is that you can re-use the same deployment script in multiple environments. For example, if you wanted to do a dry-run deployment on a staging or pre-prod DB / comments
You say "on the second time of deployment".
Have you tried to redeploy the same release against the same DB twice?
You should note that a DlmDatabaseRelease includes a specific upgrade script (in y...
Use SQL Compare.
SQL Data Compare deploys the data contained in tables. To deploy the table itself use SQL Compare. / comments
Use SQL Compare.
SQL Data Compare deploys the data contained in tables. To deploy the table itself use SQL Compare.
I'll be there wearing a bright orange helper shirt! Looking forward to seeing everyone. :-) / comments
I'll be there wearing a bright orange helper shirt! Looking forward to seeing everyone. :-)
If the user has a SQL Toolbelt licence - yes. Otherwise no. / comments
If the user has a SQL Toolbelt licence - yes. Otherwise no.
To install tSQLt on a DB, follow these instructions:
If using Redgate SQL Test: https://documentation.red-gate.com/sqt2/adding-a-database-to-sql-test
If not using Redgate SQL Test: http://tsqlt.org/user-guide/quick-start/ / comments
To install tSQLt on a DB, follow these instructions:
If using Redgate SQL Test:https://documentation.red-gate.com/sqt2/adding-a-database-to-sql-test
If not using Redgate SQL Test:http://tsqlt.org/u...
Hi there,
First, a quick question:
Have you added tSQLt on your dev DB and committed it to source control?
If not, the reason you get the error is that when DLMA builds the DB it doesn't have the tSQLt objects (because your source code doesn't have the tSQLt objects) - hence the error.
If you do have the tSQLt objects in source control, are you using a persistent temporary database (i.e. a specific named database using the -TemporaryDatabase parameter) or did you exclude that parameter, allowing DLMA to create a temporary scratch DB for you with a GUID for a name?
If you are using the -TemporaryDatabase parameter, have you set TRUSTWORTHY to ON on that database? TRUSTWORTHY is required to be on in order for tSQLt to work. I believe the cmdlet will deploy tSQLt for you (assuming it's in source control), but tSQLt will only work if the DB has TRUSTWORTHY enabled. If it is not enabled you can get some unintuitive error messages.
To enable trustworthy:
ALTER DATABASE dbname SET TRUSTWORTHY ON;
Note: Do not do this on production. TRUSTWORTHY is a bad idea on production: https://stackoverflow.com/questions/27006432/security-risks-of-setting-trustworthy-on-in-sql-server-2012
Let me know if that helps. / comments
Hi there,
First, a quick question:
Have you added tSQLt on your dev DB and committed it to source control?
If not, the reason you get the error is that when DLMA builds the DB it doesn't have the t...
How's your PowerShell? https://documentation.red-gate.com/clone2/automation/powershell-worked-examples / comments
How's your PowerShell?https://documentation.red-gate.com/clone2/automation/powershell-worked-examples
Fantastic. Just shout if you need any more help. / comments
Fantastic. Just shout if you need any more help.
Follow these instructions: https://documentation.red-gate.com/ddb1/investigating-schema-changes/using-filters / comments
Follow these instructions:https://documentation.red-gate.com/ddb1/investigating-schema-changes/using-filters
I would use branches instead.
I wrote a blog post a little while ago about a format for discussing branching/shelving strategies whilst attempting to avoid flame wars. You may or may not find it useful: http://workingwithdevs.com/branching-reality/ / comments
I would use branches instead.
I wrote a blog post a little while ago about a format for discussing branching/shelving strategies whilst attempting to avoid flame wars. You may or may not find it us...