sqlservr.exe nealy 300M of memory at boot and growing

[pallen]

The sqlserver.exe service installed with the DSC module in LV 8.6 on this computer.  Pretty much right away I noticed serious performance issues with the PC.  The hard drive was thrashing continuously, and memory was being gobbled up even when little or nothing was running on it. 

This screen shot is taken right after boot.

A quick Googling confirms that I'm not the only one facing this problem.  So there's a good chance that it's completely unrelated to LabVIEW.  But other LabVIEW programmers may be seeing performance problems after it's installed. 

My real concern is that I need the DSC module on an upcoming project on three PCs.  These PCs will running automated testing equipment in another country.  So they need to be as robust as possible. 

Can anyone tell me which processes exactly this server is required for?  

If I don't absolutely require it, I would like to disable it permanently, or remove it completely.  

Thanks.  

[Davidek]

Hi Patrick

Have a look at this post. Seems to describe the same behavior and has a solution too.

Best Regards

David

NISW

[Davidek · Accepted solution]

Hi again Patrick

Just saw that the crucial link in the other post was broken and the command in the post did not work for me. I'm hoping that downloading and installing this and the following this will do the trick. Downloading while I'm typing this so I let you know how it goes.

Best Regards

David 

[pallen]

Thanks for the link David.  This is along the lines of some other links I found about changing the memory allocation limits.

Unfortunately, I don't seem to be able to establish a connection to the sever through the command line.  I don't recall ever creating a password here.  Am I doing something wrong?

[Davidek]

Hi Patrick

That's the same error message I got, but I could log in and change the memory settings using the application I linked in my last post. There it by default used my Windows username and a blank password to log in. It also specified a server name as "mycomputername"\SQLEXPRESS. So I tried using the the command:

C:\>osql -S LAPTOP\SQLSERVER -E

That got me somewhere, just need to find the command for changing memory allocation. But like I said, it worked using the Microsoft app.

Best Regards

David

Message Edited by Davidek on 08-17-2009 09:24 AM

Message Edited by Davidek on 08-17-2009 09:25 AM

[Davidek]

Think I found it. Logged in according to last post and then posted all of the following in one go to the 1> prompt:

EXEC sys.sp_configure N'show advanced options', N'1'  RECONFIGURE WITH OVERRIDE
GO
EXEC sys.sp_configure N'max server memory (MB)', N'100'
GO
RECONFIGURE WITH OVERRIDE
GO
EXEC sys.sp_configure N'show advanced options', N'0'  RECONFIGURE WITH OVERRIDE
GO

That reset the Maximum Server Memory to 100MB

Best Regards

David

Message Edited by Davidek on 08-17-2009 09:31 AM

[pallen]

Thanks for the updated link David.

I downloaded and installed the application with no troubles.  I set the max memory size to 50M, and then closed the application and rebooted the PC.  

At shutdown, nicitdl5.exe threw a C++ Runtime error fault.  But it seems to have started back up okay on reboot.  

After about ten minutes or so, it seems that both sqlservr.exe and nicitdl5.exe are pretty stable just below 50M each.  I'll keep an eye on things throughout the day.  Hopefully this has done the trick.

Thanks again for the tip. It's a good one!  

[pallen]

---

Davidek wrote:

Hi Patrick

That's the same error message I got, but I could log in and change the memory settings using the application I linked in my last post. There it by default used my Windows username and a blank password to log in. It also specified a server name as "mycomputername"\SQLEXPRESS. So I tried using the the command:

C:\>osql -S LAPTOP\SQLSERVER -E

That got me somewhere, just need to find the command for changing memory allocation. But like I said, it worked using the Microsoft app.

---

 

I figured that when I logged in with the app that the same connection details would work for the command line.  That's good to know.  

One odd thing is that when I first started up the MS application, it stated that Max memory was already configured for 256M.  I know for sure that I've seen it grow way beyond that, so I'm wondering if the limit was imposed as a "default" when the application was installed.

This could certainly have been a "Gotchya" for me on an upcoming project.  Now I will set the memory limits as part of my initial setup.  

Sweet.  No service calls.  

 

(......I hope)