AWE and 3GB switches

I'm configuring a new server with Windows 2003 Enterprise SP1 and SQL Server
2000 Enterprise/SP3a. The server has 8GB of RAM
I have set the /PAE switch in boot.ini and then ran the following:
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
I can confirm using the SQL Server:Memory Manager-Total Server Memory
counter that SQL Server is using 6303928 kbs of memory.
Should I be using the 3GB switch? If so why?
If you want to use as much of the 8GB SQL server then no.
Using the /3G switch will allow only up to 3GB of RAM to SQL Server.
Likewise, you should leave approx. 1GB of RAM for the OS for every 8GB of
RAM available.
MG
"Terri" wrote:

> I'm configuring a new server with Windows 2003 Enterprise SP1 and SQL Server
> 2000 Enterprise/SP3a. The server has 8GB of RAM
> I have set the /PAE switch in boot.ini and then ran the following:
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> I can confirm using the SQL Server:Memory Manager-Total Server Memory
> counter that SQL Server is using 6303928 kbs of memory.
> Should I be using the 3GB switch? If so why?
>
>
>
|||Hurme, thanks for your response. My confusion on this issue unfortunately
persists. Subsequent to my post I found the following article which says I
should use both, /3GB and /PAE.
http://www.sql-server-performance.com/sql_server_performance_audit5.asp
"Hurme" <michael.geles@.thomson.com> wrote in message
news:93A66D75-882B-4501-9607-309CC354FA40@.microsoft.com...[vbcol=seagreen]
> If you want to use as much of the 8GB SQL server then no.
> Using the /3G switch will allow only up to 3GB of RAM to SQL Server.
> Likewise, you should leave approx. 1GB of RAM for the OS for every 8GB of
> RAM available.
> --
> MG
>
> "Terri" wrote:
Server[vbcol=seagreen]
|||Hmmm...the wording is a little ambiguous. It does say in the article, "you
must enter one of the following switches in the boot line of the boot.ini
file..." and Perfmon is showing that more than 6GB on RAM is getting used.
Here is a line that found in another article
http://support.microsoft.com/default.aspx/kb/274750 :
"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 3 GB of memory."
It's doesn't say that you need both flags to use more that 4GB.
HTH
MG
"Terri" wrote:

> Hurme, thanks for your response. My confusion on this issue unfortunately
> persists. Subsequent to my post I found the following article which says I
> should use both, /3GB and /PAE.
> http://www.sql-server-performance.com/sql_server_performance_audit5.asp
> "Hurme" <michael.geles@.thomson.com> wrote in message
> news:93A66D75-882B-4501-9607-309CC354FA40@.microsoft.com...
> Server
>
>
|||Yes, there is some ambiguity. Perhaps others will chime in with additional
thoughts.
"Hurme" <michael.geles@.thomson.com> wrote in message
news:1A5C69C9-0D56-4F33-845C-457C11FAEE62@.microsoft.com...
> Hmmm...the wording is a little ambiguous. It does say in the article,
"you
> must enter one of the following switches in the boot line of the boot.ini
> file..." and Perfmon is showing that more than 6GB on RAM is getting used.
> Here is a line that found in another article
> http://support.microsoft.com/default.aspx/kb/274750 :
> "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 3 GB of memory."
> It's doesn't say that you need both flags to use more that 4GB.
>
|||Terry
http://support.microsoft.com/kb/283037/en-us
With more than 4GB, then you should use PAE, whether or not Win2K3 enables
this for you or not, use the registry settings to determine if it was
detected, but AWE will require PAE to make use of any address space above
4GB. In fact, the OS and SS will not even recognize memory greater than 4GB
even exists without PAE enabled.
"Terri" <terri@.cybernets.com> wrote in message
news:f0lsmn$g2k$1@.reader2.nmix.net...
> Yes, there is some ambiguity. Perhaps others will chime in with additional
> thoughts.
> "Hurme" <michael.geles@.thomson.com> wrote in message
> news:1A5C69C9-0D56-4F33-845C-457C11FAEE62@.microsoft.com...
> "you
> the
>

AWE and 3GB switches

