<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2005
»
Administering
»
max worker threads
max worker threads
Rate Topic
Display Mode
Topic Options
Author
Message
trayalacheruvu
trayalacheruvu
Posted Tuesday, May 12, 2009 4:47 AM
SSC Rookie
Group: General Forum Members
Last Login: Tuesday, February 19, 2013 10:18 PM
Points: 25,
Visits: 152
Dear All,
i ahve dedicated SQL server 2005 Database server for supporting one application.
Server Configuration is : O/S:64-bit, Microsoft SQL Server Standard Edition (64-bit), 4 processes with 12 GB RAM. currently we have 150 concurrent users are performing operations.here i am i am facing the issue like "Timeout expired. The timeout period elapsed prior to completion of the operation
or the server is not responding." while installing SQL server Instance i didn't change any configuration setting. The Max worker treads is default is 0 ..
Can any one suggest me if i changed from 0 to some other valve it will improve the perfomance.
Thanks in advance,
Thulasi.
Post #714854
MarkusB
MarkusB
Posted Tuesday, May 12, 2009 5:06 AM
SSCarpal Tunnel
Group: General Forum Members
Last Login: Tuesday, May 07, 2013 3:03 AM
Points: 4,218,
Visits: 3,874
trayalacheruvu (5/12/2009)
Dear All,
i ahve dedicated SQL server 2005 Database server for supporting one application.
Server Configuration is : O/S:64-bit, Microsoft SQL Server Standard Edition (64-bit), 4 processes with 12 GB RAM. currently we have 150 concurrent users are performing operations.here i am i am facing the issue like "Timeout expired. The timeout period elapsed prior to completion of the operation
or the server is not responding." while installing SQL server Instance i didn't change any configuration setting. The Max worker treads is default is 0 ..
Can any one suggest me if i changed from 0 to some other valve it will improve the perfomance.
Thanks in advance,
Thulasi.
I don't think changing the max worker thread setting will solve your problem. And even if it wouuld solve the problem I see it more as a last option if everything else fails.
A better approach is investigating the process which causes the timeout. Timeout errors are generated by the frontend application, since SQL Server doesn't have a query timeout. It's just the client, which won't wait any longer.
You should try to find out what queries are taking too long and why are they taking so long. Is it because the database is huge and the query very complex, do you need to add indexes or is it because different processes are blocking each other.
Markus Bohse
Post #714864
John.Sansom
John.Sansom
Posted Tuesday, May 12, 2009 5:16 AM
Old Hand
Group: General Forum Members
Last Login: Friday, May 10, 2013 1:52 AM
Points: 343,
Visits: 1,453
Hi,
As the prior poster mentions, you need to identify the source of your performance woes. Only then can you troubleshoot and optimise performance.
Take a look at the SQL Server Perormance area of Brent Ozar's blog. It provides some guidelines on how you can go about performance tuning a SQL Server Platform.
http://www.brentozar.com/sql-server-performance-tuning/
John Sansom (
@sqlBrit
) |
www.sqlbrit.com
The SQLBrit Community Forum
- "There's so more to being a Data Professional than just technology."
Post #714867
trayalacheruvu
trayalacheruvu
Posted Tuesday, May 12, 2009 5:16 AM
SSC Rookie
Group: General Forum Members
Last Login: Tuesday, February 19, 2013 10:18 PM
Points: 25,
Visits: 152
hi Markus,
There are few queries which is taking time to execute..but in the application level they have set that connection timeout period as 100 sec. for testing purpose i am planing to change this 100 sec to 200sec. after changing 200sec if its not giving the time error means we can optimize those long running queries. I have created indexes each and every table. and all the indexes are making use of the application.
Thanks,
Thulasi
Post #714868
MarkusB
MarkusB
Posted Tuesday, May 12, 2009 5:49 AM
SSCarpal Tunnel
Group: General Forum Members
Last Login: Tuesday, May 07, 2013 3:03 AM
Points: 4,218,
Visits: 3,874
trayalacheruvu (5/12/2009)
hi Markus,
There are few queries which is taking time to execute..but in the application level they have set that connection timeout period as 100 sec. for testing purpose i am planing to change this 100 sec to 200sec. after changing 200sec if its not giving the time error means we can optimize those long running queries. I have created indexes each and every table. and all the indexes are making use of the application.
Thanks,
Thulasi
You should look for the query timeout, not the connection timeout. The connection timeout is just how long will it wait for the sewrver to respond when logging on to the database. The query timeout means how long the app waits for the results of a query.
Markus Bohse
Post #714886
Grant Fritchey
Grant Fritchey
Posted Tuesday, May 12, 2009 6:22 AM
SSChampion
Group: General Forum Members
Last Login: Yesterday @ 4:50 AM
Points: 13,371,
Visits: 25,143
trayalacheruvu (5/12/2009)
hi Markus,
There are few queries which is taking time to execute..but in the application level they have set that connection timeout period as 100 sec. for testing purpose i am planing to change this 100 sec to 200sec. after changing 200sec if its not giving the time error means we can optimize those long running queries. I have created indexes each and every table. and all the indexes are making use of the application.
Thanks,
Thulasi
Are you sure it's using the indexes effeciently? Just because you see the index in the execution plan doesn't mean it's being used well. Are there scans? Are you getting the right kinds of joins based on the amount of data being moved? Are your statistics up to date? Are the indexes fragmented?
All this information should be checked before you ever get into low level tuning of worker threads and things like that.
----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of:
SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans
Product Evangelist for
Red Gate Software
Post #714905
« Prev Topic
|
Next Topic »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
