Added my responses to this article on SQL Server Central today, as we were having exactly the same issue occurring on SQL Server 2008 SP2...
http://www.sqlservercentral.com/articles/Foreign+Keys+(FK)/75346/
The fix we used, was to simply add the DROP_EXISTING = ON option to the creation of the new Index.
No comments:
Post a Comment