Hi Everyone,
I'm running a non-clustered sql environment, and I was
considering the scenario where I could install multiple
instances of sql server onto one "work-horse" server.
I'm concerned about the 2 Gb memory limit. Is this limit
per instance, or per physical machine?
E.g. one quad-processor server, with 6 Gb of memory
could easily accept 2 sql instances each with a 2Gb
memory limit.
Thanks in Advance
CraigHi,
This limitation in Memory / Cpu is instance based. So if you have 2 SQL
server instances you can allocate a maximum of 2 GB RAM for each instance.
FYI,
If your SQL Server edition is Enterprise edition it supports more than 2 GB
RAM for each instance. See books online on "Maximum Capacity specifications"
Thanks
Hari
MCDBA
Thanks
Hari
MCDBA
"Craig Irvine" <anonymous@.discussions.microsoft.com> wrote in message
news:cd6601c43940$2592e2d0$a601280a@.phx.gbl...
> Hi Everyone,
> I'm running a non-clustered sql environment, and I was
> considering the scenario where I could install multiple
> instances of sql server onto one "work-horse" server.
> I'm concerned about the 2 Gb memory limit. Is this limit
> per instance, or per physical machine?
> E.g. one quad-processor server, with 6 Gb of memory
> could easily accept 2 sql instances each with a 2Gb
> memory limit.
> Thanks in Advance
> Craig
>|||Hi Craig,
The 2GB Memory limitation is per instance and the SQL Server can be
configured to use more memory than 2GB. Please refer to the following
article
http://support.microsoft.com/defaul...0&Product=sql2k
Excerpt from the KB Article
HOW TO: Configure memory for more than 2 GB in SQL Server
View products that this article applies to.
This article was previously published under Q274750
IN THIS TASK
SUMMARY
Support for Operating System Versions
Microsoft Windows 2000 Server
Microsoft SQL Server 2000
Microsoft SQL Server 7.0
Microsoft Windows 2000 Advanced Server or Microsoft Windows 2000 Datacenter
or Windows Server 2003
Microsoft SQL Server 2000
Microsoft SQL Server 7.0
Microsoft Windows NT 4.0 Enterprise Edition
REFERENCES
SUMMARY
This article describes how to configure SQL Server to use more than 2 GB of
physical memory.
Microsoft SQL Server 7.0 and Microsoft SQL Server 2000 dynamically acquire
and free memory as needed. When you run multiple instances of SQL Server on
a computer, each instance dynamically acquires and frees memory to adjust
for changes in the workload of the instance.
SQL Server 2000 Enterprise Edition introduces support for the use of
Microsoft Windows 2000 Address Windowing Extensions (AWE) to address
approximately 8 GB of memory for instances that run on Microsoft Windows
2000 Advanced Server, and approximately 32 GB for instances that run on
Microsoft Windows 2000 Datacenter. With AWE, SQL Server can reserve memory
that is not in use for other applications and the operating system. Each
instance that uses this memory; however, must statically allocate the
memory it needs. SQL Server can only use this AWE allocated memory for the
data cache and not for executables, drivers, DLLs, and so forth. For
additional information, click the article number below to view the article
in the Microsoft Knowledge
Base:
283037 Large Memory Support Is Available in Windows 2000
The extended memory size option is available only for Microsoft SQL Server
7.0, Enterprise Edition on the operating system and hardware that supports
the Enterprise Memory Architecture (EMA) feature. For more information
about how to configure your system to enable the EMA feature on a
particular system configuration, refer to your Microsoft Windows NT
documentation.
Some system vendors may provide products for Microsoft Windows NT, version
4.0 or later, so that SQL Server 7.0, Enterprise Edition can use the
extended memory size option. On Intel platforms, SQL Server 7.0 can use a
feature known as PSE36. On Alpha platforms, the feature that allows use of
the extended memory option is Very Large Memory (VLM). For more information
about the availability, installation, and configuration of these products,
contact your system vendor.
Note: To use Address Windowing Extensions (AWE) memory, you must run the
SQL Server 2000 database engine under a Windows account that has been
assigned the Windows lock pages in memory administrative credentials.
back to the top
Support for Operating System Versions
Windows 2000 Server
SQL Server 2000
Normally, both the SQL Server 2000 Enterprise Edition and SQL Server 2000
Developer Edition can use up to 2 GB of physical memory. With the use of
the AWE enable option, SQL Server can use up to 4 GB of physical memory.
NOTE: You cannot allocate more than 4 GB of physical memory to an
application on Windows 2000 Server because Physical Address Extension (PAE)
is not available on Microsoft Windows 2000 Server. Also, you cannot use the
3 GB switch in the Boot.ini file with Windows 2000 Server; however, you can
use the 3 GB switch in the Boot.ini file with Microsoft Windows 2000
Advanced Server or Microsoft Windows Datacenter versions. For additional
information, click the article number below to view the article in the
Microsoft Knowledge Base:
291988 A Description of the 4 GB RAM Tuning Feature and the Physical
Address Extension Switch
back to the top
SQL Server 7.0
SQL Server 7.0 versions can use up to 2 GB of physical memory.
NOTE: The extended memory option in SQL Server 7.0 is not available on
Windows 2000.
Windows 2000 Advanced Server or Windows 2000 Datacenter or Windows Server
2003
The maximum amount of physical memory addressable by a 32-bit addressing
mode is 4 GB. All processors based on the IA-32 architecture that begin
with the Intel Pentium Pro, support a new 36-bit physical addressing mode
known as Physical Address Extension (PAE). PAE allows up to 8 GB of
physical memory on Windows 2000 Advanced Server and up to 32 GB of physical
memory on Windows 2000 Datacenter Server. This is because the tested memory
limit on Windows 2000 Datacenter Server is 32 GB. The PAE mode kernel
requires an Intel architecture processor, Pentium Pro, or later and either
Windows 2000 Advanced Server or Windows 2000 Datacenter. For additional
information, click the article number below to view the article in the
Microsoft
Knowledge Base:
268230 Scaling Out Versus Scaling Up with Intel Physical Addressing
Extensions (PAE)
Note The maximum amount of memory that can be supported on Windows Server
2003 is 4 GB. However, Windows Server 2003 Enterprise Edition supports 32
GB of physical RAM. Windows Server 2003 Datacenter Edition supports 64 GB
of physical RAM by using the Physical Address Extensions (PAE) feature. You
can use the 3 GB switch that is in the Boot.ini file with Microsoft Windows
Server 2003, Microsoft Windows Server 2003 Enterprise Edition, or with
Microsoft Windows Server 2003 Datacenter Edition.
SQL Server 2000
Both SQL Server 2000 Enterprise and SQL Server 2000 Developer Editions can
use the following options:
Use of the /PAE switch in the Boot.ini and the AWE enable option in SQL
Server allows SQL Server 2000 to utilize more than 4 GB memory. Without the
/PAE switch SQL Server can only utilize up to 4 GB of memory.
NOTE: To allow AWE to use the memory range above 16 GB on Windows 2000 Data
Center, make sure that the /3GB switch is not in the Boot.ini file. If the
/3GB switch is in the Boot.ini file, Windows 2000 may not be able to
address any memory above 16 GB correctly.
When you allocate SQL Server AWE memory on a 32 GB system, Windows 2000 may
require at least 1 GB memory to manage AWE.
back to the top
Example
The following example shows how to enable AWE and configure a limit of 6 GB
for the max server memory option: sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
-or-
-or-Use of the /3GB switch in the Boot.ini file allows SQL Server 2000 to
use up to 3 GB of available memory.
back to the top
SQL Server 7.0
SQL Server 7.0 Enterprise Edition requires the /3GB switch in the Boot.ini
in order to address up to 3 GB of available memory.
NOTE: The extended memory option in SQL Server 7.0 is not available on
Windows 2000 Advanced Server or Windows Datacenter.
Microsoft Windows NT 4.0 Enterprise Edition
SQL Server 2000
SQL Server 2000 Enterprise and Developer Edition requires the /3GB switch
in the Boot.ini file in order to address up to 3 GB of available memory.
NOTE: Windows NT 4.0 Enterprise Edition does not support the AWE memory
architecture model so AWE support is not available.
back to the top
SQL Server 7.0
SQL Server 7.0 Enterprise Edition requires the /3GB switch in the Boot.ini
file in order to address up to 3 GB of available memory.
back to the top
REFERENCES
For additional information, click the article numbers below to view the
articles in the Microsoft Knowledge Base:
170756 Available Switch Options for Windows NT Boot.ini File
171793 Information on Application Use of 4GT RAM Tuning
268363 Intel Physical Addressing Extensions (PAE) in Windows 2000
292934 Windows 2000 Datacenter Server Does Not Locate Memory Greater Than
16 GB
SQL Server 2000 Books Online; topics: "Managing AWE Memory"; "Running
Multiple Instances and Using Failover Clustering"
back to the top
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
Showing posts with label memory. Show all posts
Showing posts with label memory. Show all posts
Wednesday, March 28, 2012
multiple instances of sql - 2 Gb memory limitation?
Hi Everyone,
I'm running a non-clustered sql environment, and I was
considering the scenario where I could install multiple
instances of sql server onto one "work-horse" server.
I'm concerned about the 2 Gb memory limit. Is this limit
per instance, or per physical machine?
E.g. one quad-processor server, with 6 Gb of memory
could easily accept 2 sql instances each with a 2Gb
memory limit.
Thanks in Advance
Craig
Hi,
This limitation in Memory / Cpu is instance based. So if you have 2 SQL
server instances you can allocate a maximum of 2 GB RAM for each instance.
FYI,
If your SQL Server edition is Enterprise edition it supports more than 2 GB
RAM for each instance. See books online on "Maximum Capacity specifications"
Thanks
Hari
MCDBA
Thanks
Hari
MCDBA
"Craig Irvine" <anonymous@.discussions.microsoft.com> wrote in message
news:cd6601c43940$2592e2d0$a601280a@.phx.gbl...
> Hi Everyone,
> I'm running a non-clustered sql environment, and I was
> considering the scenario where I could install multiple
> instances of sql server onto one "work-horse" server.
> I'm concerned about the 2 Gb memory limit. Is this limit
> per instance, or per physical machine?
> E.g. one quad-processor server, with 6 Gb of memory
> could easily accept 2 sql instances each with a 2Gb
> memory limit.
> Thanks in Advance
> Craig
>
|||Hi Craig,
The 2GB Memory limitation is per instance and the SQL Server can be
configured to use more memory than 2GB. Please refer to the following
article
http://support.microsoft.com/default...&Product=sql2k
Excerpt from the KB Article
HOW TO: Configure memory for more than 2 GB in SQL Server
View products that this article applies to.
This article was previously published under Q274750
IN THIS TASK
SUMMARY
Support for Operating System Versions
Microsoft Windows 2000 Server
Microsoft SQL Server 2000
Microsoft SQL Server 7.0
Microsoft Windows 2000 Advanced Server or Microsoft Windows 2000 Datacenter
or Windows Server 2003
Microsoft SQL Server 2000
Microsoft SQL Server 7.0
Microsoft Windows NT 4.0 Enterprise Edition
REFERENCES
SUMMARY
This article describes how to configure SQL Server to use more than 2 GB of
physical memory.
Microsoft SQL Server 7.0 and Microsoft SQL Server 2000 dynamically acquire
and free memory as needed. When you run multiple instances of SQL Server on
a computer, each instance dynamically acquires and frees memory to adjust
for changes in the workload of the instance.
SQL Server 2000 Enterprise Edition introduces support for the use of
Microsoft Windows 2000 Address Windowing Extensions (AWE) to address
approximately 8 GB of memory for instances that run on Microsoft Windows
2000 Advanced Server, and approximately 32 GB for instances that run on
Microsoft Windows 2000 Datacenter. With AWE, SQL Server can reserve memory
that is not in use for other applications and the operating system. Each
instance that uses this memory; however, must statically allocate the
memory it needs. SQL Server can only use this AWE allocated memory for the
data cache and not for executables, drivers, DLLs, and so forth. For
additional information, click the article number below to view the article
in the Microsoft Knowledge
Base:
283037 Large Memory Support Is Available in Windows 2000
The extended memory size option is available only for Microsoft SQL Server
7.0, Enterprise Edition on the operating system and hardware that supports
the Enterprise Memory Architecture (EMA) feature. For more information
about how to configure your system to enable the EMA feature on a
particular system configuration, refer to your Microsoft Windows NT
documentation.
Some system vendors may provide products for Microsoft Windows NT, version
4.0 or later, so that SQL Server 7.0, Enterprise Edition can use the
extended memory size option. On Intel platforms, SQL Server 7.0 can use a
feature known as PSE36. On Alpha platforms, the feature that allows use of
the extended memory option is Very Large Memory (VLM). For more information
about the availability, installation, and configuration of these products,
contact your system vendor.
Note: To use Address Windowing Extensions (AWE) memory, you must run the
SQL Server 2000 database engine under a Windows account that has been
assigned the Windows lock pages in memory administrative credentials.
back to the top
Support for Operating System Versions
Windows 2000 Server
SQL Server 2000
Normally, both the SQL Server 2000 Enterprise Edition and SQL Server 2000
Developer Edition can use up to 2 GB of physical memory. With the use of
the AWE enable option, SQL Server can use up to 4 GB of physical memory.
NOTE: You cannot allocate more than 4 GB of physical memory to an
application on Windows 2000 Server because Physical Address Extension (PAE)
is not available on Microsoft Windows 2000 Server. Also, you cannot use the
3 GB switch in the Boot.ini file with Windows 2000 Server; however, you can
use the 3 GB switch in the Boot.ini file with Microsoft Windows 2000
Advanced Server or Microsoft Windows Datacenter versions. For additional
information, click the article number below to view the article in the
Microsoft Knowledge Base:
291988 A Description of the 4 GB RAM Tuning Feature and the Physical
Address Extension Switch
back to the top
SQL Server 7.0
SQL Server 7.0 versions can use up to 2 GB of physical memory.
NOTE: The extended memory option in SQL Server 7.0 is not available on
Windows 2000.
Windows 2000 Advanced Server or Windows 2000 Datacenter or Windows Server
2003
The maximum amount of physical memory addressable by a 32-bit addressing
mode is 4 GB. All processors based on the IA-32 architecture that begin
with the Intel Pentium Pro, support a new 36-bit physical addressing mode
known as Physical Address Extension (PAE). PAE allows up to 8 GB of
physical memory on Windows 2000 Advanced Server and up to 32 GB of physical
memory on Windows 2000 Datacenter Server. This is because the tested memory
limit on Windows 2000 Datacenter Server is 32 GB. The PAE mode kernel
requires an Intel architecture processor, Pentium Pro, or later and either
Windows 2000 Advanced Server or Windows 2000 Datacenter. For additional
information, click the article number below to view the article in the
Microsoft
Knowledge Base:
268230 Scaling Out Versus Scaling Up with Intel Physical Addressing
Extensions (PAE)
Note The maximum amount of memory that can be supported on Windows Server
2003 is 4 GB. However, Windows Server 2003 Enterprise Edition supports 32
GB of physical RAM. Windows Server 2003 Datacenter Edition supports 64 GB
of physical RAM by using the Physical Address Extensions (PAE) feature. You
can use the 3 GB switch that is in the Boot.ini file with Microsoft Windows
Server 2003, Microsoft Windows Server 2003 Enterprise Edition, or with
Microsoft Windows Server 2003 Datacenter Edition.
SQL Server 2000
Both SQL Server 2000 Enterprise and SQL Server 2000 Developer Editions can
use the following options:
Use of the /PAE switch in the Boot.ini and the AWE enable option in SQL
Server allows SQL Server 2000 to utilize more than 4 GB memory. Without the
/PAE switch SQL Server can only utilize up to 4 GB of memory.
NOTE: To allow AWE to use the memory range above 16 GB on Windows 2000 Data
Center, make sure that the /3GB switch is not in the Boot.ini file. If the
/3GB switch is in the Boot.ini file, Windows 2000 may not be able to
address any memory above 16 GB correctly.
When you allocate SQL Server AWE memory on a 32 GB system, Windows 2000 may
require at least 1 GB memory to manage AWE.
back to the top
Example
The following example shows how to enable AWE and configure a limit of 6 GB
for the max server memory option: sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
-or-
-or-Use of the /3GB switch in the Boot.ini file allows SQL Server 2000 to
use up to 3 GB of available memory.
back to the top
SQL Server 7.0
SQL Server 7.0 Enterprise Edition requires the /3GB switch in the Boot.ini
in order to address up to 3 GB of available memory.
NOTE: The extended memory option in SQL Server 7.0 is not available on
Windows 2000 Advanced Server or Windows Datacenter.
Microsoft Windows NT 4.0 Enterprise Edition
SQL Server 2000
SQL Server 2000 Enterprise and Developer Edition requires the /3GB switch
in the Boot.ini file in order to address up to 3 GB of available memory.
NOTE: Windows NT 4.0 Enterprise Edition does not support the AWE memory
architecture model so AWE support is not available.
back to the top
SQL Server 7.0
SQL Server 7.0 Enterprise Edition requires the /3GB switch in the Boot.ini
file in order to address up to 3 GB of available memory.
back to the top
REFERENCES
For additional information, click the article numbers below to view the
articles in the Microsoft Knowledge Base:
170756 Available Switch Options for Windows NT Boot.ini File
171793 Information on Application Use of 4GT RAM Tuning
268363 Intel Physical Addressing Extensions (PAE) in Windows 2000
292934 Windows 2000 Datacenter Server Does Not Locate Memory Greater Than
16 GB
SQL Server 2000 Books Online; topics: "Managing AWE Memory"; "Running
Multiple Instances and Using Failover Clustering"
back to the top
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
sql
I'm running a non-clustered sql environment, and I was
considering the scenario where I could install multiple
instances of sql server onto one "work-horse" server.
I'm concerned about the 2 Gb memory limit. Is this limit
per instance, or per physical machine?
E.g. one quad-processor server, with 6 Gb of memory
could easily accept 2 sql instances each with a 2Gb
memory limit.
Thanks in Advance
Craig
Hi,
This limitation in Memory / Cpu is instance based. So if you have 2 SQL
server instances you can allocate a maximum of 2 GB RAM for each instance.
FYI,
If your SQL Server edition is Enterprise edition it supports more than 2 GB
RAM for each instance. See books online on "Maximum Capacity specifications"
Thanks
Hari
MCDBA
Thanks
Hari
MCDBA
"Craig Irvine" <anonymous@.discussions.microsoft.com> wrote in message
news:cd6601c43940$2592e2d0$a601280a@.phx.gbl...
> Hi Everyone,
> I'm running a non-clustered sql environment, and I was
> considering the scenario where I could install multiple
> instances of sql server onto one "work-horse" server.
> I'm concerned about the 2 Gb memory limit. Is this limit
> per instance, or per physical machine?
> E.g. one quad-processor server, with 6 Gb of memory
> could easily accept 2 sql instances each with a 2Gb
> memory limit.
> Thanks in Advance
> Craig
>
|||Hi Craig,
The 2GB Memory limitation is per instance and the SQL Server can be
configured to use more memory than 2GB. Please refer to the following
article
http://support.microsoft.com/default...&Product=sql2k
Excerpt from the KB Article
HOW TO: Configure memory for more than 2 GB in SQL Server
View products that this article applies to.
This article was previously published under Q274750
IN THIS TASK
SUMMARY
Support for Operating System Versions
Microsoft Windows 2000 Server
Microsoft SQL Server 2000
Microsoft SQL Server 7.0
Microsoft Windows 2000 Advanced Server or Microsoft Windows 2000 Datacenter
or Windows Server 2003
Microsoft SQL Server 2000
Microsoft SQL Server 7.0
Microsoft Windows NT 4.0 Enterprise Edition
REFERENCES
SUMMARY
This article describes how to configure SQL Server to use more than 2 GB of
physical memory.
Microsoft SQL Server 7.0 and Microsoft SQL Server 2000 dynamically acquire
and free memory as needed. When you run multiple instances of SQL Server on
a computer, each instance dynamically acquires and frees memory to adjust
for changes in the workload of the instance.
SQL Server 2000 Enterprise Edition introduces support for the use of
Microsoft Windows 2000 Address Windowing Extensions (AWE) to address
approximately 8 GB of memory for instances that run on Microsoft Windows
2000 Advanced Server, and approximately 32 GB for instances that run on
Microsoft Windows 2000 Datacenter. With AWE, SQL Server can reserve memory
that is not in use for other applications and the operating system. Each
instance that uses this memory; however, must statically allocate the
memory it needs. SQL Server can only use this AWE allocated memory for the
data cache and not for executables, drivers, DLLs, and so forth. For
additional information, click the article number below to view the article
in the Microsoft Knowledge
Base:
283037 Large Memory Support Is Available in Windows 2000
The extended memory size option is available only for Microsoft SQL Server
7.0, Enterprise Edition on the operating system and hardware that supports
the Enterprise Memory Architecture (EMA) feature. For more information
about how to configure your system to enable the EMA feature on a
particular system configuration, refer to your Microsoft Windows NT
documentation.
Some system vendors may provide products for Microsoft Windows NT, version
4.0 or later, so that SQL Server 7.0, Enterprise Edition can use the
extended memory size option. On Intel platforms, SQL Server 7.0 can use a
feature known as PSE36. On Alpha platforms, the feature that allows use of
the extended memory option is Very Large Memory (VLM). For more information
about the availability, installation, and configuration of these products,
contact your system vendor.
Note: To use Address Windowing Extensions (AWE) memory, you must run the
SQL Server 2000 database engine under a Windows account that has been
assigned the Windows lock pages in memory administrative credentials.
back to the top
Support for Operating System Versions
Windows 2000 Server
SQL Server 2000
Normally, both the SQL Server 2000 Enterprise Edition and SQL Server 2000
Developer Edition can use up to 2 GB of physical memory. With the use of
the AWE enable option, SQL Server can use up to 4 GB of physical memory.
NOTE: You cannot allocate more than 4 GB of physical memory to an
application on Windows 2000 Server because Physical Address Extension (PAE)
is not available on Microsoft Windows 2000 Server. Also, you cannot use the
3 GB switch in the Boot.ini file with Windows 2000 Server; however, you can
use the 3 GB switch in the Boot.ini file with Microsoft Windows 2000
Advanced Server or Microsoft Windows Datacenter versions. For additional
information, click the article number below to view the article in the
Microsoft Knowledge Base:
291988 A Description of the 4 GB RAM Tuning Feature and the Physical
Address Extension Switch
back to the top
SQL Server 7.0
SQL Server 7.0 versions can use up to 2 GB of physical memory.
NOTE: The extended memory option in SQL Server 7.0 is not available on
Windows 2000.
Windows 2000 Advanced Server or Windows 2000 Datacenter or Windows Server
2003
The maximum amount of physical memory addressable by a 32-bit addressing
mode is 4 GB. All processors based on the IA-32 architecture that begin
with the Intel Pentium Pro, support a new 36-bit physical addressing mode
known as Physical Address Extension (PAE). PAE allows up to 8 GB of
physical memory on Windows 2000 Advanced Server and up to 32 GB of physical
memory on Windows 2000 Datacenter Server. This is because the tested memory
limit on Windows 2000 Datacenter Server is 32 GB. The PAE mode kernel
requires an Intel architecture processor, Pentium Pro, or later and either
Windows 2000 Advanced Server or Windows 2000 Datacenter. For additional
information, click the article number below to view the article in the
Microsoft
Knowledge Base:
268230 Scaling Out Versus Scaling Up with Intel Physical Addressing
Extensions (PAE)
Note The maximum amount of memory that can be supported on Windows Server
2003 is 4 GB. However, Windows Server 2003 Enterprise Edition supports 32
GB of physical RAM. Windows Server 2003 Datacenter Edition supports 64 GB
of physical RAM by using the Physical Address Extensions (PAE) feature. You
can use the 3 GB switch that is in the Boot.ini file with Microsoft Windows
Server 2003, Microsoft Windows Server 2003 Enterprise Edition, or with
Microsoft Windows Server 2003 Datacenter Edition.
SQL Server 2000
Both SQL Server 2000 Enterprise and SQL Server 2000 Developer Editions can
use the following options:
Use of the /PAE switch in the Boot.ini and the AWE enable option in SQL
Server allows SQL Server 2000 to utilize more than 4 GB memory. Without the
/PAE switch SQL Server can only utilize up to 4 GB of memory.
NOTE: To allow AWE to use the memory range above 16 GB on Windows 2000 Data
Center, make sure that the /3GB switch is not in the Boot.ini file. If the
/3GB switch is in the Boot.ini file, Windows 2000 may not be able to
address any memory above 16 GB correctly.
When you allocate SQL Server AWE memory on a 32 GB system, Windows 2000 may
require at least 1 GB memory to manage AWE.
back to the top
Example
The following example shows how to enable AWE and configure a limit of 6 GB
for the max server memory option: sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
-or-
-or-Use of the /3GB switch in the Boot.ini file allows SQL Server 2000 to
use up to 3 GB of available memory.
back to the top
SQL Server 7.0
SQL Server 7.0 Enterprise Edition requires the /3GB switch in the Boot.ini
in order to address up to 3 GB of available memory.
NOTE: The extended memory option in SQL Server 7.0 is not available on
Windows 2000 Advanced Server or Windows Datacenter.
Microsoft Windows NT 4.0 Enterprise Edition
SQL Server 2000
SQL Server 2000 Enterprise and Developer Edition requires the /3GB switch
in the Boot.ini file in order to address up to 3 GB of available memory.
NOTE: Windows NT 4.0 Enterprise Edition does not support the AWE memory
architecture model so AWE support is not available.
back to the top
SQL Server 7.0
SQL Server 7.0 Enterprise Edition requires the /3GB switch in the Boot.ini
file in order to address up to 3 GB of available memory.
back to the top
REFERENCES
For additional information, click the article numbers below to view the
articles in the Microsoft Knowledge Base:
170756 Available Switch Options for Windows NT Boot.ini File
171793 Information on Application Use of 4GT RAM Tuning
268363 Intel Physical Addressing Extensions (PAE) in Windows 2000
292934 Windows 2000 Datacenter Server Does Not Locate Memory Greater Than
16 GB
SQL Server 2000 Books Online; topics: "Managing AWE Memory"; "Running
Multiple Instances and Using Failover Clustering"
back to the top
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
sql
multiple instances of sql - 2 Gb memory limitation?
Hi Everyone,
I'm running a non-clustered sql environment, and I was
considering the scenario where I could install multiple
instances of sql server onto one "work-horse" server.
I'm concerned about the 2 Gb memory limit. Is this limit
per instance, or per physical machine?
E.g. one quad-processor server, with 6 Gb of memory
could easily accept 2 sql instances each with a 2Gb
memory limit.
Thanks in Advance
CraigHi,
This limitation in Memory / Cpu is instance based. So if you have 2 SQL
server instances you can allocate a maximum of 2 GB RAM for each instance.
FYI,
If your SQL Server edition is Enterprise edition it supports more than 2 GB
RAM for each instance. See books online on "Maximum Capacity specifications"
Thanks
Hari
MCDBA
Thanks
Hari
MCDBA
"Craig Irvine" <anonymous@.discussions.microsoft.com> wrote in message
news:cd6601c43940$2592e2d0$a601280a@.phx.gbl...
> Hi Everyone,
> I'm running a non-clustered sql environment, and I was
> considering the scenario where I could install multiple
> instances of sql server onto one "work-horse" server.
> I'm concerned about the 2 Gb memory limit. Is this limit
> per instance, or per physical machine?
> E.g. one quad-processor server, with 6 Gb of memory
> could easily accept 2 sql instances each with a 2Gb
> memory limit.
> Thanks in Advance
> Craig
>|||Hi Craig,
The 2GB Memory limitation is per instance and the SQL Server can be
configured to use more memory than 2GB. Please refer to the following
article
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&Product=sql2k
Excerpt from the KB Article
HOW TO: Configure memory for more than 2 GB in SQL Server
View products that this article applies to.
This article was previously published under Q274750
IN THIS TASK
SUMMARY
Support for Operating System Versions
Microsoft Windows 2000 Server
Microsoft SQL Server 2000
Microsoft SQL Server 7.0
Microsoft Windows 2000 Advanced Server or Microsoft Windows 2000 Datacenter
or Windows Server 2003
Microsoft SQL Server 2000
Microsoft SQL Server 7.0
Microsoft Windows NT 4.0 Enterprise Edition
REFERENCES
SUMMARY
This article describes how to configure SQL Server to use more than 2 GB of
physical memory.
Microsoft SQL Server 7.0 and Microsoft SQL Server 2000 dynamically acquire
and free memory as needed. When you run multiple instances of SQL Server on
a computer, each instance dynamically acquires and frees memory to adjust
for changes in the workload of the instance.
SQL Server 2000 Enterprise Edition introduces support for the use of
Microsoft Windows 2000 Address Windowing Extensions (AWE) to address
approximately 8 GB of memory for instances that run on Microsoft Windows
2000 Advanced Server, and approximately 32 GB for instances that run on
Microsoft Windows 2000 Datacenter. With AWE, SQL Server can reserve memory
that is not in use for other applications and the operating system. Each
instance that uses this memory; however, must statically allocate the
memory it needs. SQL Server can only use this AWE allocated memory for the
data cache and not for executables, drivers, DLLs, and so forth. For
additional information, click the article number below to view the article
in the Microsoft Knowledge
Base:
283037 Large Memory Support Is Available in Windows 2000
The extended memory size option is available only for Microsoft SQL Server
7.0, Enterprise Edition on the operating system and hardware that supports
the Enterprise Memory Architecture (EMA) feature. For more information
about how to configure your system to enable the EMA feature on a
particular system configuration, refer to your Microsoft Windows NT
documentation.
Some system vendors may provide products for Microsoft Windows NT, version
4.0 or later, so that SQL Server 7.0, Enterprise Edition can use the
extended memory size option. On Intel platforms, SQL Server 7.0 can use a
feature known as PSE36. On Alpha platforms, the feature that allows use of
the extended memory option is Very Large Memory (VLM). For more information
about the availability, installation, and configuration of these products,
contact your system vendor.
Note: To use Address Windowing Extensions (AWE) memory, you must run the
SQL Server 2000 database engine under a Windows account that has been
assigned the Windows lock pages in memory administrative credentials.
back to the top
Support for Operating System Versions
Windows 2000 Server
SQL Server 2000
Normally, both the SQL Server 2000 Enterprise Edition and SQL Server 2000
Developer Edition can use up to 2 GB of physical memory. With the use of
the AWE enable option, SQL Server can use up to 4 GB of physical memory.
NOTE: You cannot allocate more than 4 GB of physical memory to an
application on Windows 2000 Server because Physical Address Extension (PAE)
is not available on Microsoft Windows 2000 Server. Also, you cannot use the
3 GB switch in the Boot.ini file with Windows 2000 Server; however, you can
use the 3 GB switch in the Boot.ini file with Microsoft Windows 2000
Advanced Server or Microsoft Windows Datacenter versions. For additional
information, click the article number below to view the article in the
Microsoft Knowledge Base:
291988 A Description of the 4 GB RAM Tuning Feature and the Physical
Address Extension Switch
back to the top
SQL Server 7.0
SQL Server 7.0 versions can use up to 2 GB of physical memory.
NOTE: The extended memory option in SQL Server 7.0 is not available on
Windows 2000.
Windows 2000 Advanced Server or Windows 2000 Datacenter or Windows Server
2003
The maximum amount of physical memory addressable by a 32-bit addressing
mode is 4 GB. All processors based on the IA-32 architecture that begin
with the Intel Pentium Pro, support a new 36-bit physical addressing mode
known as Physical Address Extension (PAE). PAE allows up to 8 GB of
physical memory on Windows 2000 Advanced Server and up to 32 GB of physical
memory on Windows 2000 Datacenter Server. This is because the tested memory
limit on Windows 2000 Datacenter Server is 32 GB. The PAE mode kernel
requires an Intel architecture processor, Pentium Pro, or later and either
Windows 2000 Advanced Server or Windows 2000 Datacenter. For additional
information, click the article number below to view the article in the
Microsoft
Knowledge Base:
268230 Scaling Out Versus Scaling Up with Intel Physical Addressing
Extensions (PAE)
Note The maximum amount of memory that can be supported on Windows Server
2003 is 4 GB. However, Windows Server 2003 Enterprise Edition supports 32
GB of physical RAM. Windows Server 2003 Datacenter Edition supports 64 GB
of physical RAM by using the Physical Address Extensions (PAE) feature. You
can use the 3 GB switch that is in the Boot.ini file with Microsoft Windows
Server 2003, Microsoft Windows Server 2003 Enterprise Edition, or with
Microsoft Windows Server 2003 Datacenter Edition.
SQL Server 2000
Both SQL Server 2000 Enterprise and SQL Server 2000 Developer Editions can
use the following options:
Use of the /PAE switch in the Boot.ini and the AWE enable option in SQL
Server allows SQL Server 2000 to utilize more than 4 GB memory. Without the
/PAE switch SQL Server can only utilize up to 4 GB of memory.
NOTE: To allow AWE to use the memory range above 16 GB on Windows 2000 Data
Center, make sure that the /3GB switch is not in the Boot.ini file. If the
/3GB switch is in the Boot.ini file, Windows 2000 may not be able to
address any memory above 16 GB correctly.
When you allocate SQL Server AWE memory on a 32 GB system, Windows 2000 may
require at least 1 GB memory to manage AWE.
back to the top
Example
The following example shows how to enable AWE and configure a limit of 6 GB
for the max server memory option: sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
-or-
-or-Use of the /3GB switch in the Boot.ini file allows SQL Server 2000 to
use up to 3 GB of available memory.
back to the top
SQL Server 7.0
SQL Server 7.0 Enterprise Edition requires the /3GB switch in the Boot.ini
in order to address up to 3 GB of available memory.
NOTE: The extended memory option in SQL Server 7.0 is not available on
Windows 2000 Advanced Server or Windows Datacenter.
Microsoft Windows NT 4.0 Enterprise Edition
SQL Server 2000
SQL Server 2000 Enterprise and Developer Edition requires the /3GB switch
in the Boot.ini file in order to address up to 3 GB of available memory.
NOTE: Windows NT 4.0 Enterprise Edition does not support the AWE memory
architecture model so AWE support is not available.
back to the top
SQL Server 7.0
SQL Server 7.0 Enterprise Edition requires the /3GB switch in the Boot.ini
file in order to address up to 3 GB of available memory.
back to the top
REFERENCES
For additional information, click the article numbers below to view the
articles in the Microsoft Knowledge Base:
170756 Available Switch Options for Windows NT Boot.ini File
171793 Information on Application Use of 4GT RAM Tuning
268363 Intel Physical Addressing Extensions (PAE) in Windows 2000
292934 Windows 2000 Datacenter Server Does Not Locate Memory Greater Than
16 GB
SQL Server 2000 Books Online; topics: "Managing AWE Memory"; "Running
Multiple Instances and Using Failover Clustering"
back to the top
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
I'm running a non-clustered sql environment, and I was
considering the scenario where I could install multiple
instances of sql server onto one "work-horse" server.
I'm concerned about the 2 Gb memory limit. Is this limit
per instance, or per physical machine?
E.g. one quad-processor server, with 6 Gb of memory
could easily accept 2 sql instances each with a 2Gb
memory limit.
Thanks in Advance
CraigHi,
This limitation in Memory / Cpu is instance based. So if you have 2 SQL
server instances you can allocate a maximum of 2 GB RAM for each instance.
FYI,
If your SQL Server edition is Enterprise edition it supports more than 2 GB
RAM for each instance. See books online on "Maximum Capacity specifications"
Thanks
Hari
MCDBA
Thanks
Hari
MCDBA
"Craig Irvine" <anonymous@.discussions.microsoft.com> wrote in message
news:cd6601c43940$2592e2d0$a601280a@.phx.gbl...
> Hi Everyone,
> I'm running a non-clustered sql environment, and I was
> considering the scenario where I could install multiple
> instances of sql server onto one "work-horse" server.
> I'm concerned about the 2 Gb memory limit. Is this limit
> per instance, or per physical machine?
> E.g. one quad-processor server, with 6 Gb of memory
> could easily accept 2 sql instances each with a 2Gb
> memory limit.
> Thanks in Advance
> Craig
>|||Hi Craig,
The 2GB Memory limitation is per instance and the SQL Server can be
configured to use more memory than 2GB. Please refer to the following
article
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&Product=sql2k
Excerpt from the KB Article
HOW TO: Configure memory for more than 2 GB in SQL Server
View products that this article applies to.
This article was previously published under Q274750
IN THIS TASK
SUMMARY
Support for Operating System Versions
Microsoft Windows 2000 Server
Microsoft SQL Server 2000
Microsoft SQL Server 7.0
Microsoft Windows 2000 Advanced Server or Microsoft Windows 2000 Datacenter
or Windows Server 2003
Microsoft SQL Server 2000
Microsoft SQL Server 7.0
Microsoft Windows NT 4.0 Enterprise Edition
REFERENCES
SUMMARY
This article describes how to configure SQL Server to use more than 2 GB of
physical memory.
Microsoft SQL Server 7.0 and Microsoft SQL Server 2000 dynamically acquire
and free memory as needed. When you run multiple instances of SQL Server on
a computer, each instance dynamically acquires and frees memory to adjust
for changes in the workload of the instance.
SQL Server 2000 Enterprise Edition introduces support for the use of
Microsoft Windows 2000 Address Windowing Extensions (AWE) to address
approximately 8 GB of memory for instances that run on Microsoft Windows
2000 Advanced Server, and approximately 32 GB for instances that run on
Microsoft Windows 2000 Datacenter. With AWE, SQL Server can reserve memory
that is not in use for other applications and the operating system. Each
instance that uses this memory; however, must statically allocate the
memory it needs. SQL Server can only use this AWE allocated memory for the
data cache and not for executables, drivers, DLLs, and so forth. For
additional information, click the article number below to view the article
in the Microsoft Knowledge
Base:
283037 Large Memory Support Is Available in Windows 2000
The extended memory size option is available only for Microsoft SQL Server
7.0, Enterprise Edition on the operating system and hardware that supports
the Enterprise Memory Architecture (EMA) feature. For more information
about how to configure your system to enable the EMA feature on a
particular system configuration, refer to your Microsoft Windows NT
documentation.
Some system vendors may provide products for Microsoft Windows NT, version
4.0 or later, so that SQL Server 7.0, Enterprise Edition can use the
extended memory size option. On Intel platforms, SQL Server 7.0 can use a
feature known as PSE36. On Alpha platforms, the feature that allows use of
the extended memory option is Very Large Memory (VLM). For more information
about the availability, installation, and configuration of these products,
contact your system vendor.
Note: To use Address Windowing Extensions (AWE) memory, you must run the
SQL Server 2000 database engine under a Windows account that has been
assigned the Windows lock pages in memory administrative credentials.
back to the top
Support for Operating System Versions
Windows 2000 Server
SQL Server 2000
Normally, both the SQL Server 2000 Enterprise Edition and SQL Server 2000
Developer Edition can use up to 2 GB of physical memory. With the use of
the AWE enable option, SQL Server can use up to 4 GB of physical memory.
NOTE: You cannot allocate more than 4 GB of physical memory to an
application on Windows 2000 Server because Physical Address Extension (PAE)
is not available on Microsoft Windows 2000 Server. Also, you cannot use the
3 GB switch in the Boot.ini file with Windows 2000 Server; however, you can
use the 3 GB switch in the Boot.ini file with Microsoft Windows 2000
Advanced Server or Microsoft Windows Datacenter versions. For additional
information, click the article number below to view the article in the
Microsoft Knowledge Base:
291988 A Description of the 4 GB RAM Tuning Feature and the Physical
Address Extension Switch
back to the top
SQL Server 7.0
SQL Server 7.0 versions can use up to 2 GB of physical memory.
NOTE: The extended memory option in SQL Server 7.0 is not available on
Windows 2000.
Windows 2000 Advanced Server or Windows 2000 Datacenter or Windows Server
2003
The maximum amount of physical memory addressable by a 32-bit addressing
mode is 4 GB. All processors based on the IA-32 architecture that begin
with the Intel Pentium Pro, support a new 36-bit physical addressing mode
known as Physical Address Extension (PAE). PAE allows up to 8 GB of
physical memory on Windows 2000 Advanced Server and up to 32 GB of physical
memory on Windows 2000 Datacenter Server. This is because the tested memory
limit on Windows 2000 Datacenter Server is 32 GB. The PAE mode kernel
requires an Intel architecture processor, Pentium Pro, or later and either
Windows 2000 Advanced Server or Windows 2000 Datacenter. For additional
information, click the article number below to view the article in the
Microsoft
Knowledge Base:
268230 Scaling Out Versus Scaling Up with Intel Physical Addressing
Extensions (PAE)
Note The maximum amount of memory that can be supported on Windows Server
2003 is 4 GB. However, Windows Server 2003 Enterprise Edition supports 32
GB of physical RAM. Windows Server 2003 Datacenter Edition supports 64 GB
of physical RAM by using the Physical Address Extensions (PAE) feature. You
can use the 3 GB switch that is in the Boot.ini file with Microsoft Windows
Server 2003, Microsoft Windows Server 2003 Enterprise Edition, or with
Microsoft Windows Server 2003 Datacenter Edition.
SQL Server 2000
Both SQL Server 2000 Enterprise and SQL Server 2000 Developer Editions can
use the following options:
Use of the /PAE switch in the Boot.ini and the AWE enable option in SQL
Server allows SQL Server 2000 to utilize more than 4 GB memory. Without the
/PAE switch SQL Server can only utilize up to 4 GB of memory.
NOTE: To allow AWE to use the memory range above 16 GB on Windows 2000 Data
Center, make sure that the /3GB switch is not in the Boot.ini file. If the
/3GB switch is in the Boot.ini file, Windows 2000 may not be able to
address any memory above 16 GB correctly.
When you allocate SQL Server AWE memory on a 32 GB system, Windows 2000 may
require at least 1 GB memory to manage AWE.
back to the top
Example
The following example shows how to enable AWE and configure a limit of 6 GB
for the max server memory option: sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
-or-
-or-Use of the /3GB switch in the Boot.ini file allows SQL Server 2000 to
use up to 3 GB of available memory.
back to the top
SQL Server 7.0
SQL Server 7.0 Enterprise Edition requires the /3GB switch in the Boot.ini
in order to address up to 3 GB of available memory.
NOTE: The extended memory option in SQL Server 7.0 is not available on
Windows 2000 Advanced Server or Windows Datacenter.
Microsoft Windows NT 4.0 Enterprise Edition
SQL Server 2000
SQL Server 2000 Enterprise and Developer Edition requires the /3GB switch
in the Boot.ini file in order to address up to 3 GB of available memory.
NOTE: Windows NT 4.0 Enterprise Edition does not support the AWE memory
architecture model so AWE support is not available.
back to the top
SQL Server 7.0
SQL Server 7.0 Enterprise Edition requires the /3GB switch in the Boot.ini
file in order to address up to 3 GB of available memory.
back to the top
REFERENCES
For additional information, click the article numbers below to view the
articles in the Microsoft Knowledge Base:
170756 Available Switch Options for Windows NT Boot.ini File
171793 Information on Application Use of 4GT RAM Tuning
268363 Intel Physical Addressing Extensions (PAE) in Windows 2000
292934 Windows 2000 Datacenter Server Does Not Locate Memory Greater Than
16 GB
SQL Server 2000 Books Online; topics: "Managing AWE Memory"; "Running
Multiple Instances and Using Failover Clustering"
back to the top
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
multiple instances + memory
**** Post for FREE via your newsreader at post.mcse.ms ****
We're going to set up a Win2003 cluster on two dual cpu with 8 GB of ram
systems. I'd like to install multiple instances of SQL server so i can
switch instances on the computers.
When i use 3 instances of sql server can they each can use 2 GB' I believe
they can but i like to check this with you guys before buying 8 GB instead
of 4.
Thx,
Kasper de Jonge
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
*** mcse.ms - The #1 Usenet Newsgroup Service on The Planet! ***
http://www.mcse.ms
Unlimited Download - 19 Seperate Servers - 90,000 groups - Uncensored
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=Hi,
Yes, each instance are independent of each other. So you can define and fix
2 GB RAM for each instance.
Thanks
Hari
MCDBA
"Kasper de Jonge" <kdejonge.nospam@.elkerliek.nl> wrote in message
news:40b6f97f@.post.mcse.ms...
> **** Post for FREE via your newsreader at post.mcse.ms ****
> We're going to set up a Win2003 cluster on two dual cpu with 8 GB of ram
> systems. I'd like to install multiple instances of SQL server so i can
> switch instances on the computers.
> When i use 3 instances of sql server can they each can use 2 GB' I
believe
> they can but i like to check this with you guys before buying 8 GB instead
> of 4.
> Thx,
> Kasper de Jonge
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> *** mcse.ms - The #1 Usenet Newsgroup Service on The Planet! ***
> http://www.mcse.ms
> Unlimited Download - 19 Seperate Servers - 90,000 groups - Uncensored
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
We're going to set up a Win2003 cluster on two dual cpu with 8 GB of ram
systems. I'd like to install multiple instances of SQL server so i can
switch instances on the computers.
When i use 3 instances of sql server can they each can use 2 GB' I believe
they can but i like to check this with you guys before buying 8 GB instead
of 4.
Thx,
Kasper de Jonge
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
*** mcse.ms - The #1 Usenet Newsgroup Service on The Planet! ***
http://www.mcse.ms
Unlimited Download - 19 Seperate Servers - 90,000 groups - Uncensored
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=Hi,
Yes, each instance are independent of each other. So you can define and fix
2 GB RAM for each instance.
Thanks
Hari
MCDBA
"Kasper de Jonge" <kdejonge.nospam@.elkerliek.nl> wrote in message
news:40b6f97f@.post.mcse.ms...
> **** Post for FREE via your newsreader at post.mcse.ms ****
> We're going to set up a Win2003 cluster on two dual cpu with 8 GB of ram
> systems. I'd like to install multiple instances of SQL server so i can
> switch instances on the computers.
> When i use 3 instances of sql server can they each can use 2 GB' I
believe
> they can but i like to check this with you guys before buying 8 GB instead
> of 4.
> Thx,
> Kasper de Jonge
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> *** mcse.ms - The #1 Usenet Newsgroup Service on The Planet! ***
> http://www.mcse.ms
> Unlimited Download - 19 Seperate Servers - 90,000 groups - Uncensored
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
multiple instances + memory
**** Post for FREE via your newsreader at post.usenet.com ****
We're going to set up a Win2003 cluster on two dual cpu with 8 GB of ram
systems. I'd like to install multiple instances of SQL server so i can
switch instances on the computers.
When i use 3 instances of sql server can they each can use 2 GB? I believe
they can but i like to check this with you guys before buying 8 GB instead
of 4.
Thx,
Kasper de Jonge
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
*** Usenet.com - The #1 Usenet Newsgroup Service on The Planet! ***
http://www.usenet.com
Unlimited Download - 19 Seperate Servers - 90,000 groups - Uncensored
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Hi,
Yes, each instance are independent of each other. So you can define and fix
2 GB RAM for each instance.
Thanks
Hari
MCDBA
"Kasper de Jonge" <kdejonge.nospam@.elkerliek.nl> wrote in message
news:40b6f97f@.post.usenet.com...
> **** Post for FREE via your newsreader at post.usenet.com ****
> We're going to set up a Win2003 cluster on two dual cpu with 8 GB of ram
> systems. I'd like to install multiple instances of SQL server so i can
> switch instances on the computers.
> When i use 3 instances of sql server can they each can use 2 GB? I
believe
> they can but i like to check this with you guys before buying 8 GB instead
> of 4.
> Thx,
> Kasper de Jonge
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> *** Usenet.com - The #1 Usenet Newsgroup Service on The Planet! ***
> http://www.usenet.com
> Unlimited Download - 19 Seperate Servers - 90,000 groups - Uncensored
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
We're going to set up a Win2003 cluster on two dual cpu with 8 GB of ram
systems. I'd like to install multiple instances of SQL server so i can
switch instances on the computers.
When i use 3 instances of sql server can they each can use 2 GB? I believe
they can but i like to check this with you guys before buying 8 GB instead
of 4.
Thx,
Kasper de Jonge
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
*** Usenet.com - The #1 Usenet Newsgroup Service on The Planet! ***
http://www.usenet.com
Unlimited Download - 19 Seperate Servers - 90,000 groups - Uncensored
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Hi,
Yes, each instance are independent of each other. So you can define and fix
2 GB RAM for each instance.
Thanks
Hari
MCDBA
"Kasper de Jonge" <kdejonge.nospam@.elkerliek.nl> wrote in message
news:40b6f97f@.post.usenet.com...
> **** Post for FREE via your newsreader at post.usenet.com ****
> We're going to set up a Win2003 cluster on two dual cpu with 8 GB of ram
> systems. I'd like to install multiple instances of SQL server so i can
> switch instances on the computers.
> When i use 3 instances of sql server can they each can use 2 GB? I
believe
> they can but i like to check this with you guys before buying 8 GB instead
> of 4.
> Thx,
> Kasper de Jonge
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> *** Usenet.com - The #1 Usenet Newsgroup Service on The Planet! ***
> http://www.usenet.com
> Unlimited Download - 19 Seperate Servers - 90,000 groups - Uncensored
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
multiple instances + memory
**** Post for FREE via your newsreader at post.usenet.com ****
We're going to set up a Win2003 cluster on two dual cpu with 8 GB of ram
systems. I'd like to install multiple instances of SQL server so i can
switch instances on the computers.
When i use 3 instances of sql server can they each can use 2 GB' I believe
they can but i like to check this with you guys before buying 8 GB instead
of 4.
Thx,
Kasper de Jonge
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= *** Usenet.com - The #1 Usenet Newsgroup Service on The Planet! ***
http://www.usenet.com
Unlimited Download - 19 Seperate Servers - 90,000 groups - Uncensored
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=Hi,
Yes, each instance are independent of each other. So you can define and fix
2 GB RAM for each instance.
Thanks
Hari
MCDBA
"Kasper de Jonge" <kdejonge.nospam@.elkerliek.nl> wrote in message
news:40b6f97f@.post.usenet.com...
> **** Post for FREE via your newsreader at post.usenet.com ****
> We're going to set up a Win2003 cluster on two dual cpu with 8 GB of ram
> systems. I'd like to install multiple instances of SQL server so i can
> switch instances on the computers.
> When i use 3 instances of sql server can they each can use 2 GB' I
believe
> they can but i like to check this with you guys before buying 8 GB instead
> of 4.
> Thx,
> Kasper de Jonge
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=> *** Usenet.com - The #1 Usenet Newsgroup Service on The Planet! ***
> http://www.usenet.com
> Unlimited Download - 19 Seperate Servers - 90,000 groups - Uncensored
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
We're going to set up a Win2003 cluster on two dual cpu with 8 GB of ram
systems. I'd like to install multiple instances of SQL server so i can
switch instances on the computers.
When i use 3 instances of sql server can they each can use 2 GB' I believe
they can but i like to check this with you guys before buying 8 GB instead
of 4.
Thx,
Kasper de Jonge
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= *** Usenet.com - The #1 Usenet Newsgroup Service on The Planet! ***
http://www.usenet.com
Unlimited Download - 19 Seperate Servers - 90,000 groups - Uncensored
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=Hi,
Yes, each instance are independent of each other. So you can define and fix
2 GB RAM for each instance.
Thanks
Hari
MCDBA
"Kasper de Jonge" <kdejonge.nospam@.elkerliek.nl> wrote in message
news:40b6f97f@.post.usenet.com...
> **** Post for FREE via your newsreader at post.usenet.com ****
> We're going to set up a Win2003 cluster on two dual cpu with 8 GB of ram
> systems. I'd like to install multiple instances of SQL server so i can
> switch instances on the computers.
> When i use 3 instances of sql server can they each can use 2 GB' I
believe
> they can but i like to check this with you guys before buying 8 GB instead
> of 4.
> Thx,
> Kasper de Jonge
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=> *** Usenet.com - The #1 Usenet Newsgroup Service on The Planet! ***
> http://www.usenet.com
> Unlimited Download - 19 Seperate Servers - 90,000 groups - Uncensored
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Monday, March 26, 2012
Multiple Instance Memory Utilization
I have a Dell server with 4GB of memory and 4 CPUs with 1.6G each, hosting
one major application database. SQL Server 2000 Standard Edition was
installed on the server, OS is Windows 2000 Server. Currently with single
instance installed, I checked the memory usage using task manager, the wholes
system can only use up to less then 2 GB of memory. The peak is less than 2
GB. The system neven utilizing more than 2 GM of memory. I am in the process
of doing server consolidation and planning to move another major application
database to this dell server. I want to utilize 4 G of memory after I
consolidate the other SQL server to the Dell Server. If I just move the
database to this dell server without creating a new instance, the most memory
we can utilize is 3GB with 3 GB switch set in boot.ini. If we create a new
instance, does that mean we can utilize the other 2 GB of Memory on the
server? Security is not a major concern when using single instance. What are
the Pros and Cons?
Thank you very much for your help.
You need Enterprise edition to use more than 2GB. Windows 2000 server does
not use the /3GB switch other than in a test scenario. Yes you can use two
instances and each can use 2GB but you have to be careful as now you can
lead to a situation where there is little left for the OS. If you are
consolidating then you should look at using Enterprise edition and Win2000
ADV Server (or Win2003) so you can use all 3GB for Sql Server and have a GB
for the OS and any other apps.
Andrew J. Kelly SQL MVP
"royHe" <royHe@.discussions.microsoft.com> wrote in message
news:8B395A5C-26F6-4E71-95B2-D9CE53E62100@.microsoft.com...
>I have a Dell server with 4GB of memory and 4 CPUs with 1.6G each, hosting
> one major application database. SQL Server 2000 Standard Edition was
> installed on the server, OS is Windows 2000 Server. Currently with single
> instance installed, I checked the memory usage using task manager, the
> wholes
> system can only use up to less then 2 GB of memory. The peak is less than
> 2
> GB. The system neven utilizing more than 2 GM of memory. I am in the
> process
> of doing server consolidation and planning to move another major
> application
> database to this dell server. I want to utilize 4 G of memory after I
> consolidate the other SQL server to the Dell Server. If I just move the
> database to this dell server without creating a new instance, the most
> memory
> we can utilize is 3GB with 3 GB switch set in boot.ini. If we create a new
> instance, does that mean we can utilize the other 2 GB of Memory on the
> server? Security is not a major concern when using single instance. What
> are
> the Pros and Cons?
> Thank you very much for your help.
>
|||Thank you very much.
This is a dedicated SQL server. I find out in my situation the OS use very
little memory. Probably If I reserve 256M to 300M for the OS is enough.
Currently the peak for the OS Memory usage is around 250M.
"Andrew J. Kelly" wrote:
> You need Enterprise edition to use more than 2GB. Windows 2000 server does
> not use the /3GB switch other than in a test scenario. Yes you can use two
> instances and each can use 2GB but you have to be careful as now you can
> lead to a situation where there is little left for the OS. If you are
> consolidating then you should look at using Enterprise edition and Win2000
> ADV Server (or Win2003) so you can use all 3GB for Sql Server and have a GB
> for the OS and any other apps.
> --
> Andrew J. Kelly SQL MVP
>
> "royHe" <royHe@.discussions.microsoft.com> wrote in message
> news:8B395A5C-26F6-4E71-95B2-D9CE53E62100@.microsoft.com...
>
>
one major application database. SQL Server 2000 Standard Edition was
installed on the server, OS is Windows 2000 Server. Currently with single
instance installed, I checked the memory usage using task manager, the wholes
system can only use up to less then 2 GB of memory. The peak is less than 2
GB. The system neven utilizing more than 2 GM of memory. I am in the process
of doing server consolidation and planning to move another major application
database to this dell server. I want to utilize 4 G of memory after I
consolidate the other SQL server to the Dell Server. If I just move the
database to this dell server without creating a new instance, the most memory
we can utilize is 3GB with 3 GB switch set in boot.ini. If we create a new
instance, does that mean we can utilize the other 2 GB of Memory on the
server? Security is not a major concern when using single instance. What are
the Pros and Cons?
Thank you very much for your help.
You need Enterprise edition to use more than 2GB. Windows 2000 server does
not use the /3GB switch other than in a test scenario. Yes you can use two
instances and each can use 2GB but you have to be careful as now you can
lead to a situation where there is little left for the OS. If you are
consolidating then you should look at using Enterprise edition and Win2000
ADV Server (or Win2003) so you can use all 3GB for Sql Server and have a GB
for the OS and any other apps.
Andrew J. Kelly SQL MVP
"royHe" <royHe@.discussions.microsoft.com> wrote in message
news:8B395A5C-26F6-4E71-95B2-D9CE53E62100@.microsoft.com...
>I have a Dell server with 4GB of memory and 4 CPUs with 1.6G each, hosting
> one major application database. SQL Server 2000 Standard Edition was
> installed on the server, OS is Windows 2000 Server. Currently with single
> instance installed, I checked the memory usage using task manager, the
> wholes
> system can only use up to less then 2 GB of memory. The peak is less than
> 2
> GB. The system neven utilizing more than 2 GM of memory. I am in the
> process
> of doing server consolidation and planning to move another major
> application
> database to this dell server. I want to utilize 4 G of memory after I
> consolidate the other SQL server to the Dell Server. If I just move the
> database to this dell server without creating a new instance, the most
> memory
> we can utilize is 3GB with 3 GB switch set in boot.ini. If we create a new
> instance, does that mean we can utilize the other 2 GB of Memory on the
> server? Security is not a major concern when using single instance. What
> are
> the Pros and Cons?
> Thank you very much for your help.
>
|||Thank you very much.
This is a dedicated SQL server. I find out in my situation the OS use very
little memory. Probably If I reserve 256M to 300M for the OS is enough.
Currently the peak for the OS Memory usage is around 250M.
"Andrew J. Kelly" wrote:
> You need Enterprise edition to use more than 2GB. Windows 2000 server does
> not use the /3GB switch other than in a test scenario. Yes you can use two
> instances and each can use 2GB but you have to be careful as now you can
> lead to a situation where there is little left for the OS. If you are
> consolidating then you should look at using Enterprise edition and Win2000
> ADV Server (or Win2003) so you can use all 3GB for Sql Server and have a GB
> for the OS and any other apps.
> --
> Andrew J. Kelly SQL MVP
>
> "royHe" <royHe@.discussions.microsoft.com> wrote in message
> news:8B395A5C-26F6-4E71-95B2-D9CE53E62100@.microsoft.com...
>
>
Multiple Instance Memory Utilization
I have a Dell server with 4GB of memory and 4 CPUs with 1.6G each, hosting
one major application database. SQL Server 2000 Standard Edition was
installed on the server, OS is Windows 2000 Server. Currently with single
instance installed, I checked the memory usage using task manager, the wholes
system can only use up to less then 2 GB of memory. The peak is less than 2
GB. The system neven utilizing more than 2 GM of memory. I am in the process
of doing server consolidation and planning to move another major application
database to this dell server. I want to utilize 4 G of memory after I
consolidate the other SQL server to the Dell Server. If I just move the
database to this dell server without creating a new instance, the most memory
we can utilize is 3GB with 3 GB switch set in boot.ini. If we create a new
instance, does that mean we can utilize the other 2 GB of Memory on the
server? Security is not a major concern when using single instance. What are
the Pros and Cons?
Thank you very much for your help.You need Enterprise edition to use more than 2GB. Windows 2000 server does
not use the /3GB switch other than in a test scenario. Yes you can use two
instances and each can use 2GB but you have to be careful as now you can
lead to a situation where there is little left for the OS. If you are
consolidating then you should look at using Enterprise edition and Win2000
ADV Server (or Win2003) so you can use all 3GB for Sql Server and have a GB
for the OS and any other apps.
--
Andrew J. Kelly SQL MVP
"royHe" <royHe@.discussions.microsoft.com> wrote in message
news:8B395A5C-26F6-4E71-95B2-D9CE53E62100@.microsoft.com...
>I have a Dell server with 4GB of memory and 4 CPUs with 1.6G each, hosting
> one major application database. SQL Server 2000 Standard Edition was
> installed on the server, OS is Windows 2000 Server. Currently with single
> instance installed, I checked the memory usage using task manager, the
> wholes
> system can only use up to less then 2 GB of memory. The peak is less than
> 2
> GB. The system neven utilizing more than 2 GM of memory. I am in the
> process
> of doing server consolidation and planning to move another major
> application
> database to this dell server. I want to utilize 4 G of memory after I
> consolidate the other SQL server to the Dell Server. If I just move the
> database to this dell server without creating a new instance, the most
> memory
> we can utilize is 3GB with 3 GB switch set in boot.ini. If we create a new
> instance, does that mean we can utilize the other 2 GB of Memory on the
> server? Security is not a major concern when using single instance. What
> are
> the Pros and Cons?
> Thank you very much for your help.
>|||Thank you very much.
This is a dedicated SQL server. I find out in my situation the OS use very
little memory. Probably If I reserve 256M to 300M for the OS is enough.
Currently the peak for the OS Memory usage is around 250M.
"Andrew J. Kelly" wrote:
> You need Enterprise edition to use more than 2GB. Windows 2000 server does
> not use the /3GB switch other than in a test scenario. Yes you can use two
> instances and each can use 2GB but you have to be careful as now you can
> lead to a situation where there is little left for the OS. If you are
> consolidating then you should look at using Enterprise edition and Win2000
> ADV Server (or Win2003) so you can use all 3GB for Sql Server and have a GB
> for the OS and any other apps.
> --
> Andrew J. Kelly SQL MVP
>
> "royHe" <royHe@.discussions.microsoft.com> wrote in message
> news:8B395A5C-26F6-4E71-95B2-D9CE53E62100@.microsoft.com...
> >I have a Dell server with 4GB of memory and 4 CPUs with 1.6G each, hosting
> > one major application database. SQL Server 2000 Standard Edition was
> > installed on the server, OS is Windows 2000 Server. Currently with single
> > instance installed, I checked the memory usage using task manager, the
> > wholes
> > system can only use up to less then 2 GB of memory. The peak is less than
> > 2
> > GB. The system neven utilizing more than 2 GM of memory. I am in the
> > process
> > of doing server consolidation and planning to move another major
> > application
> > database to this dell server. I want to utilize 4 G of memory after I
> > consolidate the other SQL server to the Dell Server. If I just move the
> > database to this dell server without creating a new instance, the most
> > memory
> > we can utilize is 3GB with 3 GB switch set in boot.ini. If we create a new
> > instance, does that mean we can utilize the other 2 GB of Memory on the
> > server? Security is not a major concern when using single instance. What
> > are
> > the Pros and Cons?
> >
> > Thank you very much for your help.
> >
> >
>
>
one major application database. SQL Server 2000 Standard Edition was
installed on the server, OS is Windows 2000 Server. Currently with single
instance installed, I checked the memory usage using task manager, the wholes
system can only use up to less then 2 GB of memory. The peak is less than 2
GB. The system neven utilizing more than 2 GM of memory. I am in the process
of doing server consolidation and planning to move another major application
database to this dell server. I want to utilize 4 G of memory after I
consolidate the other SQL server to the Dell Server. If I just move the
database to this dell server without creating a new instance, the most memory
we can utilize is 3GB with 3 GB switch set in boot.ini. If we create a new
instance, does that mean we can utilize the other 2 GB of Memory on the
server? Security is not a major concern when using single instance. What are
the Pros and Cons?
Thank you very much for your help.You need Enterprise edition to use more than 2GB. Windows 2000 server does
not use the /3GB switch other than in a test scenario. Yes you can use two
instances and each can use 2GB but you have to be careful as now you can
lead to a situation where there is little left for the OS. If you are
consolidating then you should look at using Enterprise edition and Win2000
ADV Server (or Win2003) so you can use all 3GB for Sql Server and have a GB
for the OS and any other apps.
--
Andrew J. Kelly SQL MVP
"royHe" <royHe@.discussions.microsoft.com> wrote in message
news:8B395A5C-26F6-4E71-95B2-D9CE53E62100@.microsoft.com...
>I have a Dell server with 4GB of memory and 4 CPUs with 1.6G each, hosting
> one major application database. SQL Server 2000 Standard Edition was
> installed on the server, OS is Windows 2000 Server. Currently with single
> instance installed, I checked the memory usage using task manager, the
> wholes
> system can only use up to less then 2 GB of memory. The peak is less than
> 2
> GB. The system neven utilizing more than 2 GM of memory. I am in the
> process
> of doing server consolidation and planning to move another major
> application
> database to this dell server. I want to utilize 4 G of memory after I
> consolidate the other SQL server to the Dell Server. If I just move the
> database to this dell server without creating a new instance, the most
> memory
> we can utilize is 3GB with 3 GB switch set in boot.ini. If we create a new
> instance, does that mean we can utilize the other 2 GB of Memory on the
> server? Security is not a major concern when using single instance. What
> are
> the Pros and Cons?
> Thank you very much for your help.
>|||Thank you very much.
This is a dedicated SQL server. I find out in my situation the OS use very
little memory. Probably If I reserve 256M to 300M for the OS is enough.
Currently the peak for the OS Memory usage is around 250M.
"Andrew J. Kelly" wrote:
> You need Enterprise edition to use more than 2GB. Windows 2000 server does
> not use the /3GB switch other than in a test scenario. Yes you can use two
> instances and each can use 2GB but you have to be careful as now you can
> lead to a situation where there is little left for the OS. If you are
> consolidating then you should look at using Enterprise edition and Win2000
> ADV Server (or Win2003) so you can use all 3GB for Sql Server and have a GB
> for the OS and any other apps.
> --
> Andrew J. Kelly SQL MVP
>
> "royHe" <royHe@.discussions.microsoft.com> wrote in message
> news:8B395A5C-26F6-4E71-95B2-D9CE53E62100@.microsoft.com...
> >I have a Dell server with 4GB of memory and 4 CPUs with 1.6G each, hosting
> > one major application database. SQL Server 2000 Standard Edition was
> > installed on the server, OS is Windows 2000 Server. Currently with single
> > instance installed, I checked the memory usage using task manager, the
> > wholes
> > system can only use up to less then 2 GB of memory. The peak is less than
> > 2
> > GB. The system neven utilizing more than 2 GM of memory. I am in the
> > process
> > of doing server consolidation and planning to move another major
> > application
> > database to this dell server. I want to utilize 4 G of memory after I
> > consolidate the other SQL server to the Dell Server. If I just move the
> > database to this dell server without creating a new instance, the most
> > memory
> > we can utilize is 3GB with 3 GB switch set in boot.ini. If we create a new
> > instance, does that mean we can utilize the other 2 GB of Memory on the
> > server? Security is not a major concern when using single instance. What
> > are
> > the Pros and Cons?
> >
> > Thank you very much for your help.
> >
> >
>
>
Multiple Instance Memory Utilization
I have a Dell server with 4GB of memory and 4 CPUs with 1.6G each, hosting
one major application database. SQL Server 2000 Standard Edition was
installed on the server, OS is Windows 2000 Server. Currently with single
instance installed, I checked the memory usage using task manager, the whole
s
system can only use up to less then 2 GB of memory. The peak is less than 2
GB. The system neven utilizing more than 2 GM of memory. I am in the proces
s
of doing server consolidation and planning to move another major application
database to this dell server. I want to utilize 4 G of memory after I
consolidate the other SQL server to the Dell Server. If I just move the
database to this dell server without creating a new instance, the most memor
y
we can utilize is 3GB with 3 GB switch set in boot.ini. If we create a new
instance, does that mean we can utilize the other 2 GB of Memory on the
server? Security is not a major concern when using single instance. What ar
e
the Pros and Cons?
Thank you very much for your help.You need Enterprise edition to use more than 2GB. Windows 2000 server does
not use the /3GB switch other than in a test scenario. Yes you can use two
instances and each can use 2GB but you have to be careful as now you can
lead to a situation where there is little left for the OS. If you are
consolidating then you should look at using Enterprise edition and Win2000
ADV Server (or Win2003) so you can use all 3GB for Sql Server and have a GB
for the OS and any other apps.
Andrew J. Kelly SQL MVP
"royHe" <royHe@.discussions.microsoft.com> wrote in message
news:8B395A5C-26F6-4E71-95B2-D9CE53E62100@.microsoft.com...
>I have a Dell server with 4GB of memory and 4 CPUs with 1.6G each, hosting
> one major application database. SQL Server 2000 Standard Edition was
> installed on the server, OS is Windows 2000 Server. Currently with single
> instance installed, I checked the memory usage using task manager, the
> wholes
> system can only use up to less then 2 GB of memory. The peak is less than
> 2
> GB. The system neven utilizing more than 2 GM of memory. I am in the
> process
> of doing server consolidation and planning to move another major
> application
> database to this dell server. I want to utilize 4 G of memory after I
> consolidate the other SQL server to the Dell Server. If I just move the
> database to this dell server without creating a new instance, the most
> memory
> we can utilize is 3GB with 3 GB switch set in boot.ini. If we create a new
> instance, does that mean we can utilize the other 2 GB of Memory on the
> server? Security is not a major concern when using single instance. What
> are
> the Pros and Cons?
> Thank you very much for your help.
>|||Thank you very much.
This is a dedicated SQL server. I find out in my situation the OS use very
little memory. Probably If I reserve 256M to 300M for the OS is enough.
Currently the peak for the OS Memory usage is around 250M.
"Andrew J. Kelly" wrote:
> You need Enterprise edition to use more than 2GB. Windows 2000 server do
es
> not use the /3GB switch other than in a test scenario. Yes you can use tw
o
> instances and each can use 2GB but you have to be careful as now you can
> lead to a situation where there is little left for the OS. If you are
> consolidating then you should look at using Enterprise edition and Win2000
> ADV Server (or Win2003) so you can use all 3GB for Sql Server and have a G
B
> for the OS and any other apps.
> --
> Andrew J. Kelly SQL MVP
>
> "royHe" <royHe@.discussions.microsoft.com> wrote in message
> news:8B395A5C-26F6-4E71-95B2-D9CE53E62100@.microsoft.com...
>
>sql
one major application database. SQL Server 2000 Standard Edition was
installed on the server, OS is Windows 2000 Server. Currently with single
instance installed, I checked the memory usage using task manager, the whole
s
system can only use up to less then 2 GB of memory. The peak is less than 2
GB. The system neven utilizing more than 2 GM of memory. I am in the proces
s
of doing server consolidation and planning to move another major application
database to this dell server. I want to utilize 4 G of memory after I
consolidate the other SQL server to the Dell Server. If I just move the
database to this dell server without creating a new instance, the most memor
y
we can utilize is 3GB with 3 GB switch set in boot.ini. If we create a new
instance, does that mean we can utilize the other 2 GB of Memory on the
server? Security is not a major concern when using single instance. What ar
e
the Pros and Cons?
Thank you very much for your help.You need Enterprise edition to use more than 2GB. Windows 2000 server does
not use the /3GB switch other than in a test scenario. Yes you can use two
instances and each can use 2GB but you have to be careful as now you can
lead to a situation where there is little left for the OS. If you are
consolidating then you should look at using Enterprise edition and Win2000
ADV Server (or Win2003) so you can use all 3GB for Sql Server and have a GB
for the OS and any other apps.
Andrew J. Kelly SQL MVP
"royHe" <royHe@.discussions.microsoft.com> wrote in message
news:8B395A5C-26F6-4E71-95B2-D9CE53E62100@.microsoft.com...
>I have a Dell server with 4GB of memory and 4 CPUs with 1.6G each, hosting
> one major application database. SQL Server 2000 Standard Edition was
> installed on the server, OS is Windows 2000 Server. Currently with single
> instance installed, I checked the memory usage using task manager, the
> wholes
> system can only use up to less then 2 GB of memory. The peak is less than
> 2
> GB. The system neven utilizing more than 2 GM of memory. I am in the
> process
> of doing server consolidation and planning to move another major
> application
> database to this dell server. I want to utilize 4 G of memory after I
> consolidate the other SQL server to the Dell Server. If I just move the
> database to this dell server without creating a new instance, the most
> memory
> we can utilize is 3GB with 3 GB switch set in boot.ini. If we create a new
> instance, does that mean we can utilize the other 2 GB of Memory on the
> server? Security is not a major concern when using single instance. What
> are
> the Pros and Cons?
> Thank you very much for your help.
>|||Thank you very much.
This is a dedicated SQL server. I find out in my situation the OS use very
little memory. Probably If I reserve 256M to 300M for the OS is enough.
Currently the peak for the OS Memory usage is around 250M.
"Andrew J. Kelly" wrote:
> You need Enterprise edition to use more than 2GB. Windows 2000 server do
es
> not use the /3GB switch other than in a test scenario. Yes you can use tw
o
> instances and each can use 2GB but you have to be careful as now you can
> lead to a situation where there is little left for the OS. If you are
> consolidating then you should look at using Enterprise edition and Win2000
> ADV Server (or Win2003) so you can use all 3GB for Sql Server and have a G
B
> for the OS and any other apps.
> --
> Andrew J. Kelly SQL MVP
>
> "royHe" <royHe@.discussions.microsoft.com> wrote in message
> news:8B395A5C-26F6-4E71-95B2-D9CE53E62100@.microsoft.com...
>
>sql
Subscribe to:
Posts (Atom)