all groups > sql server replication > july 2004 >
You're in the

sql server replication

group:

Filtered publication + transactional replication


Filtered publication + transactional replication Hassan
7/13/2004 4:41:37 PM
sql server replication:
Ive got my transactional replication all setup between 2 SQL Servers..

A table from Source A to Dest B has filters defined within a publication ...

i.e select * from tableA where id in (1,5,10)

Now I want to add another id in there in that filtered clause and not
disturb the existing replication thats active. is it possible ?
If so how ?

Re: Filtered publication + transactional replication Paul Ibison
7/14/2004 9:17:33 AM
Hassan,
it is possible by editing the stored procedure that performs the filter. The
name of the procedure will be something like 'FLTR_Tablename_1__52'.
You'll need to edit it using alter procedure statements rather than directly
in EM.
2 Caveats:
this can lead to major difficulties in support, as the filter clause
described in the publication properties will be different from the actual
filter used. At some time in the future you'll need to reinitialize.
the filter is used in the initial snapshot generation, so if you change it
to increase its scope the related rows won't exist on the subscriber.
Regards,
Paul Ibison

Re: Filtered publication + transactional replication Hassan
7/14/2004 4:53:58 PM
Does that mean that everytime data is inserted on the publishing db, these
filtered sprocs get called ? Are these all internal that the profiler
wouldnt pick up the execution of these sprocs ? Also double clicking on
these sprocs within EM gives you an error message something like " the
selected object has been dropped from the database and select refresh to see
the current objects " although i did the refresh..However sp_helptext works,
so Im not complaining.

Will try to give this a try..

[quoted text, click to view]

Re: Filtered publication + transactional replication Paul Ibison
7/15/2004 4:56:02 PM
Hassan,
yes, this is correct - these procs get called each time.
To verify this you can see them in profiler if you monitor for
SP:StatementStarting.
Regards,
Paul Ibison

AddThis Social Bookmark Button