January 25, 2011 at 8:33 am
I have an web app using ASP and SqlServer. On my local and Dev version for same DB We don't get script time out, but, on Live instance many time Script time out error is generated.
Please can somebody help to debug/fix the issue. Is it web server or database related. What parameters we need to check to debug issue?
January 25, 2011 at 8:36 am
Is it tsql which it dies on, 1st maybe load sql mgmt studio on web server and run the sql statements and see if you get a time out. At the same time run sql server profiler on the db server and see if you see any errors or issues on the prod db server when you run the sql
January 25, 2011 at 8:36 am
Most likely, the live version is either working against much more data than the dev database, or is running into blocking issues.
Is the production database much larger than the dev one?
Have you looked at blocking?
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
January 25, 2011 at 9:26 am
Another possibility is differences in the physical boxes. We had a production box once that had slower CPU's the dev box. Made us crazy for a while til we noticed.
A more likely possibility, do you have good statistics maintenance running on the production box? If the data is volatile there you might have out of date statistics leading to a different execution plan.
I'd start with comparing the execution plans to see if they're different.
"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
January 25, 2011 at 11:18 am
Thanks, I have only remote access. And I am not comfortable with Execution Plans. How to read them!
January 25, 2011 at 11:23 am
SAnjy N (1/25/2011)
And I am not comfortable with Execution Plans. How to read them!
Look at the post right above this one. Look at the books that the author of that post listed in his signature.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 25, 2011 at 11:47 am
SAnjy N (1/25/2011)
Thanks, I have only remote access. And I am not comfortable with Execution Plans. How to read them!
If you search on the web you can find a free copy of my book on executtion plans. A couple of chapters are available over on Simple-Talk under my name (I'm typing this from an iPad & it's a bear to copy & paste links or I'd provide them for you).
You don't need to interpret the plans just yet. Generate the plans from each of the machines and just compare them visually. That inspection alone will give you a ton of information.
"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
January 25, 2011 at 12:40 pm
Sorry all of these solutions should come after profiler, it may be something as simple as a login issue,start simple first
November 6, 2014 at 11:49 pm
while running the query please check sp_who2 which is blocking that you can know.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply