Character conversion table

Hi,
I have been told a conversion table exist in either the master or the msdb
database which can do a character conversion of data before it is sent to a
subscriber. I am not not talking about character set conversion but about
the ability to modify named characters into another named character, e.g.
chr(10)+chr(13) into chr(13).
Does anybody know of such a table? I haven not been able to locate it.
Cheers
/Christian
its in the msdb database and its called MSdatatype_mappings. However, this
doesn't really do what you are looking for. Its pure datatype mappings, ie a
datatype in SQL Server to a datatype in access.
Query this table to get an idea of what it actually does.
I think what you want to do is to use a DTS transform to carry this form of
conversion out.
What type of a database are you replicating to?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Christian Dam" <badeanden@._no_spam_hotmail.com> wrote in message
news:ex8Mr%23aiEHA.2848@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I have been told a conversion table exist in either the master or the msdb
> database which can do a character conversion of data before it is sent to
a
> subscriber. I am not not talking about character set conversion but about
> the ability to modify named characters into another named character, e.g.
> chr(10)+chr(13) into chr(13).
> Does anybody know of such a table? I haven not been able to locate it.
> Cheers
> /Christian
>
|||Yep, I know the MSdatatype_mappings but unfortunately that's not the one I
was looking for. Your reply, however, have finally convinced me that table I
was told existed, actually do not exist.
For a customer we have set up a replication from SQL Server 2000 to DB2.
Originally the DB2 was located on Windows and everything worked fine. The
customer then moved DB2 to AIX resulting in the line feed characters got
transferred incorrectly, I'm guessing because of the differences between NT
and AIX (the LFCR vs. CR thingy).
Unfortunately I don't have much additional information. It could look like a
ODBC configuration problem, but we don't even know if it is a line feed
characters are transferred incorrectly if it appears within normal row data.
We are using the IBM DB2 ODBC driver version 7.01.00.88.
Thanks
/Christian
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:%23$LROydiEHA.2764@.TK2MSFTNGP11.phx.gbl...
> its in the msdb database and its called MSdatatype_mappings. However, this
> doesn't really do what you are looking for. Its pure datatype mappings, ie
a
> datatype in SQL Server to a datatype in access.
> Query this table to get an idea of what it actually does.
> I think what you want to do is to use a DTS transform to carry this form
of[vbcol=seagreen]
> conversion out.
> What type of a database are you replicating to?
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Christian Dam" <badeanden@._no_spam_hotmail.com> wrote in message
> news:ex8Mr%23aiEHA.2848@.TK2MSFTNGP10.phx.gbl...
msdb[vbcol=seagreen]
to[vbcol=seagreen]
> a
about[vbcol=seagreen]
e.g.
>
|||I know some people who are replicating to DB2 on AIX and are using IBM's
Open Direct (IIRC) driver to do so.
I am curious as to how you/they got the data from DB2/NT to DB2/AIX. Perhaps
something was translated incorrectly in this process.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Christian Dam" <badeanden@._no_spam_hotmail.com> wrote in message
news:eHj7TCeiEHA.140@.TK2MSFTNGP12.phx.gbl...
> Yep, I know the MSdatatype_mappings but unfortunately that's not the one I
> was looking for. Your reply, however, have finally convinced me that table
I
> was told existed, actually do not exist.
> For a customer we have set up a replication from SQL Server 2000 to DB2.
> Originally the DB2 was located on Windows and everything worked fine. The
> customer then moved DB2 to AIX resulting in the line feed characters got
> transferred incorrectly, I'm guessing because of the differences between
NT
> and AIX (the LFCR vs. CR thingy).
> Unfortunately I don't have much additional information. It could look like
a
> ODBC configuration problem, but we don't even know if it is a line feed
> characters are transferred incorrectly if it appears within normal row
data.[vbcol=seagreen]
> We are using the IBM DB2 ODBC driver version 7.01.00.88.
> Thanks
> /Christian
>
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:%23$LROydiEHA.2764@.TK2MSFTNGP11.phx.gbl...
this[vbcol=seagreen]
ie
> a
> of
> msdb
> to
> about
> e.g.
>
|||Unfortunately it is not option to change the drivers. We are stuck with
what's already installed. (The customer have VERY strict change management
processes in place)
I don't know how the data was transferred to DB2/AIX, but the problem we are
facing now is concerned with new data originating from SQL Server. Any old
data is not affected. However, I doubt if the customer changed any of the
replication settings when they made the switch.
Cheers
/Christian
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:ODyoLGeiEHA.2992@.TK2MSFTNGP12.phx.gbl...
> I know some people who are replicating to DB2 on AIX and are using IBM's
> Open Direct (IIRC) driver to do so.
> I am curious as to how you/they got the data from DB2/NT to DB2/AIX.
Perhaps[vbcol=seagreen]
> something was translated incorrectly in this process.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Christian Dam" <badeanden@._no_spam_hotmail.com> wrote in message
> news:eHj7TCeiEHA.140@.TK2MSFTNGP12.phx.gbl...
I[vbcol=seagreen]
table[vbcol=seagreen]
> I
The[vbcol=seagreen]
> NT
like[vbcol=seagreen]
> a
> data.
> this
mappings,[vbcol=seagreen]
> ie
form[vbcol=seagreen]
the[vbcol=seagreen]
sent[vbcol=seagreen]
it.
>