Re: Transformable v. regular subscriptions

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




.

Relevant Pages

  • Re: Date problem with mail merge Word 2002
    ... > a hotfix from MS Support, or modify the way that you were transferring ... >> a mail merge document using Word 2002 on my clients PC. ... >> format and blank date data is not shown. ... >> Microsoft Word 11.0 Object library as the reference setting. ...
    (microsoft.public.word.mailmerge.fields)
  • Re: Transferring an instance of an Object with OLEDragDrop
    ... I have gone with just transferring text. ... > - You aren't guaranteed to get the exact data back from the byte array ... The settings for format are: ... Private Sub List1_OLEStartDrag(Data As DataObject, ...
    (comp.lang.basic.visual.misc)
  • Re: Archiving genealogy records
    ... It is nice to say to keep transferring your data to the latest format, ... Currently researching LEE and BEDFORD families from Islington ...
    (soc.genealogy.britain)
  • Re: HHEELLPP!!!!!
    ... Can you be a bit more explicit about what happens when you try to install BK ... There's an outside chance that it may save the data in Gedcom format (or you ... understood by many different genealogy programs - so you would be able to ... I did have difficulty transferring it to ...
    (soc.genealogy.britain)