I'm configuring a new server with Windows 2003 Enterprise SP1 and SQL Server
2000 Enterprise/SP3a. The server has 8GB of RAM
I have set the /PAE switch in boot.ini and then ran the following:
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
I can confirm using the SQL Server:Memory Manager-Total Server Memory
counter that SQL Server is using 6303928 kbs of memory.
Should I be using the 3GB switch? If so why?If you want to use as much of the 8GB SQL server then no.
Using the /3G switch will allow only up to 3GB of RAM to SQL Server.
Likewise, you should leave approx. 1GB of RAM for the OS for every 8GB of
RAM available.
--
MG
"Terri" wrote:

> I'm configuring a new server with Windows 2003 Enterprise SP1 and SQL Serv
er
> 2000 Enterprise/SP3a. The server has 8GB of RAM
> I have set the /PAE switch in boot.ini and then ran the following:
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> I can confirm using the SQL Server:Memory Manager-Total Server Memory
> counter that SQL Server is using 6303928 kbs of memory.
> Should I be using the 3GB switch? If so why?
>
>
>|||Hurme, thanks for your response. My confusion on this issue unfortunately
persists. Subsequent to my post I found the following article which says I
should use both, /3GB and /PAE.
http://www.sql-server-performance.c...ance_audit5.asp
"Hurme" <michael.geles@.thomson.com> wrote in message
news:93A66D75-882B-4501-9607-309CC354FA40@.microsoft.com...[vbcol=seagreen]
> If you want to use as much of the 8GB SQL server then no.
> Using the /3G switch will allow only up to 3GB of RAM to SQL Server.
> Likewise, you should leave approx. 1GB of RAM for the OS for every 8GB of
> RAM available.
> --
> MG
>
> "Terri" wrote:
>
Server[vbcol=seagreen]|||Hmmm...the wording is a little ambiguous. It does say in the article, "you
must enter one of the following switches in the boot line of the boot.ini
file..." and Perfmon is showing that more than 6GB on RAM is getting used.
Here is a line that found in another article
http://support.microsoft.com/default.aspx/kb/274750 :
"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 3 GB of memory."
It's doesn't say that you need both flags to use more that 4GB.
HTH
--
MG
"Terri" wrote:

> Hurme, thanks for your response. My confusion on this issue unfortunately
> persists. Subsequent to my post I found the following article which says I
> should use both, /3GB and /PAE.
> http://www.sql-server-performance.c...ance_audit5.asp
> "Hurme" <michael.geles@.thomson.com> wrote in message
> news:93A66D75-882B-4501-9607-309CC354FA40@.microsoft.com...
> Server
>
>|||Yes, there is some ambiguity. Perhaps others will chime in with additional
thoughts.
"Hurme" <michael.geles@.thomson.com> wrote in message
news:1A5C69C9-0D56-4F33-845C-457C11FAEE62@.microsoft.com...
> Hmmm...the wording is a little ambiguous. It does say in the article,
"you
> must enter one of the following switches in the boot line of the boot.ini
> file..." and Perfmon is showing that more than 6GB on RAM is getting used.
> Here is a line that found in another article
> http://support.microsoft.com/default.aspx/kb/274750 :
> "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 3 GB of memory."
> It's doesn't say that you need both flags to use more that 4GB.
>|||Terry
http://support.microsoft.com/kb/283037/en-us
With more than 4GB, then you should use PAE, whether or not Win2K3 enables
this for you or not, use the registry settings to determine if it was
detected, but AWE will require PAE to make use of any address space above
4GB. In fact, the OS and SS will not even recognize memory greater than 4GB
even exists without PAE enabled.
"Terri" <terri@.cybernets.com> wrote in message
news:f0lsmn$g2k$1@.reader2.nmix.net...
> Yes, there is some ambiguity. Perhaps others will chime in with additional
> thoughts.
> "Hurme" <michael.geles@.thomson.com> wrote in message
> news:1A5C69C9-0D56-4F33-845C-457C11FAEE62@.microsoft.com...
> "you
> the
>

AutoNumber Primary Key

