Comments
Sort by recent activity
I think the problem is around the if ($LASTEXITCODE=63) line - this is actually assigning 63 to the $LASTEXITCODE variable. You probably want to say if ($LASTEXITCODE -eq 63) instead. / comments
I think the problem is around the if ($LASTEXITCODE=63) line - this is actually assigning 63 to the $LASTEXITCODE variable. You probably want to say if ($LASTEXITCODE -eq 63) instead.
I don't think there's a way to do this at the moment, unfortunately. There's an 'Ignore permissions' project option you could set if you wanted to look at fixing the column discrepancies first, but there isn't an inverse option that ignores everything except permissions. / comments
I don't think there's a way to do this at the moment, unfortunately. There's an 'Ignore permissions' project option you could set if you wanted to look at fixing the column discrepancies first, but...
Hi - sorry for the confusion here
The generated scripts you're seeing are the comparison between the two tables similar to the diff panel at the bottom of the comparison results UI. If you want a deployment script, you can use the /scriptfile:<filepath> option for the commandline - see this part of the documentation for more details
You should be able to use the /makebackup option along with other /backup* options to add a backup command to the deployment script / comments
Hi - sorry for the confusion here
The generated scripts you're seeing are the comparison between the two tables similar to the diff panel at the bottom of the comparison results UI. If you want a d...
Hi - sorry to hear you're having trouble with the commandline
I think there could be a couple of things going on here:
Firstly, the regex isn't quite correct, since we're interpreting the commandline option as a .NET regex rather than a glob, so MyDomain* will match things like MyDomai and MyDomain and MyDomainnnnnn. Adding .* at the end would be technically more correct.
However, that probably isn't the issue here, since we only need to match a substring of the user name for it to be excluded anyway. It looks like the line that's failing isn't actually creating a user in the database, but trying to create a server login for the user in case that is necessary. It's probably worth taking a look at the deployment script that the commandline is trying to run using the /scriptfile:<filename> argument - I'm guessing that the part of the deployment script that's failing will look something like this: ...
IF NOT EXISTS (SELECT * FROM master.dbo.syslogins WHERE loginname = N'MyDomain\JoeUser')
CREATE LOGIN [MyDomain\JoeUser] FROM WINDOWS
GO
CREATE USER [Joe] FOR LOGIN [MyDomain\JoeUser]
...
In this case, it's the user Joe that we need to exclude rather than the login [MyDomain\JoeUser], so the commandline arguments would look something more like /exclude:user:Joe in this example / comments
Hi - sorry to hear you're having trouble with the commandline
I think there could be a couple of things going on here:
Firstly, the regex isn't quite correct, since we're interpreting the commandli...
Hi
Sorry, I don't know of any other options which might cause the SQL Data Compare commandline to display an extra window. As far as I know we don't do anything which should cause a window to appear (eg when running in a powershell window, all of the commandline's output goes into powershell and a separate commandline window doesn't appear). Sorry that's not the answer you were looking for [image] / comments
Hi
Sorry, I don't know of any other options which might cause the SQL Data Compare commandline to display an extra window. As far as I know we don't do anything which should cause a window to appea...
Hi - sorry to hear you're having trouble with Data Compare. Unfortunately this looks like a fairly generic crash report with not a lot of information, so this might be a bit hard to track down (exception code c0000005 means ACCESS_VIOLATION in unmanaged memory, which we don't really deal with much since we run almost completely managed .NET code).
There might be some things we can do to track down the source of this error, though. Do you see the same problem when saving projects in SQL Compare? Does repairing the SQL Data Compare installation (through Programs and Features in windows) help? / comments
Hi - sorry to hear you're having trouble with Data Compare. Unfortunately this looks like a fairly generic crash report with not a lot of information, so this might be a bit hard to track down (exc...
Hi - apologies for the lack of information in this part of the UI. We have some long-term plans to try and improve the dependency logic in SQL Compare to display more information about why certain dependencies have been selected (and to allow for more fine-grained control over dependencies) but we don't have anything concrete yet and it may be a long time before we're able to work on it.
However, in the meantime, it might be helpful if you could post the creation scripts for the objects involved - maybe we can help figure out why a dependency has been suggested here (or reproduce the bug if it turns out to be completely erroneous). If you want to keep your database details private you can get in touch with support@red-gate.com who can help figure out a reproduction
Hope that's helpful, / comments
Hi - apologies for the lack of information in this part of the UI. We have some long-term plans to try and improve the dependency logic in SQL Compare to display more information about why certain ...
Hi - sorry to hear you're having problems with SQL Compare
If I understand the problem correctly, near the top of the deployment script there should be some lines like this: (when the user is selected) IF NOT EXISTS (SELECT * FROM master.dbo.syslogins WHERE loginname = N'loginX')
CREATE LOGIN [loginX] WITH PASSWORD = 'p@ssw0rd'
GO
CREATE USER [userX] FOR LOGIN [loginX]
It sounds like the login already exists, so the CREATE LOGIN statement isn't running, but the CREATE USER statement is failing because the login is already assigned to a different user. I think the thing to do is to find this other user that the login is assigned to and deploy that one first, so that the login is freed up to be assigned to the user that you want to deploy.
Hope that's helpful, / comments
Hi - sorry to hear you're having problems with SQL Compare
If I understand the problem correctly, near the top of the deployment script there should be some lines like this: (when the user is selec...
We've just released 12.4.5.4811 which should contain a fix for this problem / comments
We've just released 12.4.5.4811 which should contain a fix for this problem
Hi
Sorry about the confusion here - this was an unintended behaviour change introduced in SQL Compare 12.4.3. We're working on a fix for this at the moment and hope to have a release with the comparison working as expected soon. As a side note, this is just a display issue - the deployment should still do the right thing if you check the deployment script that is produced.
Apologies,
Mark / comments
Hi
Sorry about the confusion here - this was an unintended behaviour change introduced in SQL Compare 12.4.3. We're working on a fix for this at the moment and hope to have a release with the compa...