Comments
Sort by recent activity
Hello,
I'm sorry to hear you're hitting a problem!
Have you managed to successfully compare these two databases before you started seeing this error? If so, has anything changed recently in the schema? / comments
Hello,
I'm sorry to hear you're hitting a problem!
Have you managed to successfully compare these two databases before you started seeing this error? If so, has anything changed recently in the sch...
Hello,
Our apologies for the problem you've encountered.
'SSMS Integration Pack' appears as a separate product to SQL Compare. Please can you try uninstalling 'SSMS Integration Pack Framework' (and if you have it installed 'SSMS Integration Pack') and checking whether you still see a problem? / comments
Hello,
Our apologies for the problem you've encountered.
'SSMS Integration Pack' appears as a separate product to SQL Compare. Please can you try uninstalling 'SSMS Integration Pack Framework' (and...
Hi all, The latest SQL Search version (v 3.2.2) released today should now support Azure AD authentication. / comments
Hi all,The latest SQL Search version (v 3.2.2) released today should now support Azure AD authentication.
Hi Gerardo,
I'm sorry to hear you're hitting this problem!
You are correct in your understanding how the filters work. Setting Options.Default.Plus(Options.IgnoreUsers, Options.IgnoreUserProperties) should indeed ignore any Users and UserProperties differences. I have raised an internal bug report CSD-220 for investigation; we shall update you when we have made any progress.
Again, sorry you encountered this!
Thanks,
Asha / comments
Hi Gerardo,
I'm sorry to hear you're hitting this problem!
You are correct in your understanding how the filters work. Setting Options.Default.Plus(Options.IgnoreUsers, Options.IgnoreUserProperties...
Hello,
SQL Compare should indeed either drop the existing index before creating the new one, or alter the existing one. Could you check the project options you are using to make sure you don't have the "Ignore indexes" option set and let us know if that's solved your problem?
Thanks,
Asha / comments
Hello,
SQL Compare should indeed either drop the existing index before creating the new one, or alter the existing one. Could you check the project options you are using to make sure you don't have...
Ah I see what you mean now. I've tried to replicate but I am seeing the constraint with the default value correctly picked up in the target column. What version of SQL Compare are you running? If you upgrade to the latest version (under Help --> Check for updates) do you still see the same problem?
If you're still hitting the problem could you please email support@red-gate.com; someone will be in touch to investigate further and try to resolve this.
Thanks,
Asha / comments
Ah I see what you mean now. I've tried to replicate but I am seeing the constraint with the default value correctly picked up in the target column. What version of SQL Compare are you running? If y...
Hello,
Sorry to hear you're hitting a problem!
I'm having some trouble reproducing the issue you mentioned. Did you mean your source column is
[PublicHousing] [bit] NOT NULL CONSTRAINT [DF_Interview_PublicHousing] DEFAULT ((0))
and your target column is
[PublicHousing] [bit] NOT NULL
?
I have tried a deployment like this and I can see Compare correctly creating the constraint:
PRINT N'Adding constraints to [dbo].[table]'
GO
ALTER TABLE [dbo].[table] ADD CONSTRAINT [DF_Interview_PublicHousing] DEFAULT ((0)) FOR [PublicHousing]
GO
I don't understand how this is failing due to the named constraint already existing, as the named constraint doesn't exist in the target column. Am I misunderstanding something?
Thanks,
Asha / comments
Hello,
Sorry to hear you're hitting a problem!
I'm having some trouble reproducing the issue you mentioned. Did you mean your source column is
[PublicHousing] [bit] NOT NULL CONSTRAINT [DF_Intervie...
Hi,
Sorry you're having this problem!
This error is thrown whenever a duplicated definition is found that is not solely due to case sensitivity (for instance, definitions for 'UserName' and 'username' would throw a different error). Could you check inside the file 'Scripts.Sql' and see if it has a different definition for 'UserName' defined in there?
If this isn't the case we'd need to look into this further; could you contact support@red-gate.com and attach the scripts you are using to compare against the database, and we shall investigate further.
Thanks,
Asha / comments
Hi,
Sorry you're having this problem!
This error is thrown whenever a duplicated definition is found that is not solely due to case sensitivity (for instance, definitions for 'UserName' and 'userna...
Hello,
Thank you for your question! Unfortunately we currently don't support scripting merges or deletes for each insert. However this idea has been raised before on our uservoice channel (https://redgate.uservoice.com/forums/147879-sql-data-compare/suggestions/2795870-add-if-not-exists-to-data-compare) and has gained a lot of votes so we are aware of the interest surrounding this use case. Please feel free to add your vote to any ideas (or post your own) that you think will improve the product.
Thanks,
Asha / comments
Hello,
Thank you for your question! Unfortunately we currently don't support scripting merges or deletes for each insert. However this idea has been raised before on our uservoice channel (https://...
Hi Imran,
Sorry to hear you're hitting this problem. This is actually a warning message instead of an error letting you know sql server does not allow full-text indexes to be deployed in transactions. There is some extra text to the warning message recommending you select the 'Do not use transactions in deployment scripts' project option when deploying full-text indexes, however it seems you've found a separate bug where our message display textbox is trimming the text; if you enlarge the window with the warning message you should be able to read the rest of the text, but we shall certainly fix that going forward.
Would you mind selecting the 'Do not use transactions in deployment scripts' project option and see if your deployment scripts are now created without any warnings?
Thanks,
Asha / comments
Hi Imran,
Sorry to hear you're hitting this problem. This is actually a warning message instead of an error letting you know sql server does not allow full-text indexes to be deployed in transactio...