Isolating Extended Procedures
Because extended procedures run in the SQL Server process space, they can wreak havoc when ill-behaved. Of particular concern is the possibility that an extended procedure can leak memory, eventually exhausting the entire MemToLeave pool. SQL Server memory is organized into two basic memory pools: the buffer pool, from which the data and procedure caches are allocated, as well as most other memory allocations; and the MemToLeave pool, which defaults to 256MB in SQL Server 2000 (128MB in SQL Server 7.0) and is the area from which extended procedure and COM in-process (e.g., OLE-DB) allocations come. You can set the size of the MemToLeave pool via SQL Server's -g command-line option.
If an extended procedure that leaks ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access