September 8, 2009 at 7:43 am
I have been use CLR intensily for over 2 years without any problems to handle lots of automation using SP1/SP2. However after recenlty switching over to SP3 I need to restart the service ~2 days due to memory issues.
It seems as though I now have memory leaks where this was not an issue until we swithed to SP3.
background of CLR usage:
----------------------------
filesystem / ftp / zip / regex
web service calls (salesforce.com,google,mapquest,etc...)
xlst transformations
Server setup:
-------------
32bit W2003 12GB using /PAE
initially setup wo/AWE but have tried w/AWE 6GB max with no luck.
I have be using the -g switch and have been in the ranges of 512-2024.
Errors in eventvwr:
.NET Framework execution was aborted by escalation policy because of out of memory.
Any suggestions?
September 8, 2009 at 8:48 am
Are any of your CLR assembles installed with the UNSAFE permission set?
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
September 8, 2009 at 12:40 pm
Not UNSAFE, some are EXTERNAL
September 8, 2009 at 12:52 pm
You might want to take a look at this Connect issue: https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=473669&wa=wsignin1.0
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
September 8, 2009 at 4:29 pm
You are most likely running out of VAS (virtual address space). 32-bit SQL Server can only address 4GB of virtual addresses (not physical memory!)
By default only 2GB VAS is available to each user-mode process (the OS reserves the other 2GB). Note that this does not equate to physical memory - it is the pool of available virtual addresses.
You can increase it to 3GB through use of the /3GB OS switch (or /USERVA) but this is not normally recommended without guidance from Microsoft PSS.
64-bit editions of SQL Server can address 8TB of virtual addresses (7TB on Itanium). This is the recommended solution.
Be sure to read and understand the following Technet article and links before you do anything. It is a complex subject (on 32-bit).
http://blogs.technet.com/beatrice/archive/2008/08/29/3gb-pae-and-awe-taking-away-some-confusion.aspx
Paul
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply