Data Versioning Transactional Replication

Hi,
I've got a requirement to know when some data has been propagated to
all my (read-only) subscribers. This is because the data will be
cleaned, and the subscribers shouldn't "use" the new version for
certain queries until I know that the new data is there.
I've created a model where I have a "version" table with an identity,
that gets updated by the log reader every time it reads. I check the
version at the time the data changes are finished. Then, when i save
the version with the query that i want to run at the subscriber, and
wait until the version number is greater than or equal to my version
number.
This model seems to work, it requires me to add some steps to the
distribution job, but I'm wondering if there is a better way? Ie,
some form of replication that doesn't require me to custom code the
versioning scheme of the data.
Thx,
Doug
If the data is updated on the publisher in discrete batches you can always
wait for the distribution agent to complete. Other than that the scheme you
have implemented sounds like the best way to go. SQL 2005 will have tracer
tokens that might help with your requirement.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Douglas Tarr" <douglas.tarr@.gmail.com> wrote in message
news:c33eac8b.0409070825.1654dcb3@.posting.google.c om...
> Hi,
> I've got a requirement to know when some data has been propagated to
> all my (read-only) subscribers. This is because the data will be
> cleaned, and the subscribers shouldn't "use" the new version for
> certain queries until I know that the new data is there.
> I've created a model where I have a "version" table with an identity,
> that gets updated by the log reader every time it reads. I check the
> version at the time the data changes are finished. Then, when i save
> the version with the query that i want to run at the subscriber, and
> wait until the version number is greater than or equal to my version
> number.
> This model seems to work, it requires me to add some steps to the
> distribution job, but I'm wondering if there is a better way? Ie,
> some form of replication that doesn't require me to custom code the
> versioning scheme of the data.
> Thx,
> Doug

Data Transformation in Transactional Replication

I already put this set of questions to another group and oly one person
replied. I would appreciate if other people can share their opinion as well.
Thanks
=====================
I have a transactional replication set up from one system to another.
Subscriber has only read mode on data (Uni-directional Replication). I need
to do lots of transformation in the data while replication from Publisher to
Subcriber Like adding the same record in the other table as well or do some
denormalization etc.
Which route should I choose?
1. Modify Replicaiton procedures to have this business rule in-built.
2. Should I create indexed views and other tables on reporting server.
3. Should I create trigger on the reporting server and have the replication
procedure only do the insert and trigger do rest of the business rules
implementaion.
4. Can reporting services be used for such a transformation.
5. Should I have DTS as a part of replication.
-Nitin
Perhaps you should call PSS and get their input.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Now available on Amazon.com
http://www.amazon.com/gp/product/off...?condition=all
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Nitin" <Nitin@.discussions.microsoft.com> wrote in message
news:A2EE86E0-024D-4E1D-9051-6144C65B310F@.microsoft.com...
> I already put this set of questions to another group and oly one person
> replied. I would appreciate if other people can share their opinion as
well.
> Thanks
> =====================
> I have a transactional replication set up from one system to another.
> Subscriber has only read mode on data (Uni-directional Replication). I
need
> to do lots of transformation in the data while replication from Publisher
to
> Subcriber Like adding the same record in the other table as well or do
some
> denormalization etc.
> Which route should I choose?
> 1. Modify Replicaiton procedures to have this business rule in-built.
> 2. Should I create indexed views and other tables on reporting server.
> 3. Should I create trigger on the reporting server and have the
replication
> procedure only do the insert and trigger do rest of the business rules
> implementaion.
> 4. Can reporting services be used for such a transformation.
> 5. Should I have DTS as a part of replication.
> -Nitin

Data Transformation in Replication

I have a transactional replication set up from one system to another.
Subscriber has only read mode on data (Uni-directional Replication). I need
to do lots of transformation in the data while replication from Publisher to
Subcriber Like adding the same record in the other table as well or do some
denormalization etc.
Which route should I choose?
1. Modify Replicaiton procedures to have this business rule in-built.
2. Should I create indexed views and other tables on reporting server.
3. Should I create trigger on the reporting server and have the replication
procedure only do the insert and trigger do rest of the business rules
implementaion.
4. Can reporting services be used for such a transformation.
5. Should I have DTS as a part of replication.
-Nitin
1. Yes, these procs will be whacked the next time you do a reinitialization.
Make sure you uncheck the Create the stored procedures during the initial
synchronization of subscriptions option. This is possibly the preferred way
to go.
2. This is another option. However Indexed Views may not be able to do
everything you need. Indexed Views are less complex to set up than custom
stored procedures. Indexed Views are best used on EE, as opposed to standard
as their indexes won't be included in the query plans query optimizer
generates on standard.
3.No, No, No, No, No. You will find that triggers will slow down the
performance of the replication stored procedures. Your latency will increase
many fold.
4. I believe so, however, replication processes may be better tuned for this
this. I think this will be the case only if you replicate the execution of
stored procedures.
5. No, for performance reasons. Use DTS when you have to modify the data en
route to heterogeneous subscribers.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Now available on Amazon.com
http://www.amazon.com/gp/product/off...?condition=all
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Nitin" <Nitin@.discussions.microsoft.com> wrote in message
news:1C92DDBA-5FC5-4910-B022-A87A7C75466D@.microsoft.com...
> I have a transactional replication set up from one system to another.
> Subscriber has only read mode on data (Uni-directional Replication). I
need
> to do lots of transformation in the data while replication from Publisher
to
> Subcriber Like adding the same record in the other table as well or do
some
> denormalization etc.
> Which route should I choose?
> 1. Modify Replicaiton procedures to have this business rule in-built.
> 2. Should I create indexed views and other tables on reporting server.
> 3. Should I create trigger on the reporting server and have the
replication
> procedure only do the insert and trigger do rest of the business rules
> implementaion.
> 4. Can reporting services be used for such a transformation.
> 5. Should I have DTS as a part of replication.
> -Nitin