Comments
Sort by recent activity
Did you try to follow the other options? Like using online licenses manager?
[...]
1. The license administrator logs in to their account on the Redgate website.
2. On the My Products summary page, click on the product or serial you want to deactivate.
3. On the product detail page the list of identified users is displayed:
[...] / comments
Did you try to follow the other options? Like using online licenses manager?
[...]
1. The license administrator logs in to their account on the Redgate website.
2. On the My Products summary page, ...
Hi @hrudy,
please read here.
In order to deactivate the serials, You can use the tool inside the documentation link.
hope this helps / comments
Hi @hrudy,
please read here.
In order to deactivate the serials, You can use the tool inside the documentation link.
hope this helps
Hi Kazoo60,
are you trying to do so in a default instance SQL Server installation or a named one? In case of named instance, you've to enter (local)\INSTANCENAME. You could try also "." instead of "(local)".
Please try and let us know ;-) / comments
Hi Kazoo60,
are you trying to do so in a default instance SQL Server installation or a named one? In case of named instance, you've to enter (local)\INSTANCENAME. You could try also "." instead of ...
Hi GregDodd,
I know that it could be just a workaround, but you can try to change the tab size. / comments
Hi GregDodd,
I know that it could be just a workaround, but you can try to change the tab size.
hi @itzikpaz,
If I remember right, there is no option in SQL Compare to do so.
I've found this idea in uservoice: https://redgate.uservoice.com/forums/141379-sql-compare/suggestions/6014210-ignore-final-semicolons-when-comparing-stored-proc. You can try to upvote. / comments
hi @itzikpaz,
If I remember right, there is no option in SQL Compare to do so.
I've found this idea in uservoice: https://redgate.uservoice.com/forums/141379-sql-compare/suggestions/6014210-ignore-...
Not right now, but you can upvote for adding the feature. / comments
Not right now, but you can upvote for adding the feature.
Hi @Gadge,
this is how SQL Data Compare could work. Both the same and different networks (two SQL Server instances). The command line, is the application itself. So you need to setup at least in one place the tool.
hope this helps,
ale / comments
Hi @Gadge,
this is how SQL Data Compare could work. Both the same and different networks (two SQL Server instances). The command line, is the application itself. So you need to setup at least in on...
if you're using this, you can setup the following setting:
DLMAutomationDeleteExistingFiles = True
Did you try to change it? / comments
if you're using this, you can setup the following setting:
DLMAutomationDeleteExistingFiles = True
Did you try to change it?
Hi @JDenman,
I didn't get it actually. The DLM Automation is installed where? Have you also a SQL Source Control somewhere or are you using just the DLM Automation for packaging? How this is related to reading the sql file for users and SQL Compare? And what do you mean with "Leave artifacts from SQL Compare"?
I'm really sorry for the questions, but I could not understand, and I'd like to do so, because your pipeline made me curious [image]
The database where your're getting the user from is a dev database? Would you like to notify the dev team or you need to compare users with a test/production environment?
cheers,
ale / comments
Hi @JDenman,
I didn't get it actually. The DLM Automation is installed where? Have you also a SQL Source Control somewhere or are you using just the DLM Automation for packaging? How this is relate...
hi @mortenma71,
the "post deploy" scripts cannot be executed after the data comparison. We had the same requirements in our company and we started to apply migration scripts (feature of Sql Source Control, latest versions). With them, we inject the data creation after (or instead of) some structural change or else adding just a dedicated migration scripts with only data to send to the target environment.
Unfortunately, this solution become not so useful if you're deploying to a multi customer environment, because in that case you need to get a script which is often different for each customer. Additionally, is completely useless if you don't have a Sql Source Control license. In this scenario, you have to make something custom (like a powershell script for comparing and, then, applying scripts) or you can use a deployment tool, like octopus deploy.
If you don't want to buy octopus, Source Control or using PowerShell is not an option, you can let SQL Data Compare create the script for you and, then, append manually the post deploy "INSERTS" to it. So you will execute the generated script instead of comparing via tool.
hope this helps / comments
hi @mortenma71,
the "post deploy" scripts cannot be executed after the data comparison. We had the same requirements in our company and we started to apply migration scripts (feature of Sql Source ...