Nothing there, you may want to repost.

However, assuming the XML is well formed, you have multiple options for importing it.

Definitely go for the varchar(max). The only down sides are disk space, but that's easily monitored.

I wasn't going to comment on the Tuning Advisor, but since the gate is now open... I haven't had good experiences with the Advisor either. I haven't had it ruin...

Oh, and, I'd offer to help her work on her performance issues in order to clean up her system enough so that you can connect to it.

Steve's correct. Further, some degree of processing will occur on both of the servers, no matter what. Bare minimum, depending on what kind of server you're linking to and how...

Still not there.

One other suggestion, I'd use SSIS over DTS especially since you're trying to move data to 2005.

I'm largely piling on at this point, but what the heck...

Yes, seperate the databases by customer and seperate them by module as well. If possible isolate by instance or use...

I was thinking the same thing, but I did some searching Integer8 and it's actually a 64 bit value. I'm not convinced you can put it into a BigInt, but...

You are posting your questions to the 2005 TSQL forum. Any answers are likely to contain syntax that won't work in 2000. That's...

The first two messages are lower level messages that are not a part of the TSQL statement, but are occurring at a lower level within the system. The CATCH statement...

I'm sorry, I've got nothing that shows how to convert from the 64bit Integer8 data type into anything in SQL Server within TSQL.

You may have a perfect opportunity to...

Good one. I hadn't thought it through that far.

Unless...

Sorry that wasn't helpful.

You've got a lot of very odd restrictions on how you can do this work. Why is the behavior so peculiar?

However, if you must have 30...