Re: Transformable v. regular subscriptions
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Fri, 12 May 2006 12:56:02 -0400
Have a look at a custom sync object. I think this will do what you are
looking for.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"Oskar" <Oskar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:695F66D2-B2E6-4835-ACB2-5DFC29571F4D@xxxxxxxxxxxxxxxx
I use transformable subscriptions and the accompanying character format of
snapshots, because, as far as I can see, that's the only way I can "tell"
the
snapshot agent to skip the columns that aren't present in the publication
database while data is copied in bulk into the respective table in the
subscription database. If the snapshot agent of the transactional
replication
could use the format file in the same way the bcp utility does it, I'd
stick
with the native format of snapshots, but since it doesn't I'm left with
only
the character format. Is the character format the same as the native
format
in respect of transferring the exact copy of published data to the
subscription database? Can you think of any issues, for example, when
transferring data stored using a very outdated codepage ?
-- Many thanks, Oskar
"Hilary Cotter" wrote:
Transformable Subscriptions use a DTS package to transform the data as it
moves from the Publisher to the Subscriber. It is intended to transform
the
data when it goes to heterogeneous subscribers. It has been deprecated in
SQL 2005. If you need to transform the data for SQL Server subscribers
you
are better to use custom stored procedures.
To answer your question, I take it that you are able to use the DTS
package
code outside of the publication and it does not lose data. If so, you
should
not be loosing data while using transformable subscriptions. You can
always
log to a table where the DTS package runs for debugging purposes.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"Oskar" <Oskar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9839B177-4F0D-4C95-9E92-310B9288EE5C@xxxxxxxxxxxxxxxx
Forgot to mention that the data in the publication database for the
transactional replication is stored using a legacy multilingual DOS
codepage,
which is mapped to a single codepage that can be recognized by the SQL
Server
software on the servers.
"Oskar" wrote:
Hi,
Tell me please, is there any chance to lose or get altered data in a
susbcription database if the character mode format of snapshots and
transformable subscriptions are used in the transactional replication
that
was set up between MS SQL Server 2000 SP3 servers?
--Many thanks, Oskar
.
- Follow-Ups:
- Re: Transformable v. regular subscriptions
- From: Oskar
- Re: Transformable v. regular subscriptions
- References:
- Re: Transformable v. regular subscriptions
- From: Hilary Cotter
- Re: Transformable v. regular subscriptions
- From: Oskar
- Re: Transformable v. regular subscriptions
- Prev by Date: Re: compensate_for_errors
- Next by Date: Re: Best replication strategy
- Previous by thread: Re: Transformable v. regular subscriptions
- Next by thread: Re: Transformable v. regular subscriptions
- Index(es):
Relevant Pages
|
Loading
