I have a complex query I use to populate reports. I need to move the
reporting environment from actual production database that gets updated
frequently. I have converted the reporting query into a view that pulls
information from many tables with complex joins
In my reporting databases, i have a simple table with the exact fields
in my view.
So here is the situation.
Server A (Live production DB)
Many tables
View - V_abc (with complex joins and returns some columns)
Server B (Reporting Server)
View - V_abc (referencing T_abc with the same exact column on ServerA
view columns)
Table - T_abc (referenced by V-abc with the same column names)
I am trying to set up transactional replicatin (as I need live data) to
pull information from the Production Server A view and insert it into
the reporting Server B db view (V_abc) which will place data to the
underlaying table (T_abc).
I keep getting the error message when I start the replication
"Unable to replicate a view or function because the referenced objects
or columns are not present on the Subscriber. - (Source: AGENT (Agent);
Error number: 00000)"
Its also dropping the View in ServerB.
Is this even posible or am I just chasing ghost..???
I would appreciate some help with this problem...
Paul Ibison - 26 May 2006 20:11 GMT
Why not just replicate the table information itself as normal and manipulate
what the report server can access by using views on this end?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
Query Builder - 26 May 2006 20:21 GMT
Thanks for your response Paul...
In that case, I would have to bring in alot of data that I will not
need. I see some mentiond on one of the other threads about indexed
views? Can anyone help me with that thought?
THanks again...
Paul Ibison - 26 May 2006 21:01 GMT
That was my other thought, but there is always the issue of overhead on the
publisher which could be avoided if you take the whole table. I guess it
depends on how much redundancy we're talking about. Also, the requirements
for the indexed view must be met. If you're happy with this, then definitely
this is the way to go.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
Hilary Cotter - 29 May 2006 15:25 GMT
You can build a custom sync objects and key off one of the tables which
forms the primary key.

Signature
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
>I have a complex query I use to populate reports. I need to move the
> reporting environment from actual production database that gets updated
[quoted text clipped - 30 lines]
>
> I would appreciate some help with this problem...