Lock Pages in Memory

External Article

Great SQL Server Debates: Lock Pages in Memory

  • Article

There has been much debate over the need for the Lock Pages in Memory privilege, on 64-bit versions of SQL Server. Jonathan Kehayias presents a "warts and all" account of its history, the confusions surrounding its use, and why he believes it's still a good default configuration for 64-bit SQL Server instances, even when running Windows Server 2008 and Windows Server 2008R2.

2011-12-29

2,878 reads

Blogs

A New Word: the Wends

By

the wends– n. the frustration that you’re not enjoying an experience as much as...

7 Best Online Advanced SQL Training Courses to Learn in 2024 and Beyond

By

The world runs on data, and SQL is the key to unlocking its secrets....

Manually Updating Redgate Monitor/SQL Monitor Patch Info

By

This post looks at updating the patch information for SQL Monitor/Redgate Monitor without using...

Read the latest Blogs

Forums

Upgrading SSRS 2016 to SSRS 2019 in place

By koln

Server A has SSRS 2016 on it and I would now like to upgrade...

Pipeline Failure Route not working

By rjdineen

Hi there, I have a couple of Stored Proc tasks, that fire off after...

extracting cloud based netsuite data from the cloud in ssis

By stan

Hi we are going to need to extract netsuite data from the cloud.  This...

Visit the forum

Question of the Day

Default Objects in Clones

On SQL Server 2022, I do this:

USE model
GO
CREATE TABLE dbo.DBALog
(logdate DATETIME2(3), logmsg VARCHAR(2000))
GO
I then create a new database:
CREATE DATABASE INVENTORY
GO
I install a new database application in here with multiple tables, views, etc. I do not run any queries. I then decide to run this code:
DBCC CLONEDATABASE(INVENTORY, Inventory_clone);
GO
What happens?

See possible answers