Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
sql server 2000 gone slow 1
- Thread starter shams123
- Start date
has the tempdb run out of space - check where master/tempdb etc are located and check they arent running out of space.
Second option - try running profiler to see where the problem lies (i.e. if excessive reads etc could be query plans are skewed)
101 other options - wait to George gets started
"I'm living so far beyond my income that we may almost be said to be living apart
Second option - try running profiler to see where the problem lies (i.e. if excessive reads etc could be query plans are skewed)
101 other options - wait to George gets started
"I'm living so far beyond my income that we may almost be said to be living apart
proably statistics that are out of date
Denis The SQL Menace
SQL blog:
Denis The SQL Menace
SQL blog:
-
1
- #4
mrdenny
Programmer
- May 27, 2002
- 11,595
It could be any number of things. Way more information will be needed before anyone can take more than a guess as to what the problem is.
Here are some common possible reasons.
1. The OS doesn't have enough memory left to it. (Check this in the Task Monitor).
2. The drives that the database is on are at capacity. (Check the performance monitor for the disk queueing for that drive.)
3. There is another process running that is taking all the CPU power from the server.
4. There are to many processes running taking all the CPU power from the server.
5. Your stats are out of date.
6. Indexes are missing or were dropped that are needed.
Does the problem go away if SQL Server is restarted?
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005)
--Anything is possible. All it takes is a little research. (Me)
![[noevil]](/data/assets/smilies/noevil.gif "[noevil] [noevil]")
Here are some common possible reasons.
1. The OS doesn't have enough memory left to it. (Check this in the Task Monitor).
2. The drives that the database is on are at capacity. (Check the performance monitor for the disk queueing for that drive.)
3. There is another process running that is taking all the CPU power from the server.
4. There are to many processes running taking all the CPU power from the server.
5. Your stats are out of date.
6. Indexes are missing or were dropped that are needed.
Does the problem go away if SQL Server is restarted?
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005)
--Anything is possible. All it takes is a little research. (Me)
- Thread starter
- #5
mrdenny
Programmer
- May 27, 2002
- 11,595
No problem.
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005)
--Anything is possible. All it takes is a little research. (Me)
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005)
--Anything is possible. All it takes is a little research. (Me)
- Status
Similar threads
- Locked
- Question
