Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Object cannot be renamed because the object participates in enforced dependencies. Expand / Collapse
Author
Message
Posted Monday, July 22, 2013 11:51 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Tuesday, August 12, 2014 12:04 PM
Points: 727, Visits: 426
Here is the senario... I have multiple copies of a table across several servers. The problem is that these sometimes get out of sync in the data that is inside them.

I have been tasked with replacing these tables with a single copy.

I have made the linked server I need, and i have created the view that is the reference i need.

I have come across the Titled error when attempting to rename, there are 15-20 stored procs and 5-10 views that use the data.

What I want to do is a quick rename, and then a synonym refernce to the view i've created in there. (the view is so developers who use it can still have a reference in the local database w/o having to go to another server to see it and not having to know or care that the table changed)

Is there a quick way to acomplish this or do i need to go in and switch the dependencies to utilize the view and THEN switch it over? I can most certainly do this and fairly rapidly, but was wondering if there was a quick way to turn off the dependency check and get what i want done and then re-enable the checks....

If not, no issue, i can still solve this.
Post #1476172
Posted Monday, July 22, 2013 1:52 PM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Tuesday, August 12, 2014 12:04 PM
Points: 727, Visits: 426
this was a simpler fix than i thought. the object that was complaining was a schema bound object. It didn't need to be bound, and once i corrected that, no other changes were necessary.

now just making sure the various apps that utilize this source work correctly (and they seem to, but better paranoid and checking than caught with pants down)

Post #1476242
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse