Discover our Clipsal Smart Home packages as seen on The Block 2018

in location


I'm looking for

  • Wholesalers
    • Uncheck All Check All
    • Expand
    • Expand
    • Expand
    • Uncheck All Check All
  • Switchboard Manufacturers
    • Uncheck All Check All

The best way to see what Clipsal electric products can do for your home is seeing them in action at a Clipsal Display Centre.

Product stock may vary according to location. If you're after a specific product range, please check with your chosen location before visiting.

10 Results
    Load More Load Complete
    Change Location

    Enabling the Lock Pages in Memory Option

    To lock the RAM allocated to SQL Server so it cannot be paged to disk to free up memory.

    Product Line
    SQL Server

    Windows Operating System

    This security setting determines which accounts can use a process to keep data in physical memory, which prevents the system from paging the data to virtual memory on disk. Exercising this privilege could significantly affect system performance by decreasing the amount of available random access memory (RAM).

    *Warning: This article contains information about editing local policies. Improper changes to the local policies can permanently damage the operating system. Consult with your system administrator to determine whether or not to enable the Lock pages in memory permission setting in Windows for the SQL service account on all SQL Server instances.*

    To enable the lock pages in memory option:

    1. Click Start > Run and type gpedit.msc in the Run dialog to open the Local Group Policy Editor.

    2. In the left pane, navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies.

    3. Expand Local Policies and select User Rights Assignment. The policies are listed in the right pane.

    4. Locate Lock pages in memory in the list and double click the policy name to open the Lock pages in memory Properties dialog.

    5. Click Add User or Group on the Local Security Setting tab.

    6. Add an account with the privileges to run sqlserver.exe and click OK to close the dialog

    7. Click OK to close the Local Group Policy Editor.

    A server reboot or a restart of the SQL Server service is not required.

    Didn’t find what you were looking for?

    Try Searching Again View Our Categories

    Need further assistance?

    Our Customer Care department provides total customer service solutions for our residential, industrial and commercial applications.

    Get Assistance