instances of SQL. Server sees the full 32GB of memory without any problems
with the /PAE option enabled. Problem is when a instance is configured for
the exact size of 8192mb the instance has a hard time starting. It fails
multiple times and what when a normal startup takes 30 seconds can now 10
minutes or more to get going. Any instance goes back to normal by changing
to a different number other than 8192 as the memory allocation. Just curious
if any else has seen this problem with this "magic" number.This is a multi-part message in MIME format.
--=_NextPart_000_0016_01C4846C.1D613220
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
We have seen this problem, and I believe that a fix is being considered =for SQL 2000 SP4.
Thanks!
Ryan Stonecipher
Microsoft SQL Server Storage Engine
"Rich" <Rich@.discussions.microsoft.com> wrote in message =news:C90B5CAD-773E-4A75-8A99-06DBFC8A3C6C@.microsoft.com...
I have windows 2003 with 4 CPU's and 32GB of memory running multiple instances of SQL. Server sees the full 32GB of memory without any =problems with the /PAE option enabled. Problem is when a instance is =configured for the exact size of 8192mb the instance has a hard time starting. It =fails multiple times and what when a normal startup takes 30 seconds can now =10 minutes or more to get going. Any instance goes back to normal by =changing to a different number other than 8192 as the memory allocation. Just =curious if any else has seen this problem with this "magic" number.
--=_NextPart_000_0016_01C4846C.1D613220
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
We have seen this problem, and =I believe that a fix is being considered for SQL 2000 SP4.
Thanks!
Ryan Stonecipher
Microsoft SQL Server Storage Engine
"Rich"
--=_NextPart_000_0016_01C4846C.1D613220--|||Ryan, were you not assisting on replication a year or 2 ago ?
"Ryan Stonecipher [MSFT]" <ryanston@.online.microsoft.com> wrote in message
news:u3CXMbKhEHA.1656@.TK2MSFTNGP09.phx.gbl...
We have seen this problem, and I believe that a fix is being considered for
SQL 2000 SP4.
Thanks!
Ryan Stonecipher
Microsoft SQL Server Storage Engine
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:C90B5CAD-773E-4A75-8A99-06DBFC8A3C6C@.microsoft.com...
I have windows 2003 with 4 CPU's and 32GB of memory running multiple
instances of SQL. Server sees the full 32GB of memory without any problems
with the /PAE option enabled. Problem is when a instance is configured for
the exact size of 8192mb the instance has a hard time starting. It fails
multiple times and what when a normal startup takes 30 seconds can now 10
minutes or more to get going. Any instance goes back to normal by changing
to a different number other than 8192 as the memory allocation. Just
curious
if any else has seen this problem with this "magic" number.
No comments:
Post a Comment