February 20, 2015 at 8:30 am
Greetings
I have a SQL Server 2012 w/SP2. Whenever I finally get into SSMS and try to do anything (e.g., open a query window, keyin and execute SELECT @@VERSION) it takes forever. And there is one small db on this server with no one but myself using it at this time.
Microsoft SQL Server 2012 - 11.0.5058.0 (X64)
May 14 2014 18:34:29
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
I look in Windows TASK MANAGER and see that SSMS.EXE is consuming the CPU. I've searched the Internet (and will continue to do so) with no luck.
Has anyone had this problem? Is there a solution?
thanks in advance.
February 20, 2015 at 10:30 am
I've heard about this being an issue before, but I'm not sure what the solution is. In most circumstances, you shouldn't be running SSMS on the Production server. Instead you run it remotely and connect to the production server. That way the production machine is only ever handling the SQL Server instance, and not any GUI tools.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply