November 15, 2009 at 11:45 am
On in-place upgraded servers that went from SQL Server 2000 to 2008, I am getting a timeout when performing a simple insert through ADO.NET; I'm allowing 30 seconds. I tried performing the same insert using a T-SQL command and it took an exceptionally long time (50 seconds or so). The strangest part is that after it has completed the insert, subsequent inserts take less than a second to perform. On newly installed SQL Server 2008 instances (not upgraded), there is not initial slow insert. An example of the T-SQL is:
NSERT CaseCheckOut(Case_ID, CheckedOut, WorkstationName)
VALUES (4800015, 1, 'WORKSTATION1')
Some information that I believe is relevant, but could be a red herring, is that the table in question is the master table for a join filter for a merge replication. There are about 30 or so tables that are joined to this table to allow for on replicating only a subset of the data to a workstation.
Any thoughts as to why this would be an issue on a in-place upgraded installation but not on a new workstation? I have checked the options, and I have most of the options the same, including the Compatibility level (both 100).
Thank you.
November 16, 2009 at 1:31 am
When you upgraded, did you update the statistics after the upgrade completed?
Not sure about 2008, but I know this was required after upgrading from 2000 to 2005, and not doing this could cause significant performance problems until the statistics were updated.
November 16, 2009 at 6:40 am
I had not, but when I just ran them, every table came back with no updates needed (e.g., 0 index(es)/statistic(s) have been updated, 2 did not require update.)
Thanks for the response. Any other thoughts?
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply