October 12, 2012 at 9:36 am
Have a table Wells_Dundry_Description PK with a Schema-bound dependency to Wells_Sundry FK that needs to be removed.
The Wells_Sundry was a legacy table used before a new replacement table was put in its place.
This was done in MS Access. Using the SQL Server Migration Assistant for MS Access, the table and its old legacy dependcy was migrated over to SQL Server 2008.
Is there code in the Alter Table to drop only the single dependency?
What would be the steps to drop a table, remove the dependency then recreate the table with out loosing the data?
Found:
Dropping Objects
The syntax for dropping most any object is pretty much the same. You cannot drop objects that would render schema-bound dependencies invalid. For example, you cannot drop a table if it is referenced in a dependent foreign key constraint. In this case, you must either drop the related table or alter the table and remove the constraint.
Viewing post 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy