Post reply

SQL CLR - Memory Issue

  • January 9, 2009 at 8:24 am

    #127878

    Hello:

    We are using SQL Server 2005's CLR to create XML's and save it to a network location from SQL server data. Whenever there is large data to process, we are running into following error.

    ===========================================================================================================

    SqlErrorMessage: .NET Framework execution was aborted by escalation policy because of out of memory.

    System.Threading.ThreadAbortException: Thread was being aborted.

    System.Threading.ThreadAbortException:

    SqlErrorNumber 6532.

    ===========================================================================================================

    Questions We have are :

    1. Can we setup memory allocated for CLR? If yes, how?

    2. Is there any way to clear off this memory after each use? One solution seems to be daily restart at certain time.

    Any guidance on this would be helpful as this is causing production issue on almost daily basis.

    Thanks,

    Ramesh.

  • January 9, 2009 at 10:22 pm

    #924780

    It sounds to me as if someone built in a memory leak in the CLR.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply