That's for inserting a new column in the design. If you try the same thing for an actual row of data, the new line will still be inserted at...

Can you post the query you are using??? It's gonna clear up a lot of misconceptions about your work .

No it's not true. It true that it's best to keep a few gig of spare for backups/restore operation, but 40-1 is jut ridiculous.

There's another claim like this one...

That's not unelegant. It's the way it should be.

You're better off moving the history data into an history table. The primary key there would the the primary key of the main table + DateModified

K.

Depends how you filter the set. I don't know how Oracle optimization works. You'll have to do your tests yourself to answer that one.

If you use the openxml functions in vb, you'll be fine. The 2000 limit is for display only and in QA only.

I just can't see how you cannot adapt that script. What's wrong with it??

It's not undocumented. It's just the way it works, and it can cause problems sometimes.

Each line seems to have between 35 and 40 characthers. (6*40 = 240). So I guess that it would be the most likely answer, but untill we hear from...

Just to clarify :

Tools / Options / Results / Max Charaters per column, mine is set to 2000.

Btw I was using QA to test my results.

This works for me : Select * from dbo.SysObjects for XML auto

check this out :

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=179518

Just make sure you get the minimum rowcount from the remote server. This will help a lot because it'll be less work for sql server.

Also test a few versions...