[dba-SQLServer] System not responding for seconds at a time

jwcolby jwcolby at colbyconsulting.com
Thu May 1 10:59:30 CDT 2008


This did not completely fix the issue but it did make a HUGE difference.

I was getting REALLY strange behavior like pauses every time Visual 
studio would step INTO a function.  It appeared to have something to do 
with initializing objects as well, any time I would initialize an object 
it would pause for several seconds.  I observed this stepping through a 
program.  Needless to say when I just fired up my project and tried to 
run to a break point buried way down in the code it would not respond 
for 20-30 seconds...  Truly strange.

In the end I had to shut down SQL Server and reboot the system.  Then 
the system responded normally.  However I have discovered that .Net on 
x64 systems do not have editing in a running project (forget what that 
is called).  It works in x32 but not x64, which is where I am trying to 
do my dev at this moment.

John W. Colby
www.ColbyConsulting.com


Jim Lawrence wrote:
> That is very good to know... John
> 
> -----Original Message-----
> From: dba-sqlserver-bounces at databaseadvisors.com
> [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Thursday, May 01, 2008 6:31 AM
> To: Discussion concerning MS SQL Server; VBA; Discussion of Hardware and
> Software issues
> Subject: Re: [dba-SQLServer] System not responding for seconds at a time
> 
> Well... it appears that I have fixed the issue.  After Googling "slow 
> server response time" or something similar I ran across references to a 
> "Maximum Memory" property for SQL Server.  I finally found that and it 
> was set to something insane like 200000000 MEGABYTES (several petabytes 
> of server memory).  While I can dream of such a machine, it ain't 
> happening here!
> 
> I adjusted the Maximum Memory down to 2 gigs and the "amount available" 
> in Task Manager Performance tab popped up to 4 gigs.  Having done that, 
> and after perhaps 30 seconds, suddenly my machine is responding in a 
> normal way.  I am now adjusting that number to "leave" perhaps 2 gigs 
> available to applications other than SQL Server.  I probably don't even 
> need 2 gigs but it is critical that I don't end up unable to do anything 
> on that machine.
> 
> John W. Colby
> www.ColbyConsulting.com
> 
> 
> jwcolby wrote:
>> I don't quite know where to address this so I am cross posting it.  I am 
>> working on a fairly powerful server running Windows 2003 x64 and SQL 
>> Server 2003 x64.  It has 8 gigs of memory.  No malware software, 
>> software firewall, virus scanner etc.  Nothing.
>>
>> I am running a file shrink on the SQL Server file, trying to remove 
>> about 140 gigs of empty space.  That process has been running since last 
>> night, well over 8 hours now.  It APPEARS that process is using all of 
>> available memory since task manager shows only about 200 megs 
>> "available".  However if you look at the process tab, no process says it 
>> is using more than 100 megs of ram.  The performance tab shows almost no 
>> CPU cycles used, 4 cores hanging out about 0 - 10% used, and even then 
>> only one of the cores appears to be doing anything.
>>
>> The computer is "stuttering" badly.  Try to do anything - change to a 
>> different program, page up in visual studios code etc, and the computer 
>> will usually hesitate before doing whatever you requested.  I am trying 
>> to work on a VB project and can't get anything done because as I move 
>> around in the doc it may take 2 to 5 seconds just to respond to my 
>> request to move my cursor.
>>
>> Has anyone seen SQL Server lock up the the system like this, IOW is it 
>> SQL Server?  Does anyone know how long the file shrink could take - 
>> days, weeks, months?  Does anyone know how to cancel the file shrink? 
>> This is the most powerful server I have, quad core, running x64 
>> software, 8 gigs, high speed raid arrays etc.
>>
>> Unfortunately I was in the middle of a vb.net project yesterday before I 
>> started the shrink running after work and the server is unusable for 
>> anything right now.
>>
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
> 
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
> 
> 



More information about the dba-SQLServer mailing list