Re: datatype conversion error in sql 2000 replication



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?





.



Relevant Pages

  • Re: datatype conversion error in sql 2000 replication
    ... The bad part is I couldn't find the article on the public microsoft site ... in SQL2000 which is addressed in QFE build 8.00.2209. ... Implicit conversion from data type text to nvarchar is not ... (Source: MYBACKUPSERVER (Data source); Error number: 257) ...
    (microsoft.public.sqlserver.replication)
  • Re: When to use Access ???
    ... A well designed database could go ... The second limitation is that it does not make a good web database. ... Your Resource For Help With Access, Excel And Word Applications ... > Microsoft warns against using it for any production systems. ...
    (microsoft.public.access.gettingstarted)
  • Re: PHsettings.exe not able to be accessed
    ... Microsoft is currently fixing heaps of issues with VoIP and will be ... releasing a QFE soon. ... "DaveF" wrote: ...
    (microsoft.public.windowsce.platbuilder)
  • Re: software raid0/striping on C: ?
    ... has to be accessible on boot phase when only BIOS I/O is available. ... > This limitation indeed exixts within the Redhat/Fedora implementations too ... > Slackware Linux on the other hand SHOWS that it is possible to in fact ... > although I love and prefer Microsoft, and since it's possible because I ...
    (microsoft.public.development.device.drivers)
  • Re: URGENT: Table format slows down document in Word 2003
    ... We have broken the document into smaller tables (not exceeding 50 rows each) ... It would be more effective to have Microsoft build a more powerful Word ... "Jay Freedman" wrote: ... suggestions or this is a limitation in Word, ...
    (microsoft.public.word.tables)

Loading