SQLWB.EXE max cpu
SQL Server Management Studio 2005
Windows 2000
when I "Open Table" to view all the records in a table, the cpu goes to 100% and the records are drawn very slowly - about the same speed as you read !
I have re-installed all the software and also tried service pack 1. SQL 2000 worked fine.
any ideas ?
thanks
John, UK
Microsoft SQL Server Management Studio 9.00.2040.00
Microsoft Analysis Services Client Tools 2005.090.2040.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 built by: (_sqlbld)
Microsoft MSXML 2.6 3.0 5.0 6.0
Microsoft Internet Explorer 6.0.2800.1106
Microsoft .NET Framework 2.0.50727.42
Operating System 5.0.2195
Answers
- I would have to think that your local hardware is causing the performance problems you are seeing.
I managed to fix the problem by updating all drivers on my laptop - bios, graphics, network etc and all is ok now. I can't say for sure which one was the key, but I think it was the graphics - don't ask me to explain it !!!
John
All Replies
- the CPU going up during the OPEN TABLE Object Explorer command is normal. I would be more concerned about the machine's hardware and other software consuming valuable resources as well as the sql server's resources and the bandwidth between your box and the server. And another issue is the number of records you are returning.
- If there are a lot of records in the table, construct query in Diagram Pane, Criteria Pane or SQL Pane: probably you don't need all the data at the moment. If you would like just to look at your data, run query from New query window: it works faster. And finally, yes, that's is not a secret that Management Studio consumes more resources than it was done by EM and QA.
Thanks for the replies so far.
I have opened many tables, some as small as 20 records, and they all paint very slowly.
I have opened tables using SQL 2000 with no problem, so I would assume that my hardware is fine. The PC is a DELL GX280 with 1GB ram.
Does anyone else have SQLWB maxing during the screen paint process ?
thanks
John
- I would have to think that your local hardware is causing the performance problems you are seeing.
- Hi,
I'm experiencing the same problems as John. Table > open table and my laptop freezes completely, CPU going up to 100 % even when it's only 20 records. Don't think it's a bandwith nor a hardware problem. Every action afterwards, like for example resizing the object browser takes the cpu up again and the screen starts repainting with a speed even slower then you can read. When i query the same table with a simple select statement using new query , the grid fills up in no time.
So I think the problem lies in Management Studio itself and then specially the screen called by Open Table.
I have a Dell Latitude 610 with 1.86Ghz cpu, 1Gb RAM.
SQL 2005 SP1
Kind regards,
Johan I have the same issue, it often happens while running a long running query. The same query in 2000 doesn't freeze my machine, so it has to be a SQLWb.exe issue not hardware. Seems like its not give up time properly in all cases while waiting for results. Its particlairly bad if you select "include actual execution plan" then click on the plan tab before the result set finishes.
Darrick
I agree that the problem lies directly in Management Studio. I can assure you that it is not just conneted to the Open Table screen. I have this problem occur on a regular basis and I can attest to the fact that it isnt even necessary to attempt any database operations. Simply starting the application, opening a query window, and attempting to save the source code for a new stored procedure to a file is often enough to tie up not only sqlwb.exe but the entire machine for 10 minutes or more. That's if it ever comes back.
This happnes on a 2.8 GHz HP laptop that has 1GB of RAM, Windows XP Professional with Service pack 2 with all additional applicable updates and SP1 for SQL Server 2005 installed.
I thought I would add me version info from SQLWB help about.
Microsoft SQL Server Management Studio 9.00.2047.00 Microsoft Analysis Services Client Tools 2005.090.2047.00 Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158) Microsoft MSXML 2.6 3.0 4.0 5.0 6.0 Microsoft Internet Explorer 7.0.5700.6 Microsoft .NET Framework 2.0.50727.42 Operating System 5.1.2600 I've the same problem, the process SqlWb.exe cosumes all my resouces. When the transactions ends the memory is not deallocated. I'm working in a Dell Power Edge Server with 2 real processors and 2 dual core processors and 4 GB of RAM. if anyone knows how to raise the perfomance of the data base engine please help me.
Thank's everybody
The performance problems you are seeing are definitely not normal. Please file a defect report on http://connect.microsoft.com. The product team uses customer defect reports to prioritize future work. When you file your report, please let us know if the performance problem happens every time you open a table during a Management Studio session, or just the first time.
Management Studio is mostly managed code which uses garbage collection to manage memory. As far as Windows in concerned, memory allocations in managed applications tend to accumulate until there is memory pressure on the box, then the .NET runtime becomes more aggressive about collecting unused memory. I wouldn't worry too much about the amount of memory Management Studio has allocated unless this is causing the OS to start swapping virtual memory to disk. If virtual memory swapping starts happening, performance of all applications will slow to a crawl and the hard drive access lights will turn on and stay on (or flicker very rapidly) as long as virtual memory is being used.
On less capable machines, it can sometimes improve workstation performance to limit the amount of memory available to the SQL Server engine. Obviously, that trades off server performance for console application performance. Whether or not that is acceptible depends on the environment. I have to do this on my laptop to keep enough memory available for the operating system and applications. On my laptop (PIII/1200 MHz -- definitely not a super-machine), I normally limit SQL Server to 128 MB of ram, leaving ~900 free for the OS, Visual Studio, and SSMS.
You can change the amount of memory the server will use using the server properties dialog in Management Studio. Connect to the server in Object Explorer, right click on the server node and select "Properties" in the context menu. Click on the Memory page to change the memory usage settings.
Hope this helps,
SteveI'm also having significant problem with sqlwb.exe CPU usage in a VS2005 development environment on a Dell Precision M70 laptop with 1mb ram 2ghz centrino processor.
All I'm doing is opening the SSMS solution and generally it hangs (before I see anything) and forces me to shut down my pc (takes 15min's to close all applications, via Task Manager -> end process). One of the annoying things is killing the process seems to transfer CPU problems to the next most hungry application, often IE7 or VS2005 IDE (which is really painful).
There were a couple of bugs logged in the bugs database, but none really explained the 100% CPU hang that I've experienced.
So I logged a bug at https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=241997
I managed to fix the problem by updating all drivers on my laptop - bios, graphics, network etc and all is ok now. I can't say for sure which one was the key, but I think it was the graphics - don't ask me to explain it !!!
John
- I would have to agree with John, display drivers on my Dell Laptop seemed to be the root cause of the problem. Once I removed Nvida's Nview destop management software and upgraded the drivers for the laptop, the problem hasn't re-occured.
- If you are using SQL Server 2005 1GB of ram is simply not enough. sqlservr.exe consumes on average 1.2 GB of memory by itself. .NET applications are memory hogs, SQL Server 2005 is no exception.
Has anybody else found a solution to this? I don't think my drivers are out of date, according to the nvida's website.
But my symptoms are identical to yours... SQLWB.exe takes all the CPU, and when I kill it, all the CPU time transfers to another process (Outlook, VWD2005, or Explorer typically).
I end up having to shutdown and reboot, and have to force an EndTask on about 10 tasks before it reboots by itself.
I noticed this start happening after I upgraded to IE7, so I think some of the shared files that got upgraded as part of the IE7 install have caused this. I am now working on a project that uses VWD2005 and SQLExpress, which means I need to use the exact tools that cause this problem. I am rebooting (no joke) about 7-10 times a day!
Reinstalling the OS with all updates, then installing SQL Server and all relevant updates appeared to do the trick. It isn't a very desirable course of action but it is one I was forced to do about 2 months back. Since then, I have not had issues with SqlWb.exe maxing out the CPU. All my drivers where up to date before the reinstall, so they should be the same ones I had afterwards. In my case it seemed to be an issue that was fixed by SQL Server SP1, but only applied properly when the system was still in a clean unused state.
Hi, I just stumbled across this thread while looking up SqlWb.exe (as its currently maxing out one of my CPUs). I too have seen the issue where a process goes supernova and, once you've killed it, another process takes up the CPU (actually, it just goes to 50% as its a Pentium D) - you kill that one and another takes it up, very odd.
I also believe it to be linked to IE7. Its only happening on my IE7 machine and usually follows a problem on a page. These days I leave as many as 20 pages open for weeks and refresh them alot (they have Java stock charts in them), and mem usage can get to >300Mb for iexplore. Today, I tried refreshing a page and IE hung; when I eventually killed IE and took a look at task manager, I noticed SqlWb.exe was the runaway, but I really believe the problem starts in IE and "infects" other processes.
When I was having the issue with the SqlWb maxing out the CPU simply killing the process tree was sufficient. I never experienced the situation where a second process would start hogging the CPU. As a result, I never actually needed to reboot the machine, just keep restarting SqlWb until I had an instance that didn't go crazy on me.
Personally, I still think the service pack fixes the issue but only if it is applied to a clean installation of SQL Server. I don't believe IE7 has anything to do with the issue as I had the problem while still under IE6. After I was forced to reinstall everything, I never saw the issue again, even after installing IE7.
hriverag93 wrote: I've the same problem, the process SqlWb.exe cosumes all my resouces. When the transactions ends the memory is not deallocated. I'm working in a Dell Power Edge Server with 2 real processors and 2 dual core processors and 4 GB of RAM. if anyone knows how to raise the perfomance of the data base engine please help me.
Thank's everybody
Does anyone have the solution for this issue?
Thanks.. really appreciated
Having reviewed all the answers to my initial question, I still feel confident that the issue is display drivers. The comments regarding memory are understandable but SQL will only allocated memory as required and not blow physical limits - it's not that stupid !! Pause whilst doubt creeps in.....
The IE comments again are understandable as lots of files are updated, such as VBScript, but again I don't feel it is the cause of the problem.
Go along the lines of updating drivers. If that fails, do a full rebuild and put SQL on last. Do disk images so you can step back and repeat certain steps.
I have had no feedback from Microsoft but I'm sure they know about it. Doubt creeping in again, damn.....
John
All I did was run a delete statement on 60,000 records in sql 2005 and I nearly maxed dual quad core xeons. I have 16 gb of ram in the server!
I had the same issue which started when I updated to the latest nvidia driver on my Dell laptop. It also caused stability issues with other applications. I did a complete video driver uninstall and the problem is gone.
Thanks for your info in this post and I hope this confirmation helps some other people.
Donny
- Same for me... Disable Nvidia nView Desktop manager.. Problem solved
I want to add that I am having problems with SQLWB.EXE using 50 - 80% of the CPU time on both processors of my Dell Optiplex 745. I have 2 GB of memory, with 1 GB of physical RAM free. I can reproduce the problem by either saving or opening a .sql file in MGMT studio. To anyone confused about the problem, this is a client tool problem, not SQL Server. At any rate, I will try the display driver update and see if this resolves the issue, although I have an ATI video card.
Thanks,
Eric
Just wanted to confirm, that after suffering with this strange behavior of SqlWB (Sql Management Studio), I came across this thread. As soon as I disabled NVidia Desktop Manager, SqlWB immediately snapped back to its spritely self.
- I am having the same CPU race condition but I am seeing this on a Dell PowerEdge 1950 running Server 2008 DC, the SQL server is running under Hyper-V. The host server has 4 GB of RAM, is using the default VGA display driver so no nvidia desktop manager to cause the issue. I noticed this while running a SQL query that was retuning about 15 rows of data, so no heavy db access.
Anyone else have any ideas on what might cause this? No memory or hardware issues, no nvidia drivers to cause problems.
Regards,
Anthony
Anthony Clendenen - A user reported me the same problem. He was observing that in addition to a high CPU usage by SQLWB.EXE there was also a significant CPU usage (about 40%) caused by services.exe. Turning off NVidia Desktop Manager makes SQL Management Studio performing normal. Turning on again NVidia Desktop Manager the Management Studio performed slowly.
- I too am experiencing this behaviour. It started when I installed Kaspersky Server Anti-virus. I was wondering if anyone not suffering from the nvidia problem also had Kaspersky installed. Perhaps the extra scanning is slowing it down?
- Hi LSilk ,
me too have the same problem as yours. After installation of KIS (Kaspersky Internet Security) 2010 (9.0.0.736) I experienced a high CPU usage from the process SQLWb.exe when I invoke File Open or File Save (both when I try to open/save a file - .sql – and when I choose to save results to file). The File Open / File Save dialogs takes many seconds to open. When I select a file (for example to open it) it takes a long time to open that file. I don’t have MRU or networks references and I’m sure the problem began when I installed KIS new version. At the moment I did not found any solution to my issue.
.:. Marcello Rutter .:.
