April 21, 2010 at 4:04 am
Hello,
I have followed the instructions to the letter to enable 'Lock Pages In Memory' for SQL Server 2005 x64 SP3 CU4. I see the trace flag in the log but not the following text:
Using locked pages for buffer pool
The server is still suffering from memory trims. I can't see why it would make a difference but this is a clustered environment. The log from startup is below any help would be much appreciated.
04/21/2010 01:46:03,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67504<c/> committed (KB): 132396<c/> memory utilization: 50%.
04/21/2010 01:44:56,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67460<c/> committed (KB): 132284<c/> memory utilization: 50%.
04/21/2010 01:43:49,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67564<c/> committed (KB): 132484<c/> memory utilization: 50%.
04/21/2010 01:42:42,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67448<c/> committed (KB): 132372<c/> memory utilization: 50%.
04/21/2010 01:41:40,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 60376<c/> committed (KB): 125228<c/> memory utilization: 48%.
04/21/2010 01:40:29,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67576<c/> committed (KB): 132540<c/> memory utilization: 50%.
04/21/2010 01:39:22,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67568<c/> committed (KB): 132500<c/> memory utilization: 50%.
04/21/2010 01:38:15,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67580<c/> committed (KB): 132580<c/> memory utilization: 50%.
04/21/2010 01:37:08,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67580<c/> committed (KB): 132524<c/> memory utilization: 50%.
04/21/2010 01:36:00,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67724<c/> committed (KB): 132796<c/> memory utilization: 50%.
04/21/2010 01:34:54,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67564<c/> committed (KB): 132580<c/> memory utilization: 50%.
04/21/2010 01:33:47,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67612<c/> committed (KB): 132596<c/> memory utilization: 50%.
04/21/2010 01:30:28,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67472<c/> committed (KB): 132540<c/> memory utilization: 50%.
04/21/2010 01:29:21,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67732<c/> committed (KB): 132820<c/> memory utilization: 50%.
04/21/2010 01:28:14,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67712<c/> committed (KB): 132796<c/> memory utilization: 50%.
04/21/2010 01:27:07,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67576<c/> committed (KB): 132572<c/> memory utilization: 50%.
04/21/2010 01:26:00,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67844<c/> committed (KB): 133028<c/> memory utilization: 50%.
04/21/2010 01:24:53,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67748<c/> committed (KB): 132884<c/> memory utilization: 50%.
04/21/2010 01:23:46,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 62800<c/> committed (KB): 127924<c/> memory utilization: 49%.
04/21/2010 01:22:37,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67792<c/> committed (KB): 132948<c/> memory utilization: 50%.
04/21/2010 01:20:24,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67684<c/> committed (KB): 132860<c/> memory utilization: 50%.
04/21/2010 01:19:18,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67816<c/> committed (KB): 133012<c/> memory utilization: 50%.
04/21/2010 01:18:11,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67804<c/> committed (KB): 132956<c/> memory utilization: 50%.
04/21/2010 01:17:04,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67780<c/> committed (KB): 132932<c/> memory utilization: 50%.
04/21/2010 01:15:58,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 68076<c/> committed (KB): 133540<c/> memory utilization: 50%.
04/21/2010 01:14:51,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67908<c/> committed (KB): 133180<c/> memory utilization: 50%.
04/21/2010 01:13:44,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67972<c/> committed (KB): 133284<c/> memory utilization: 50%.
04/21/2010 01:12:37,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 67804<c/> committed (KB): 132956<c/> memory utilization: 50%.
04/21/2010 01:07:06,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 72504<c/> committed (KB): 142172<c/> memory utilization: 50%.
04/21/2010 01:01:34,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 72428<c/> committed (KB): 142108<c/> memory utilization: 50%.
04/21/2010 00:57:10,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 72568<c/> committed (KB): 142300<c/> memory utilization: 50%.
04/21/2010 00:51:38,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 72752<c/> committed (KB): 142668<c/> memory utilization: 50%.
04/21/2010 00:47:11,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 72824<c/> committed (KB): 142836<c/> memory utilization: 50%.
04/21/2010 00:41:41,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 73272<c/> committed (KB): 143764<c/> memory utilization: 50%.
04/21/2010 00:37:16,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 72644<c/> committed (KB): 143316<c/> memory utilization: 50%.
04/21/2010 00:31:44,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 74052<c/> committed (KB): 145212<c/> memory utilization: 50%.
04/21/2010 00:26:12,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 75384<c/> committed (KB): 148060<c/> memory utilization: 50%.
04/21/2010 00:25:05,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 56480<c/> committed (KB): 151060<c/> memory utilization: 37%.
04/21/2010 00:22:50,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 3008<c/> committed (KB): 427316<c/> memory utilization: 0%.
04/20/2010 11:11:17,spid58,Unknown,Using 'xpSLS.dll' version '0005.01.00' to execute extended stored procedure 'xp_slssqlmaint'. This is an informational message only; no user action is required.
04/20/2010 11:03:05,spid51s,Unknown,StartService() returned error 5<c/> 'Access is denied.'
04/20/2010 11:03:05,spid51s,Unknown,Error: 22003<c/> Severity: 16<c/> State: 1.
04/20/2010 11:02:55,spid52,Unknown,Using 'xplog70.dll' version '2005.90.4035' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
04/20/2010 11:02:55,spid52,Unknown,Using 'xpsqlbot.dll' version '2005.90.4035' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
04/20/2010 11:02:55,spid52,Unknown,Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
04/20/2010 11:02:55,spid52,Unknown,Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
04/20/2010 11:02:55,spid52,Unknown,Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
04/20/2010 11:02:55,spid51s,Unknown,Using 'xpstar90.dll' version '2005.90.4035' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
04/20/2010 11:02:54,spid7s,Unknown,Launched startup procedure 'usp_reset_subsystem_path'.
04/20/2010 11:02:54,spid14s,Unknown,Service Broker manager has started.
04/20/2010 11:02:54,spid14s,Unknown,The Database Mirroring protocol transport is disabled or not configured.
04/20/2010 11:02:54,spid14s,Unknown,The Service Broker protocol transport is disabled or not configured.
04/20/2010 11:02:48,Server,Unknown,SQL Server is now ready for client connections. This is an informational message; no user action is required.
04/20/2010 11:02:48,Server,Unknown,The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098<c/> state: 15. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
04/20/2010 11:02:48,Server,Unknown,Dedicated admin connection support was established for listening locally on port 2770.
04/20/2010 11:02:48,Server,Unknown,Server is listening on [ 127.0.0.1 <ipv4> 2770].
04/20/2010 11:02:48,Server,Unknown,Server is listening on [ 'any' <ipv4> 10009].
04/20/2010 11:02:48,Server,Unknown,A self-generated certificate was successfully loaded for encryption.
04/20/2010 11:02:48,spid11s,Unknown,Starting up database 'model'.
04/20/2010 11:02:46,spid7s,Unknown,The resource database build version is 9.00.4226. This is an informational message only. No user action is required.
04/20/2010 11:02:45,spid7s,Unknown,Starting up database 'mssqlsystemresource'.
04/20/2010 11:02:44,spid7s,Unknown,SQL Trace ID 1 was started by login "sa".
04/20/2010 11:02:42,spid7s,Unknown,CHECKDB for database 'master' finished without errors on 2010-04-20 07:21:33.420 (local time). This is an informational message only; no user action is required.
04/20/2010 11:02:39,spid7s,Unknown,Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
04/20/2010 11:02:39,spid7s,Unknown,0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
04/20/2010 11:02:38,spid7s,Unknown,6 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
04/20/2010 11:02:35,spid2s,Unknown,A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 51188<c/> committed (KB): 103412<c/> memory utilization: 49%.
04/20/2010 11:02:35,spid7s,Unknown,Starting up database 'master'.
04/20/2010 11:02:35,Server,Unknown,Database mirroring has been enabled on this instance of SQL Server.
04/20/2010 11:02:35,Server,Unknown,Resource Manager Creation Failed: 0x8004d01c(error not found)
04/20/2010 11:02:35,Server,Unknown,Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
04/20/2010 11:02:35,Server,Unknown,Multinode configuration: node 1: CPU mask: 0x00000000000000ff Active CPU mask: 0x00000000000000ff. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
04/20/2010 11:02:35,Server,Unknown,Multinode configuration: node 0: CPU mask: 0x000000000000ff00 Active CPU mask: 0x000000000000ff00. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
04/20/2010 11:02:35,Server,Unknown,Lock partitioning is enabled. This is an informational message only. No user action is required.
04/20/2010 11:02:35,Server,Unknown,Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
04/20/2010 11:02:34,Server,Unknown,Detected 16 CPUs. This is an informational message; no user action is required.
04/20/2010 11:02:34,Server,Unknown,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
04/20/2010 11:02:34,Server,Unknown,-T845
04/20/2010 11:02:34,Server,Unknown,-l G:\SS\DATA\mastlog.ldf
04/20/2010 11:02:34,Server,Unknown,-e G:\SS\Log\ERRORLOG
04/20/2010 11:02:34,Server,Unknown,-d G:\SS\DATA\master.mdf
04/20/2010 11:02:34,Server,Unknown,Registry startup parameters:
04/20/2010 11:02:34,Server,Unknown,This instance of SQL Server last reported using a process ID of 6068 at 20/04/2010 11:01:59 (local) 20/04/2010 10:01:59 (UTC). This is an informational message only; no user action is required.
04/20/2010 11:02:34,Server,Unknown,Logging SQL Server messages in file 'G:\SS\Log\ERRORLOG'.
04/20/2010 11:02:34,Server,Unknown,Authentication mode is WINDOWS-ONLY.
04/20/2010 11:02:34,Server,Unknown,Server process ID is 10300.
04/20/2010 11:02:34,Server,Unknown,All rights reserved.
04/20/2010 11:02:34,Server,Unknown,(c) 2005 Microsoft Corporation.
04/20/2010 11:02:34,Server,Unknown,Microsoft SQL Server 2005 - 9.00.4226.00 (X64) <nl/> May 26 2009 14:58:11 <nl/> Copyright (c) 1988-2005 Microsoft Corporation<nl/> Standard Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
April 21, 2010 at 4:07 am
What changes you have done... Have u added user running SQL services for Loack pages in memory seetings and restart sql services.
hope this will work...
April 21, 2010 at 4:57 am
Hi,
The service account is a domain user and has been added to the Lock Pages in Memory local policy
The SQL Server has been patched to the SP3 CU4 update
The Trace flag -T845 has been added to the startup parameters
The server has been restarted.
Cheers
Chris
December 6, 2010 at 4:01 am
Apologies for the late post but I found my error. An errant space was the problem.
Trace flags have to be added precisely, although I can't remember seeing many warnings when reading up on it.
The flags must have no spaces what so ever, the - should follow immediately after the last ; with no space between T and the number. Example below
-dG:\ABCD\DATA\master.mdf;-eG:\ABCD\Log\ERRORLOG;-lG:\ABCD\DATA\mastlog.ldf;-T845
Cheers
Chris
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply