Results 1 to 5 of 5
  1. #1
    Join Date
    Oct 2002
    Posts
    1

    Unanswered: Getting "WARNING: Failed to reserve contiguous memory of Size= 65536." error

    Getting this error intermittently. SQL 2000 Enterprise w/SP2. Active/Active cluster. 8 GB RAM. No AWE. Memory set to 3.5GB. Only 1.5GB used by SQL Server. Thanks for your help.

  2. #2
    Join Date
    Apr 2003
    Posts
    2

    Re: Getting "WARNING: Failed to reserve contiguous memory of Size= 65536." error

    Originally posted by tknoob
    Getting this error intermittently. SQL 2000 Enterprise w/SP2. Active/Active cluster. 8 GB RAM. No AWE. Memory set to 3.5GB. Only 1.5GB used by SQL Server. Thanks for your help.
    We got the same problem. We have a procedure that runs through a large amounts of records and when it runs on smaller amounts it doesn't fail. We have a test server on which the procedure works, so it is only on our live server the problem exist.

    Live server:
    SQL Server 2000 SP3
    Windows 2000 Server SP3
    2 GB memory
    4 Processors

    Test Server:
    SQL Server 2000 SP3
    Windows 2000 Server SP3
    1 GB memory
    2 Processors

    If we change the database to "Database Combability level 70" instead of "Database Combability level 80" the problem goes away, but we would really like to run with full SQL Server 2000 functionality.

    Anyone knows a solution? Thanks for your help!

  3. #3
    Join Date
    Jul 2003
    Posts
    1

    Re: Getting "WARNING: Failed to reserve contiguous memory of Size= 65536." error

    Originally posted by tknoob
    Getting this error intermittently. SQL 2000 Enterprise w/SP2. Active/Active cluster. 8 GB RAM. No AWE. Memory set to 3.5GB. Only 1.5GB used by SQL Server. Thanks for your help.
    Did you find a solutions for this problem?. We have a active/passive cluster with the same configuration and we are getting the same message. Any comments or suggestions will be greatly appreciated!.

  4. #4
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    I occasionally get the same problem when trying to use SQL Profiler. Unfortunately, I am not too sure where to look to find more information. DBCC memorystatus dumps a lot of numbers out, but not a whole lot of them mean a whole lot to me. If anyone knows any way of troubleshooting, or isolating this problem, I would certainly like to hear about it.

  5. #5
    Join Date
    Apr 2003
    Posts
    2
    We have found a way around it, since it only happens to us on ADO 2.7 when we bombard the server with unparameterized requests. We have changed the most repeated sql which where running in loops to parameterized ADO-commands to utilize the cache better as it seemed to get flooded.

    This is the resulting commands on the SQL-server

    Before:
    SELECT * FROM Clients WHERE ClientID = 1

    After:
    DECLARE @ClientID int
    SET @ClientID = 1
    SELECT * FROM Clients WHERE ID = @ClientID

    The last one utilizes the proc cache while the first doesn't when you change the client id.

    Also making stored procedures would be an even better improvement.

    This is only a work around. There must be a problem in SQL Server 2000 with deallocation of memory.
    Last edited by MartinJ; 07-18-03 at 04:46.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •