Hi all,
my collaegues were migrating the Solarwinds database to a new SQL Server with a different collation a long while ago, now we would like to adjust the collation of the database to match the one of the server, we think this might be beneficial to the performance.
I do have a script which served well on other products with SQL databases.
The script is basically doing the following:
- Back up all constraints in the database
- Drop all constraints in the database
- Alters collation
- Recreates constraints
However if I let it run against the Solarwinds database I get the error that it can't recreate the constraints:
Msg 1776, Level 16, State 0, Line 1
There are no primary or candidate keys in the referenced table 'dbo.StatusCalculators' that match the referencing column list in the foreign key 'FK_Containers_StatusCalculators'.
Msg 1750, Level 16, State 0, Line 1
Could not create constraint. See previous errors.
When I check the constraint in the "old" database it is there, and I do not see a reason why it should not be possible to recreate it.
I will open a Case with Support, maybe they can help, but if anyone has an idea, I'll be more than glad to hear those.
Thanks
Holger