SQL Server uses a lot of memory

Here's a little work around for SQL server which uses a lot more memory than it should. Naturally, you can set this through the properties of the instance it self. however, since this is a bug in microsoft sql server 2008 (r2?), this script is a workaround.





EXEC sys.sp_configure N'show advanced options', N'1'

RECONFIGURE WITH OVERRIDE

GO

EXEC sys.sp_configure N'max server memory (MB)', N'{low water mark}'

GO

RECONFIGURE WITH OVERRIDE

GO

EXEC sys.sp_configure N'max server memory (MB)', N'{High water mark}'

GO

RECONFIGURE WITH OVERRIDE

GO

EXEC sys.sp_configure N'show advanced options', N'0'

RECONFIGURE WITH OVERRIDE

GO
 
Low water mark : Minimum usage
High water mark : High usage max.
Credit: Jason Plank 




Popular posts from this blog

[SOLVED] Veeam: Failed change tracking (CBT)

Image
Failed to flush change tracking data, using full scan to determine changes. Failed to create change tracking time stamp for virtual disk file I've encountered the above, after i added some new CSV to a cluster. The backup jobs have been running fine for ages before this. As per say, this is not really a critical issue, since the backups just takes longer. Needless to say, i wanted it to function. I tried: Reboot Nodes, Hosts, VMs Fully update Stop VeeamFCT service and Start it again Update hyper-v integration service Delete previous backups Run full backups Read Veeam forums Running Reset-HvVmChangeTracking Din't work. However!
Read more »»»

Fixing Error 25541. Failed to open XML file

Fixing Error 25541. I had to install Compact 4.0 on a client computer today. However, i got the error below: Error 25541. Failed to open XML file C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config, system error: -2147024786 Setup failed. Rolling back  This was a huge pain in the a**, but the solution was very simple.
Read more »»»