SQL2000 ? Make the user DDL-admin in stead of DB_owner. Look at BOL.

Thanks to implicit conversions. Rule 4 never thrust a default-behaviour. And it strikes when you don't expect it.

try it with substring(text,1,case when len(text) > your_max_length then your_max_length else len(text) end.

If you don't like bulk-insert, you can minimize logging with simple-recovery-setting (sql2k) or truncate-log-on-checkpoint (sql7) when using small transactions. This means you have to chop up your input in chuncks...

Take a look at sqlserver books online (BOL).

db_datawriter can update all tables in the databasen, except is that user has been denied write rights. look at BOL.

I know it's primitive, but it works.

set nocount on

go

create table Ttest (id char(29) not null, info varchar(20) not null)

go

insert into Ttest values('10069905,7/31/2002,2020705358','380214 196145 0000')

go

insert into Ttest values('10069905,7/31/2002,2020705358','380214 197183 0000')

go

insert into...

If nothing found in the KB then I'd go for the working solution. Upgrade to sp2 move the 6.5 dbs and afterwards upgrade to sp3.

I've installed sql2ksp3 with success, but DTS gave me headaches. All worked but those connecting to DB2 UDB V7.2 (rtm version). Contacted pss and it took a couple of days...

I've installed sql2ksp3 with success, but DTS gave me headaches. All worked but those connecting to DB2 UDB V7.2 (rtm version). Contacted pss and it took a couple of days...

that goes also for those using a comma as decimal point (user setting!).

Must have been for Valintines day :))

I've got a sp3-dts problem in a transfert from db2os390 to sqlserver(local). Still working on it with MS. I'll keep you informed.

Thanks. I'll definitely check with MS.

fyi check http://support.microsoft.com/default.aspx?scid=KB;EN-US;814113

I too have an xp_sendmail problem. This occurs on a w2k-sp2 clustered server (i know mail is not supported on a cluster, but anyway) Every once in a while it...

take a look at : Microsoft Knowledge Base Article - 814064 BUG: SQLBrowseConnect May Cause an Access Violation in the Client Application.