Reply to thread

Message

<blockquote data-quote="jimbeam128" data-source="post: 347541" data-attributes="member: 85829">I found a thread and that worked for me:Here an extract for that thread:This is for SBS SQL Monitoring Database, but works also for all other databases. Just enter it in the command line. Then you do not have to install the SQL Server Management Studio on your htpc or any other computer....<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" />So, how to limit RAM usage for SBS SQL monitoring database?First, go with your Task Manager and underView -&gt; Select Columnscheck PID and Virtual Memory Size.Then see PID for the sqlservr.exe process which consumes large amount of RAM.Then go to CMD Command prompt and enter this command:tasklist /svc | find &quot;sql&quot;You'll get something like this:Koda:C:&gt;tasklist /svc|find &quot;sql&quot;sqlservr.exe&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 1628 MSSQL$MICROSOFT##SSEEsqlservr.exe&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 1724 MSSQL$SBSMONITORINGsqlagent.EXE&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2868 SQLAgent$SBSMONITORINGsqlwriter.exe&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; 2952 SQLWritersqlmangr.exe&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; 10832 N/AFind the PID from Task Manager in the list from this command. Most probably it is MSSQL$SBSMONITORING process which is guilty for large RAM consumption.If this is true, you may limit it via Command prompt entering these commands (what you need to type is marked bold):C:&gt;osql -E -S SERVERNAME\SBSMONITORING1&gt; sp_configure 'show advanced options',12&gt; reconfigure with override3&gt; goConfiguration option 'show advanced options' changed from 0 to 1. Run theRECONFIGURE statement to install.1&gt; sp_configure 'max server memory',702&gt; reconfigure with override3&gt; goDBCC execution completed. If DBCC printed error messages, contact your systemadministrator.Configuration option 'max server memory (MB)' changed from 2147483647 to 70.Run the RECONFIGURE statement to install.1&gt; exitC:&gt;Note: Replace SERVERNAME, SBSMONITORING and number 70 with values to match your system!As you see, by design SBS monitoring database has a limit of 2147483647 MB of memory, so it can eat up practically all your RAM!The 70 MB limit here shown is just a guess, and my recommendation is to use some value between 70 and 300, depending on your free RAM.Have your Task Manager open and watch your sqlservr.exe process how it releases RAM imidiatelly after you issue these commands. Many people have used this hack and all are happy with server behaviour. No side effects have been noticed (as far as I know).</blockquote>

[QUOTE="jimbeam128, post: 347541, member: 85829"] I found a thread and that worked for me: Here an extract for that thread: This is for SBS SQL Monitoring Database, but works also for all other databases. Just enter it in the command line. Then you do not have to install the SQL Server Management Studio on your htpc or any other computer....:D So, how to limit RAM usage for SBS SQL monitoring database? First, go with your Task Manager and under View -> Select Columns check PID and Virtual Memory Size. Then see PID for the sqlservr.exe process which consumes large amount of RAM. Then go to CMD Command prompt and enter this command: tasklist /svc | find "sql" You'll get something like this: Koda: C:>tasklist /svc|find "sql" sqlservr.exe 1628 MSSQL$MICROSOFT##SSEE sqlservr.exe 1724 MSSQL$SBSMONITORING sqlagent.EXE 2868 SQLAgent$SBSMONITORING sqlwriter.exe 2952 SQLWriter sqlmangr.exe 10832 N/A Find the PID from Task Manager in the list from this command. Most probably it is MSSQL$SBSMONITORING process which is guilty for large RAM consumption. If this is true, you may limit it via Command prompt entering these commands (what you need to type is marked bold): C:>osql -E -S SERVERNAME\SBSMONITORING 1> sp_configure 'show advanced options',1 2> reconfigure with override 3> go Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install. 1> sp_configure 'max server memory',70 2> reconfigure with override 3> go DBCC execution completed. If DBCC printed error messages, contact your system administrator. Configuration option 'max server memory (MB)' changed from 2147483647 to 70. Run the RECONFIGURE statement to install. 1> exit C:> Note: Replace SERVERNAME, SBSMONITORING and number 70 with values to match your system! As you see, by design SBS monitoring database has a limit of 2147483647 MB of memory, so it can eat up practically all your RAM! The 70 MB limit here shown is just a guess, and my recommendation is to use some value between 70 and 300, depending on your free RAM. Have your Task Manager open and watch your sqlservr.exe process how it releases RAM imidiatelly after you issue these commands. Many people have used this hack and all are happy with server behaviour. No side effects have been noticed (as far as I know). [/QUOTE]

Verification