Re: datatype conversion error in sql 2000 replication
- From: "Raymond Mak [MSFT]" <rmak@xxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 26 Oct 2006 09:28:12 -0700
The bad part is I couldn't find the article on the public microsoft site
either (otherwise I would have posted the link to the QFE) so you would
probably need to contact Microsoft Support (which I know nobody likes to
do). I will see if I can dig up something.
-Raymond
"archuleta37" <archuleta37@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4E800037-B152-445F-9898-0FB6CB28E161@xxxxxxxxxxxxxxxx
oops, I shouldn't post just before I'm going to bed. I meant to say "that
could be it, it might have too many columns" and in fact it turns out it
does
have too many columns. It has 247 columns - way too many. I tried looking
for
that article again but couldn't find it again - looking forward to reading
it.
"archuleta37" wrote:
That could be it, it might need more columns. I'll check as soon as I get
a
chance. I tried to search for the kb article you reference but got no
results. Could you have a typo in the kb number? Could you post a url to
read
the article?
"Raymond Mak [MSFT]" wrote:
If your table has many columns, you are probably running into a
limitation
in SQL2000 which is addressed in QFE build 8.00.2209. You can either
contact
Microsoft support for the QFE fix (KB923563) or you can upgrade to
SQL2005
which doesn't have this limitation out of the box.
-Raymond
"archuleta37" <archuleta37@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:21837EA5-B4B2-479F-8AF2-D7A42593F3DC@xxxxxxxxxxxxxxxx
Hilary,
I'll have to check to see what I can give you from the schema, but
here's
the last command that sql said it ran:
if (@@microsoftversion >= 0x080002C0) begin exec sp_addsynctriggers
N'PURGED_MGMT_TABLES', N'null', N'DBSERVER', N'Accounting',
N'Accounting',
N'sp_MSsync_ins_PURGED_MGMT_TABLES_1',
N'sp_MSsync_upd_PURGED_MGMT_TABLES_1',
N'sp_MSsync_del_PURGED_MGMT_TABLES_1',
N'sp_MScft_Accounting_PURGED_MGMT_TABLES', N'dbo', N'null', N'null',
N'null',
0x00000010000000000000000000000000000000000000000000000000000000,
0,1,N'DBSERVER', 2 end
Transaction sequence number and command ID of last execution batch
are
0x0001AA3A000001D500D800000001 and 81.
"Hilary Cotter" wrote:
It shouldn't be changing like this, can you post your schema or the
problem
table?
--
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
"archuleta37" <archuleta37@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:F0B915F2-245D-4ECB-AC9D-CA5CA3D16AB6@xxxxxxxxxxxxxxxx
I'm working on setting up replication on a database in SQL 2000
and get
the
following error:
Implicit conversion from data type text to nvarchar is not
allowed. Use
the
CONVERT function to run this query.
(Source: MYBACKUPSERVER (Data source); Error number: 257)
Why would this occur? I don't understand why a field datatype
would
change
when doing replication. More importantly, I have no idea how to
resolve
this
issue and research hasn't helped much. Can anyone give me some
insight
on
where to start to fix this?
.
- References:
- Re: datatype conversion error in sql 2000 replication
- From: Hilary Cotter
- Re: datatype conversion error in sql 2000 replication
- From: Raymond Mak [MSFT]
- Re: datatype conversion error in sql 2000 replication
- From: archuleta37
- Re: datatype conversion error in sql 2000 replication
- From: archuleta37
- Re: datatype conversion error in sql 2000 replication
- Prev by Date: Re: MySQL vs MsSQL on replication
- Next by Date: Re: Merge Replication-Massive Insertion
- Previous by thread: Re: datatype conversion error in sql 2000 replication
- Next by thread: Re: datatype conversion error in sql 2000 replication
- Index(es):
Relevant Pages
|
