Few good commands run from RUN to give information about OS is
msinfo32
msconfig
perfmon
Some sp_readerrorlog
DBCC memorystatus
Wednesday, August 22, 2007
Tuesday, August 21, 2007
SQL 2000 Ent Ed and Win 2k3 Ent Ed, 3 GB memory
Recently I had to move huge SQL data base from fast SAN to slow array.
after successfully planning and reducing downtime from two- three days to two hours.
and even online new system we are gotten in to problem of making SQL server use more than 3GB of memory.
From web sites
http://support.microsoft.com/kb/274750
http://www.sql-server-performance.com/articles/per/awe_memory_sql2000_p1.aspx
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=56145
Changes I made are
1. in boot file apply /PAE and /3GB switch
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003, Enterprise" /PAE /3GB /fastdetect /NoExecute=OptOut
2. on SQL server apply AWE and MAX MEMORY LIMIT.
RECONFIGURE
GO
SP_CONFIGURE 'max server memory', 5120
RECONFIGURE
GO
Points to remember:
**PAE switch allows Ent Ed and Data Center Ed, Win Server to use more than 4 GB of Memory(Enable more then 4 GB RAM on 32 bit system)
**/3GB switch restrict the OS to use only 1 GB of memory out of 4 GB (in a 32 bit system). use if switch is preferred when
RAM is 8 GB or Less. so that application can utilize maximum of memory.
When RAM is more than 8 GB, should used /3Gb switch as it effects performance of OS to manage the big memory.
** AWE enable the SQL to use more than 3GB memory when system is PAE enabled.
also you need to specify the max memory used of SQL other wise it eats up all memory and chock the server performance....(leaving only 128 MB for OS)
(Initially posted on Agt 21, 2007)
found the fix
installed was SQLserver 2000 EE sp4(version 2039) and above was known issue to this build.
and upgraded it to SQLserver 2000 EE sp4(version 2040)
after successfully planning and reducing downtime from two- three days to two hours.
and even online new system we are gotten in to problem of making SQL server use more than 3GB of memory.
From web sites
http://support.microsoft.com/kb/274750
http://www.sql-server-performance.com/articles/per/awe_memory_sql2000_p1.aspx
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=56145
Changes I made are
1. in boot file apply /PAE and /3GB switch
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003, Enterprise" /PAE /3GB /fastdetect /NoExecute=OptOut
2. on SQL server apply AWE and MAX MEMORY LIMIT.
SP_CONFIGURE 'show advanced options', 1
RECONFIGURE
GO
RECONFIGURE
GO
SP_CONFIGURE 'max server memory', 5120
RECONFIGURE
GO
Points to remember:
**PAE switch allows Ent Ed and Data Center Ed, Win Server to use more than 4 GB of Memory(Enable more then 4 GB RAM on 32 bit system)
**/3GB switch restrict the OS to use only 1 GB of memory out of 4 GB (in a 32 bit system). use if switch is preferred when
RAM is 8 GB or Less. so that application can utilize maximum of memory.
When RAM is more than 8 GB, should used /3Gb switch as it effects performance of OS to manage the big memory.
** AWE enable the SQL to use more than 3GB memory when system is PAE enabled.
also you need to specify the max memory used of SQL other wise it eats up all memory and chock the server performance....(leaving only 128 MB for OS)
(Initially posted on Agt 21, 2007)
found the fix
installed was SQLserver 2000 EE sp4(version 2039) and above was known issue to this build.
and upgraded it to SQLserver 2000 EE sp4(version 2040)
Fix: Not All Memory is Available When AWE is Enabled on a Computer Running 32-bit Version of SQL Server 2000 SP4 (899761)
Subscribe to:
Posts (Atom)