Restoring Navision on SQL I receive error 1204

GuidoGuido Member Posts: 5
edited 2004-04-06 in Navision Attain
Hi to all!

I'm trying to restore a Navision Attain 3.60 Database backup in SQL server running Win2k Server with SP4, but I receive the following error:

Microsoft Navision Attain
Si è verificato il seguente errore SQL Server accedendo alla tabella Setup Relationship Management: 1204,"HY000",[Microsoft][ODBC SQL Server Driver][SQL Server]Impossibile ottenere una risorsa LOCK in questo momento. Rieseguire l'istruzione quando il numero di utenti attivi è minore oppure chiedere all'amministratore di sistema di verificare la configurazione della memoria e dei blocchi di SQL Server.

1204,"HY000",[Microsoft][ODBC SQL Server Driver][SQL Server]The SQL Server cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users or ask the system administrator to check the SQL Server lock and memory configuration.
OK

I restored succesfully the same "fbk" in SQL Server running with Win2k SP3 !!

Can anybody help me!
Thanks in advance to everybody! :)

Comments

  • kinekine Member Posts: 12,562
    Lock resources - part from online books for SQL:
    locks Option
    Use the locks option to set the maximum number of available locks, thereby limiting the amount of memory Microsoft® SQL Server™ uses for locks. The default setting is 0, which allows SQL Server to allocate and deallocate locks dynamically based on changing system requirements.
    
    When the server is started with locks set to 0, the lock manager allocates two percent of the memory allocated to SQL Server to an initial pool of lock structures. As the pool of locks is exhausted, additional locks are allocated. The dynamic lock pool does not allocate more than 40 percent of the memory allocated to SQL Server.
    
    Generally, if more memory is required for locks than is available in current memory, and more server memory is available (the max server memory threshold has not been reached), SQL Server allocates memory dynamically to satisfy the request for locks. However, if allocating that memory would cause paging at the operating system level (for example, if another application was running on the same computer as an instance of SQL Server and using that memory), more lock space is not allocated. 
    
    Allowing SQL Server to use locks dynamically is the recommended configuration. However, you can set locks and override SQL Server's ability to allocate lock resources dynamically. Increase this value if SQL Server displays a message that you have exceeded the number of available locks. Because each lock consumes memory (96 bytes per lock), increasing this value can require increasing the amount of memory dedicated to the server.
    
    locks is an advanced option. If you are using the sp_configure system stored procedure to change the setting, you can change locks only when show advanced options is set to 1. The setting takes effect after stopping and restarting the server.
    


    Check your free memory...
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
Sign In or Register to comment.