You can research SELECT FOR XML.  Granted this isn't perfect XML however, with a little work you can make it work for you

Sounds like there is a problem with your code.  Looks like you need to check PRIOR to updating ANYTHING that you need to ensure that the tickets have not already...

I would review the table that you are inserting the data into and ensure that the "identity" column is in fact set as IDENTITY along with default value, etc..

Or in...

Conversely, you may want to review using a UDF that returns data that you can use i.e. SELECT * FROM dbo.udf_TableReturn.....

What problem is it giving you?

Have you looked at SELECT CONVERT(VARCHAR(50), GETDATE(), 103)?

OR you could use the import/export wizard OR SQL Copy task in DTS, OR....

S@#^%# out of luck ....

I gues then that I agree with HP...

I think then that you are SOL unless you buy a 3rd party app to scroll through the Tlog OR enhance your system to have an audit trail...

Named pipes runs better over WAN than TCP/IP.  TCP/IP runs better over LAN than Named pipes.

You can try and remove it and see...

If you have a column defined for insert/update you could query off of that....

I know this MAY cause a lengthy discussion but here goes:

AMD 64bit is FASTER then Intel 64BIT when handling 32 BIT applications.

AMD will run 32BIT as fast with their 64BIT...

Try looking at USER_NAME() or CURRENT_USER  Of course you will probably need to parse the field.  This will ONLY work if trusted connections are used...

If you are always passing MM/DD/YYYY then you could (at the top of the SP) SET DATEFORMAT MDY and see if that helps...