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 |
|
multiplex77
Starting Member
24 Posts |
Posted - 2007-05-04 : 04:08:35
|
| Hi everyone,I'm connecting to my LOCAL MSSQL 2005 database using Management Studio. I find that after a few hours of use, Management Studio's connection to the database becomes extremely slow. For example, if I right click on a table and choose Open Table, it will take at least 30 secs to open the table. Then if I make changes to a record and move the cursor to the next row, it will take another 30 secs to update the record. I don't think it's anything to do with indexes, cos my table is very small (less than 20 records).I'm not running any batch jobs on my local database. In fact, my SQL Agent is turned off. I notice this does not happen when I connect to my REMOTE database, which is hosted on a commercial web host.What could be wrong here? Has anyone experienced this before?Thanks for the help. |
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2007-05-04 : 07:01:01
|
look for memory use and virtual memory use for the process sqlWb.exe (that's management studio)you'll see that over time virtual memory is increasing.this means it has memory leaks. every app has memory leaks this means that you should periodicaly restart it. obvious solution, no? _______________________________________________Causing trouble since 1980blog: http://weblogs.sqlteam.com/mladenp |
 |
|
|
multiplex77
Starting Member
24 Posts |
Posted - 2007-05-07 : 22:18:24
|
| Thanks spirit 1. Yes, I did consider that it could be due to memory leaks. That's why I tried closing and opening the application. But it didn't help. It seems that out of the blue, Mgt Studio will just decide to go into "super slow query" mode. The entire application (Mgt Studio) will lock up for a few seconds as the query is being done (e.g., when I change a table field value directly).When I check SqlWb.exe in the Task Manager, it is still using only 50,000K. There are times when it is using 90,000K and yet there isn't this lock-up-during-query problem. Any other suggestions? |
 |
|
|
jezemine
Master Smack Fu Yak Hacker
2886 Posts |
Posted - 2007-05-07 : 23:10:10
|
is it only open table that's slow? what about running this in the query editor:select top 100 * from YourTable www.elsasoft.org |
 |
|
|
multiplex77
Starting Member
24 Posts |
Posted - 2007-05-08 : 01:46:09
|
| No, even when I execute a Query, it is also slow. The same query that runs in a split second one moment, some time later takes 30+ seconds to execute. My tables are all very small -- don't even have 100 records. |
 |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2007-05-08 : 03:19:40
|
| Are there other processes running on your computer, such as automatic defrag tool?Peter LarssonHelsingborg, Sweden |
 |
|
|
multiplex77
Starting Member
24 Posts |
Posted - 2007-05-08 : 05:48:47
|
| No other processes. It is not that my computer is slowing down. My other applications run fine. It's only SQL Server that takes a long time to run queries SOMETIMES. |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-05-08 : 10:31:20
|
| Any blocking on sql server? |
 |
|
|
|
|
|
|
|