We are testing the upload of an Access 2002 data database to SQL Server
2000. Some of the tables had AutoNumber fields that were Random (due to it
being a replicated table in Access). The upload created triggers similar to
the example below. However, Access applications fail on insert because the
primary key field is not populated until the trigger runs. Any help is
appreciated.
CREATE TRIGGER T_AssessmentDocs_ITrig ON dbo.AssessmentDocs FOR INSERT AS
SET NOCOUNT ON
DECLARE @.randc int, @.newc int /* FOR AUTONUMBER-EMULATION CODE */
/* * RANDOM AUTONUMBER EMULATION CODE FOR FIELD 'DocID' */
SELECT @.randc = (SELECT convert(int, rand() * power(2, 30)))
SELECT @.newc = (SELECT DocID FROM inserted)
UPDATE AssessmentDocs SET DocID = @.randc WHERE DocID = @.newc
David
David C wrote:
> We are testing the upload of an Access 2002 data database to SQL
> Server 2000. Some of the tables had AutoNumber fields that were
> Random (due to it being a replicated table in Access). The upload
> created triggers similar to the example below. However, Access
> applications fail on insert because the primary key field is not
> populated until the trigger runs. Any help is appreciated.
> CREATE TRIGGER T_AssessmentDocs_ITrig ON dbo.AssessmentDocs FOR
> INSERT AS SET NOCOUNT ON
> DECLARE @.randc int, @.newc int /* FOR AUTONUMBER-EMULATION CODE */
> /* * RANDOM AUTONUMBER EMULATION CODE FOR FIELD 'DocID' */
> SELECT @.randc = (SELECT convert(int, rand() * power(2, 30)))
> SELECT @.newc = (SELECT DocID FROM inserted)
> UPDATE AssessmentDocs SET DocID = @.randc WHERE DocID = @.newc
> David
Change the column to an IDENTITY value. SQL Server automates the
generation of the next value. You may have to seed the identity value
using the MAX(ID) + 1 in the table.
You can pull back the newly inserted identity value into the application
using the SCOPE_IDENTITY() function.
David Gugick
Imceda Software
www.imceda.com
|||David Gugick wrote:
> David C wrote:
> Change the column to an IDENTITY value. SQL Server automates the
> generation of the next value. You may have to seed the identity value
> using the MAX(ID) + 1 in the table.
Or by using DBCC CHECKIDENT, which should do the same job.

AutoNumber Primary Key

We are testing the upload of an Access 2002 data database to SQL Server
2000. Some of the tables had AutoNumber fields that were Random (due to it
being a replicated table in Access). The upload created triggers similar to
the example below. However, Access applications fail on insert because the
primary key field is not populated until the trigger runs. Any help is
appreciated.
CREATE TRIGGER T_AssessmentDocs_ITrig ON dbo.AssessmentDocs FOR INSERT AS
SET NOCOUNT ON
DECLARE @.randc int, @.newc int /* FOR AUTONUMBER-EMULATION CODE */
/* * RANDOM AUTONUMBER EMULATION CODE FOR FIELD 'DocID' */
SELECT @.randc = (SELECT convert(int, rand() * power(2, 30)))
SELECT @.newc = (SELECT DocID FROM inserted)
UPDATE AssessmentDocs SET DocID = @.randc WHERE DocID = @.newc
DavidDavid C wrote:
> We are testing the upload of an Access 2002 data database to SQL
> Server 2000. Some of the tables had AutoNumber fields that were
> Random (due to it being a replicated table in Access). The upload
> created triggers similar to the example below. However, Access
> applications fail on insert because the primary key field is not
> populated until the trigger runs. Any help is appreciated.
> CREATE TRIGGER T_AssessmentDocs_ITrig ON dbo.AssessmentDocs FOR
> INSERT AS SET NOCOUNT ON
> DECLARE @.randc int, @.newc int /* FOR AUTONUMBER-EMULATION CODE */
> /* * RANDOM AUTONUMBER EMULATION CODE FOR FIELD 'DocID' */
> SELECT @.randc = (SELECT convert(int, rand() * power(2, 30)))
> SELECT @.newc = (SELECT DocID FROM inserted)
> UPDATE AssessmentDocs SET DocID = @.randc WHERE DocID = @.newc
> David
Change the column to an IDENTITY value. SQL Server automates the
generation of the next value. You may have to seed the identity value
using the MAX(ID) + 1 in the table.
You can pull back the newly inserted identity value into the application
using the SCOPE_IDENTITY() function.
David Gugick
Imceda Software
www.imceda.com|||David Gugick wrote:
> David C wrote:
> Change the column to an IDENTITY value. SQL Server automates the
> generation of the next value. You may have to seed the identity value
> using the MAX(ID) + 1 in the table.
Or by using DBCC CHECKIDENT, which should do the same job.