Site Sponsored By: SQLDSC - SQL Server Desired State Configuration
Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Hi Allim using windows server 2008r2 with sql server 2008r2on this server im running also the TFS server.lately tfs clients get disconnected, only after a full restart they can work 4 hours straight.im adding some stats from performance monitor and some sql queries.can anyone tell what is wrong with this server?ThanksGuy
tkizer
Almighty SQL Goddess
38200 Posts
Posted - 2015-04-06 : 12:22:03
quote:lately tfs clients get disconnected, only after a full restart they can work 4 hours straight.
We need more information. What are the symptoms?Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/
guy3145
Starting Member
3 Posts
Posted - 2015-04-06 : 13:17:15
our users use TFS from visual studio. in the middle of the day everybody getting disconnected, the issue resolve only if im restarting the sql server service. here is more stats in the picture. im guessing that this is a tempdb issue? we have only one tempdb and the server has 8 core processor, i read that i need at least 8 tempdb file to relief some of the bottleneck, is that correct?
tkizer
Almighty SQL Goddess
38200 Posts
Posted - 2015-04-06 : 13:23:16
You're jumping too far down the troubleshooting. We need to figure out why they are getting disconnected, and if it's even a SQL Server issue. Run a trace to see what is going on when it occurs. Check the error log and event viewer for any issues.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/
guy3145
Starting Member
3 Posts
Posted - 2015-04-07 : 05:44:55
thanks for your answer. there is nothing in the vent viewer that can lead to that issue. we say a lot of the same error in the picture here:that's why we are focusing on the tempdb issue
tkizer
Almighty SQL Goddess
38200 Posts
Posted - 2015-04-07 : 12:06:24
For that message, I would update the drivers and firmware for the entire IO subsystem on the database server. See if that messages go away. If they don't, you need to investigate the disks. It is not a tempdb issue but rather a severe IO performance issue. Updated IO drivers and firmware are your first step for that message.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/