August 30, 2010 at 7:16 am
Hi, I have a very simple query that inserts one record (contains XML data stuffed in a varchar(max) field) into a table. This query takes take quite a bit of duration (110 ms) but there is virtually little read or write activity. The execution plan looks very clean. There is a clusted index delete/insert. The clustered index is a datetime value. The primary key is a GUID that is inserted into a CHAR(36) column. The XML is not very long, 1600 bytes.
I didn't design this db:-).
Can anyone point me to something I should look at.
August 30, 2010 at 8:37 am
110ms isn't that long, so my initial take, look at sys.dm_exec_requests to see what it's waiting on, probably won't work, but you could try. If it's XML, that run time sounds about like what is needed to get the XML parser loaded into memory.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 30, 2010 at 9:31 am
Thanks. The data is XML, but the stored proc parameter and destination field in the DB are varchar(max) so the parser shouldn't be loading.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply