Comments
3 comments
-
Hello,
I am having trouble replicating this issue. In every case I can find, SQL Prompt 5.3 drops and recreates the foreign key rather than disabling it. Or is this actually a check constraint with "FK" in the name?
If you can script up a quick reproduction of this particular environment and email it to support@red-gate.com, I'd be happy to have a look. -
Thank you again Red Gate for inadvertantly revealing a problem with a database.
While compiling some scripts to send you, I noticed that the constraint is scripted as disabled by SSMS as well. Apparently, someone disabled this constraint at some time in the past and never enabled it again. :x
I doubt I would have ever noticed this if not for your scripting tools summary, where it finished withPRINT N'Disabling constraints on ...'
.
Problem solved.
Thanks again,
Wes -
Hello Wes,
Thanks for following up. I'll deactivate the support issue.
Add comment
Please sign in to leave a comment.
Shouldn't this be instead?
My preference would be to validate existing data as well, but I understand that cannot work as a default.