Hmm, I hope you are not doing this on large recordsets as it will kill performance (no indices could be used).

In any case, you want to get the text that...

Fortunately (or unfortunately depending on your background and point of view), SQL Server doesn't attempt to give any sort of row pointers like a file-system based database (eg FoxPro) would. ...

Your words "named instance" might give the problem away   Perhaps you have a default instance of SQL as well as the named instance...

Yes, the view would use indices when joining the tables and evaluating where clauses within the view.

I like standards - in terms of if you are going to implement some functionality and there is some standard syntax for it, you should use it - but if...

You are still confusing me by what you want??

So you have a stored procedure on Oracle...  What does it do?  Does it get all of its data from Oracle databases...

So long as just log writes were being done in the separate connection, no blocking should occur running xp_cmdshell or ADO connections, etc...  In any case, I hadn't thought of...

Good link sushila - probably a fault of the other parameters on the recordset object rather than a fault of the SQL statement you have built...  May I suggest (off...

Another nasty way of doing it is to run xp_cmdshell to start a copy of OSQL from the command prompt - this will make its own fresh connection to SQL...

I would suggest that your conversion from the binary timestamp format to a string (as part of the XML) and back is corrupting it somehow... Can you examine the value...

I hate to ask, but could you please supply the error message you are receiving??

Perhaps also run SQL Profiler whilst executing your package and see what statements are being executed... ...

Absolutely uncalled for - a polite email to you and you would have helped him out, but whenever I get instant accusations from customers of almost deliberately breaking things (why...

That was going to be my suggestion, but he did say that they tried it in his post so we can cross that off

I don't think you can catch fatal errors (high severity levels) using @@ERROR, etc...  Actually, even the new try/catch blocks in 2005 don't let you catch above severity 10 (see...

What do you mean by "bad data"?  Not the values you expect?  Certainly the timestamp will be different... And the identity column will get values in the order in which...