summaryrefslogtreecommitdiff
path: root/src/SQL_Server_2008_Memory_Management.ascii
diff options
context:
space:
mode:
Diffstat (limited to 'src/SQL_Server_2008_Memory_Management.ascii')
-rw-r--r--src/SQL_Server_2008_Memory_Management.ascii72
1 files changed, 72 insertions, 0 deletions
diff --git a/src/SQL_Server_2008_Memory_Management.ascii b/src/SQL_Server_2008_Memory_Management.ascii
new file mode 100644
index 0000000..4125534
--- /dev/null
+++ b/src/SQL_Server_2008_Memory_Management.ascii
@@ -0,0 +1,72 @@
+SQL Server 2008 Memory Management
+=================================
+:author: Aaron Ball
+:email: nullspoon@iohq.net
+
+
+== {doctitle}
+
+Once again, hello all: Recently I had a problem with SQL server. I was sifting
+through the processes in Task Manager a few days ago ordered by memory
+consumption. At the top of the list for memory consumption was SQL Server
+(sqlserver.exe) weighing in at 200 megabytes of memory. I decided to look past
+that one since 200 megabytes isn't too unreasonable for SQL, especially when
+it's hosting the data for quite a few SharePoint web applications.
+
+Today, I checked again. After my server had been online for two and a half
+days, SQL server had grown to over 650 megabytes of memory (653,224 KB
+specifically). Seeing as how I have not made any changes to my local SharePoint
+environment in that time (I'm currently developing a non-SharePoint related
+project), I decided to look into putting a cap on the memory consumption of
+SQL. Originally I had 2 gigabytes of ram for my server. I added an extra
+gigabyte to that and SQL took up the additional space.
+
+As it turns out, one can put a maximun and a minimum limit on SQL. Here's how.
+
+Open up SQL Server Management Studio 2008
+
+Type in the information to connect to the server that has SQL server running on
+it and click connect.
+
+Right click the server name
+
+image:files/MgmtStudio1.jpg[height=400]
+
+Click Properties
+
+Select Memory on the left side of the window that comes up
+
+image:files/MgmtStudio2.jpg[height=400]
+
+Under Server Memory Options, adjust the minimum and maxiumum memory settings to
+what you need.
+
+Click OK
+
+Right Click the server name again
+
+Select Stop from the menu
+
+Click necessary buttons to get through the prompts
+
+Right Click the server name yet again
+
+Select Start from the menu
+
+Click the necessary buttons to get through the prompts
+
+And that's it. Mine (as in the screenshots) has yet to go over 300 megabytes of
+memory consumption.
+
+Thanks for reading.
+
+
+Dirk
+
+
+
+Category:Microsoft
+Category:MsSQL
+
+
+// vim: set syntax=asciidoc:

Generated by cgit