Limited SQL instances but server still struggling

Recently we came across an issue whereby one of our servers was having terrible memory issues (worse than Dory from Finding Nemo).  This should be a simple one, limit the SQL instances, we thought!

The setup was a Windows Server 2008 R2 Standard (64-bit) )with 2 SQL instances running, one for each of our main applications.  To make things a little more interesting SQL Server 2005 and SQL Server 2008 were in play.  This shouldn't be an issue though, limiting the memory is the same process for both versions!

Limiting Memory Usage for an SQL Instance

  1. Open SQL Server Management Studio
  2. Log into the first instance
  3. Right-click on the instance name at the top of the Object Explorer and select Properties
  4. Select the Memory page from the left-hand menu
  5. Enter the size of memory you want to limit your instance to (in MegaBytes)
  6. Press OK
Repeat steps 1 - 6 for each instance you have configured within your SQL server(s)

Now at this point we thought we could sit back, throw our feet on the desk and basque in our technical glory at bringing the server to a happy, purring state.  This was not to be!

We opened Task Manager and watched our sqlservr.exe (or sqlservr.exe *32) processes decrease in memory usage as we expected.  Out of nowhere, another sqlservr.exe process poked it's head out like that one creepy uncle you try to avoid at a family wedding.  We only have 2 known SQL instances so where was this 3rd one coming from.  Long story short this was the process for the Windows Internal Database.

Limiting Memory Usage for Windows Internal DB Instance

To limit the memory usage of this instance you need to go through the following steps:
  1. Open SQL Server Management Studio
    • Server type:  Database Engine
    • Server name:  \\.\pipe\mssql$microsoft##ssee\sql\query
    • Authentication:  Windows Authentication (must be Windows Auth)
  2. Right-click on the instance name at the top of the Object Explorer and select Properties
  3. Select the Memory page from the left-hand menu
  4. Enter the size of memory you want to limit your instance to (in MegaBytes)
  5. Press OK
 Personally speaking, I set the limit for the Windows Internal DB to 2GB (2048MB)


What is the Windows Internal Database used for?

The Windows Internal Database is for any of the following:
  • Active Directory Rights Management Services (AD RMS)
  • Windows Server Update Services (WSUS)
  • Windows System Resource Manager
 In our scenario WSUS is in play on the server.  This never even occurred to us as WSUS usually just sits and runs through the motions at our remote sites.  Lessons learned BUT I will report back and update if we notice that the 2GB limit is not enough for WSUS to function as well as it was previously.

I ran this query against our IT team:












Sorry, terrible joke!

Give me a shout if you have any queries!

Comments

Post a Comment

Popular posts from this blog

Add Multiple Alias Email Addresses to Exchange Online/Office 365 Mailbox

I will keep the BS short for this one BUT there are a few points to mention.  Please read as it will save you time in the long run! When running through this process you MUST specify ALL email addresses that are to be associated with the mailbox you are updating It will overwrite anything that currently exists within the Email Addresses section When specifying the email addresses be sure to pay attention to SMTP and smtp Being an absolute 1337 n00b myself, I originally ran through the process to add additional email aliases to the mailbox.  Unbeknownst to me at the time, running through this process completely overwrites what is associated with the mailbox.  So, my advice?  Create the entire Set-Mailbox  string for all email addresses before starting the process. Anyway, onto the process! If you want to add multiple alias email addresses to an Exchange Online/Office 365 account run through the following: Open Powershell Type the following comman...
Read more

WHM/cPanel/Exim Mail Server // Relaying email for specific domain(s) or email address to SMTP Smart Host or remote SMTP server

As with most of my posts, scroll to the Solution  section if you are only here for a quick fix.  BUT be sure to check out the Examples at the end of the post!    WARNING:  You will bypass my attempts at humour to make this read interesting if you skip! I recently came up against a scenario whereby a client who uses a WHM/cPanel server as a dedicated mail server.  Fine.  Easy Peasy, no issues there. These guys wanted to relay their mail through an online service for reporting and reputation reasons.  Fine, again, simple. Naive little me thought "Simple, all I gotta do is log into WHM and tell Exim where to push the mail in their sweet little web interface".  Turned out to be not so straight forward. The Scenario (long-story-short) Client uses WHM/cPanel system as dedicated mail server (Exim) Wanted to send email for specific domain to specific IP address Wanted to relay all other outbound mail via 3rd party relay serv...
Read more

Re-instating "Send As" privilege Windows 2003 Server // GOOD ForEnterprise

You may recall that I had a wonderful time troubleshooting issues with the GOOD for Enterprise service, whereby user's GOOD profiles were falling into a paused state as the service was unable to successfully send emails from the user's Android & iOS apps. GOOD For Enterprise have now outlined a permanent fix for this issue. Using the following fix will re-instate the Send As permissions for the required user accounts that the GOOD app uses to remotely send emails from their handheld apps, therefore eliminating the need to go through the workaround which I had outlined in my previous post . The Permanent Fix In order to achieve a permanent fix for this issue we need to re-instate the Send As ability that the required user accounts had before a certain Windows update removed this right, this is done using the DSACLS utility. The syntax for the correct command is as follows: dsacls "cn=adminsdholder,cn=system,dc=domainname,dc=com" /G "\GoodAdmin:CA;S...
Read more