I am setting up a replication of a live server database, published by the live server and subscribed to by a separate server used as a reporting server.
The publication seems to be fine and the subscription does attempt to collect the published information.
My problem is that when the reporting server attempts to update the database it hits tables that have dependencies on a view with schema binding and so fails.
Is there a way to set the replication up so that a schema binded view does not impact the replication? All I can think of at the moment is to have a script running that recreates all the target views to not have schema binding, allow the subscription to run then recreate the views again with schema binding.
Sorry, I am completely new at this so no real knowledge of what I am talking about!
I thought that SCHEMABINDING only applied to the modification of the schema of the view and underlying tables; not the actual data. Are you trying to update the table data via the view? If you do turn off SCHEMABINDING, do the updates finish successfully?
Too often we enjoy the comfort of opinion without the discomfort of thought. - John F. Kennedy