transactional replication) from behind the firewall to our DMZ. This seems
to be the ideal way to do this, however I'm having a strange problem.
I've set filter rows for most all of the tables I'm replicating out, since I
only need a small fraction of the data. I have one table called
OPPORTUNITY_CONTACT which is just an association table between the
OPPORTUNITY table and the CONTACT table.
The filter row SQL is:
SELECT <published_columns> FROM
[SYSDBA].[OPPORTUNITY_CONTACT] WHERE OpportunityID IN
(SELECT OPPORTUNITYID FROM SYSDBA.OPPORTUNITY
WHERE TrackLeadYN = 'T')
Because (obviously) the filter row for the Opportunity table is based on
that flag being set.
That being said, a new or edited record shows up in the replicated table
almost immediately, but the record in the OPPORTUNITY_CONTACT table does
not. If I run the above query in Query Analyzer, it shows me the records I
need, so it's a replication issue or setting, not data missing, etc.
Can I not use the SELECT IN clause to limit rows based on another table?
When I created the replication, it brought over all the correct rows at the
time, but updates don't seem to come over. It is throwing no error, alert,
or conflict.
Any thoughts or help on this would be greatly appreciated!
Josh
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
