Over the next few days we are going to start the migration to a new forum
application. I'm going to start with high post count and active users. You may
receive an invitation to the new forums. It's not spam. It's just me trying to
seed the user base. My goal is to open it up over the weekend.
Once we open the site we'll block registrations here. We should be open
shortly on the new site.
After running those, I still had a few tables left due to errors: Could not drop object 'table_blah' because it is referenced by a foreign key constraint
Interesting, I thought I disabled all of those... Upon further investigation I found this command which would generate the alter table statements for whatever foreign keys existed for my specified table: SELECT 'ALTER TABLE ' + OBJECT_NAME(parent_object_id) + ' DROP CONSTRAINT ' + name FROM sys.foreign_keys WHERE referenced_object_id = object_id('table_blah') It generated two Alter table statements for me which I tried to run: ALTER TABLE table_blah DROP CONSTRAINT FK_table_other_contact And I received this error: Cannot find the object "table_other" because it does not exist or you do not have permission
Ummm.... That's because table_other was deleted with the majority of the rest of db1 when I ran the first two statements. How can a foreign key constraint exist from a table which no longer exists? More importantly, how can I drop that foreign key constraint when the table it belongs to no longer exists??
Another minor update, upon querying Sys.Objects for objects LIKE table_blah, I have received a list which has several default constraint objects, foreign key constraint objects, a primary key constraint object, and still the table itself despite no longer being visible in the tree structure and despite my not being able to view it using a select statement