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.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-11-13 : 08:44:08
|
| Rajesh writes "We are using SQL Server dadtabase with VB front end. The server is slowed down after almost 2 to 3 hours of working and so it shows time out. Will it be a hardware or software problem. The whole system has been working for almost 8 months so there will not be ny problems with the s/w, queries or stored procedures. The system had under gone a swith off due to UPS problem. NT, SQL Server and reports are working. The error shows after workibg for 2 to 3 hours only and began to show error only after the power problem. We tried with changing the RAM but no improvement. Plsas help us." |
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2002-11-13 : 16:24:57
|
quote:
Rajesh writes "We are using SQL Server dadtabase with VB front end. The server is slowed down after almost 2 to 3 hours of working and so it shows time out. Will it be a hardware or software problem. The whole system has been working for almost 8 months so there will not be ny problems with the s/w, queries or stored procedures. The system had under gone a swith off due to UPS problem. NT, SQL Server and reports are working. The error shows after workibg for 2 to 3 hours only and began to show error only after the power problem. We tried with changing the RAM but no improvement. Plsas help us."
Does this server get used 24/7?If it does then you are in tough shape.If not, I would wakeup around 3am and start my troubleshooting then. There are many issues that could cause the slowdown. For this I would think that you start work at 8am with everyone else and the server is running smooth. As network traffic and queries pick up around 10-11am the server is running slow. I know that this issue started to happen after your ups failiar but to completely rule this out I would still wakeup early and troubleshoot without the users being there. Not only so they do not put a load on the server but from this you can also not worry about rebooting or anything else that would normally interupt the user's day-to-day activities and potentially loose business. Another thing to look at is your indexes. It's been 8mo and if you are doing a lot of DML then you that could be it. Use DBCC SHOWCONTIG to find the fragmentation of your indexes. I would not think this is a hardware issue. Typically when hardware is failing or has failed it simply will not work. If RAM has failed you be getting a lot of FATAL EXCEPTIONS (blue screen of death in NT). On that note, This does not rule out drivers for the hardware that may have become corrupted in some sort of way (I consider drivers a software issue).So to recap. lol. Check SQL Server. If your indexes look good and you're not overloaded on network traffic and queries but you still cannot connect then you may have a problem with NT.DanielSQL Server DBAEdited by - sqlserverdba_dan on 11/13/2002 16:25:42 |
 |
|
|
scottpt
Posting Yak Master
186 Posts |
Posted - 2002-11-15 : 13:41:47
|
| Is the db used for alot of transactions? if so posibly the stats are getting out of wack. |
|
|
|
pareshmotiwala
Constraint Violating Yak Guru
323 Posts |
Posted - 2002-11-18 : 11:49:36
|
| I have run into similar issues. It is ideally recommended that you observe the processes and perfmon from your desktop.Occassionally, developers tend to use sql servers without 'nolock' options, not killing their query analyzer after they run such queries tends to lock resources. You may want to restrict access to the server from non production servers.(do it by IP address). let the developers come to the server and run the queries. Also the VB application you are referring to....make sure it lets go of NT threads on your middleware/software server.I would also recommend http://www.sql-server-performance.com/ |
|
|
|
|
|
|
SQL Server speed