Hi All,
I have a recent requirement to move production databases from a Live Server
running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
move this one into production
Currently, the new Server is running SQL 2000 SP3a (the same as the current
Live SQL server) as we were going to move User Databases to this version
until the requirement for SP4 came along.
Please can you advise what is the best procedure to acheive this with
minimal downtime and risk.
- Can User databases be moved to the New Server which has been upgraded to
SP4 or do all user databases need to be moved to the SP4 server, then the
server upgraded ?
- Clearly it would be more straightforward to upgrade the new Server to SP4
before moving User databases to it, but do not have info of the issues
concered with this.
Thanks in advance for you help and I hope to received a speedy response
Ben
You can do a simple backup/restore or detach/attach. However, for max
uptime, consider log shipping. You're down only for the time it takes to
kick out the users, and copy and restore the last log.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Ben P" <BenP@.discussions.microsoft.com> wrote in message
news:B79F8D95-B0A9-46C6-B8C0-5F89BDEF02B9@.microsoft.com...
Hi All,
I have a recent requirement to move production databases from a Live Server
running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
move this one into production
Currently, the new Server is running SQL 2000 SP3a (the same as the current
Live SQL server) as we were going to move User Databases to this version
until the requirement for SP4 came along.
Please can you advise what is the best procedure to acheive this with
minimal downtime and risk.
- Can User databases be moved to the New Server which has been upgraded to
SP4 or do all user databases need to be moved to the SP4 server, then the
server upgraded ?
- Clearly it would be more straightforward to upgrade the new Server to SP4
before moving User databases to it, but do not have info of the issues
concered with this.
Thanks in advance for you help and I hope to received a speedy response
Ben
|||Just to confirm - Does that mean we can upgrade the new Server to SP4, then
restore the user DBs from the SP3a server on to this new one with out any
issues? Obviusly Backing up the databases before hand and straight after the
restore
Ben
"Tom Moreau" wrote:
> You can do a simple backup/restore or detach/attach. However, for max
> uptime, consider log shipping. You're down only for the time it takes to
> kick out the users, and copy and restore the last log.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Ben P" <BenP@.discussions.microsoft.com> wrote in message
> news:B79F8D95-B0A9-46C6-B8C0-5F89BDEF02B9@.microsoft.com...
> Hi All,
> I have a recent requirement to move production databases from a Live Server
> running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
> move this one into production
> Currently, the new Server is running SQL 2000 SP3a (the same as the current
> Live SQL server) as we were going to move User Databases to this version
> until the requirement for SP4 came along.
> Please can you advise what is the best procedure to acheive this with
> minimal downtime and risk.
> - Can User databases be moved to the New Server which has been upgraded to
> SP4 or do all user databases need to be moved to the SP4 server, then the
> server upgraded ?
> - Clearly it would be more straightforward to upgrade the new Server to SP4
> before moving User databases to it, but do not have info of the issues
> concered with this.
> Thanks in advance for you help and I hope to received a speedy response
> --
> Ben
>
|||Yes. Be sure to transfer the logins first, as well as and SQL Server Agent
jobs. You may also want to look at any DTS packages that have the server
name hard-wired.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
"Ben P" <BenP@.discussions.microsoft.com> wrote in message
news:C1760DC8-F77A-40D1-BC0E-F4C0146E6118@.microsoft.com...
Just to confirm - Does that mean we can upgrade the new Server to SP4, then
restore the user DBs from the SP3a server on to this new one with out any
issues? Obviusly Backing up the databases before hand and straight after the
restore
Ben
"Tom Moreau" wrote:
> You can do a simple backup/restore or detach/attach. However, for max
> uptime, consider log shipping. You're down only for the time it takes to
> kick out the users, and copy and restore the last log.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Ben P" <BenP@.discussions.microsoft.com> wrote in message
> news:B79F8D95-B0A9-46C6-B8C0-5F89BDEF02B9@.microsoft.com...
> Hi All,
> I have a recent requirement to move production databases from a Live
> Server
> running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
> move this one into production
> Currently, the new Server is running SQL 2000 SP3a (the same as the
> current
> Live SQL server) as we were going to move User Databases to this version
> until the requirement for SP4 came along.
> Please can you advise what is the best procedure to acheive this with
> minimal downtime and risk.
> - Can User databases be moved to the New Server which has been upgraded to
> SP4 or do all user databases need to be moved to the SP4 server, then the
> server upgraded ?
> - Clearly it would be more straightforward to upgrade the new Server to
> SP4
> before moving User databases to it, but do not have info of the issues
> concered with this.
> Thanks in advance for you help and I hope to received a speedy response
> --
> Ben
>
|||Thanks for the update Tom
Will will be transferrring the logins, but creating new maintenance plan
jobs on the SP4 upgraded server.
Will these Maintenance plans work ok on the Databases transferred from the
SP3a server ?
Ben
"Tom Moreau" wrote:
> Yes. Be sure to transfer the logins first, as well as and SQL Server Agent
> jobs. You may also want to look at any DTS packages that have the server
> name hard-wired.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> "Ben P" <BenP@.discussions.microsoft.com> wrote in message
> news:C1760DC8-F77A-40D1-BC0E-F4C0146E6118@.microsoft.com...
> Just to confirm - Does that mean we can upgrade the new Server to SP4, then
> restore the user DBs from the SP3a server on to this new one with out any
> issues? Obviusly Backing up the databases before hand and straight after the
> restore
> --
> Ben
>
> "Tom Moreau" wrote:
>
>
Showing posts with label serverrunning. Show all posts
Showing posts with label serverrunning. Show all posts
Friday, March 30, 2012
Moving User Databases from a SQL 2000 SP3a to SP4
Hi All,
I have a recent requirement to move production databases from a Live Server
running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
move this one into production
Currently, the new Server is running SQL 2000 SP3a (the same as the current
Live SQL server) as we were going to move User Databases to this version
until the requirement for SP4 came along.
Please can you advise what is the best procedure to acheive this with
minimal downtime and risk.
- Can User databases be moved to the New Server which has been upgraded to
SP4 or do all user databases need to be moved to the SP4 server, then the
server upgraded ?
- Clearly it would be more straightforward to upgrade the new Server to SP4
before moving User databases to it, but do not have info of the issues
concered with this.
Thanks in advance for you help and I hope to received a speedy response
BenYou can do a simple backup/restore or detach/attach. However, for max
uptime, consider log shipping. You're down only for the time it takes to
kick out the users, and copy and restore the last log.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Ben P" <BenP@.discussions.microsoft.com> wrote in message
news:B79F8D95-B0A9-46C6-B8C0-5F89BDEF02B9@.microsoft.com...
Hi All,
I have a recent requirement to move production databases from a Live Server
running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
move this one into production
Currently, the new Server is running SQL 2000 SP3a (the same as the current
Live SQL server) as we were going to move User Databases to this version
until the requirement for SP4 came along.
Please can you advise what is the best procedure to acheive this with
minimal downtime and risk.
- Can User databases be moved to the New Server which has been upgraded to
SP4 or do all user databases need to be moved to the SP4 server, then the
server upgraded ?
- Clearly it would be more straightforward to upgrade the new Server to SP4
before moving User databases to it, but do not have info of the issues
concered with this.
Thanks in advance for you help and I hope to received a speedy response
Ben|||Just to confirm - Does that mean we can upgrade the new Server to SP4, then
restore the user DBs from the SP3a server on to this new one with out any
issues? Obviusly Backing up the databases before hand and straight after the
restore
Ben
"Tom Moreau" wrote:
> You can do a simple backup/restore or detach/attach. However, for max
> uptime, consider log shipping. You're down only for the time it takes to
> kick out the users, and copy and restore the last log.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Ben P" <BenP@.discussions.microsoft.com> wrote in message
> news:B79F8D95-B0A9-46C6-B8C0-5F89BDEF02B9@.microsoft.com...
> Hi All,
> I have a recent requirement to move production databases from a Live Serve
r
> running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
> move this one into production
> Currently, the new Server is running SQL 2000 SP3a (the same as the curren
t
> Live SQL server) as we were going to move User Databases to this version
> until the requirement for SP4 came along.
> Please can you advise what is the best procedure to acheive this with
> minimal downtime and risk.
> - Can User databases be moved to the New Server which has been upgraded to
> SP4 or do all user databases need to be moved to the SP4 server, then the
> server upgraded ?
> - Clearly it would be more straightforward to upgrade the new Server to SP
4
> before moving User databases to it, but do not have info of the issues
> concered with this.
> Thanks in advance for you help and I hope to received a speedy response
> --
> Ben
>|||Yes. Be sure to transfer the logins first, as well as and SQL Server Agent
jobs. You may also want to look at any DTS packages that have the server
name hard-wired.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
"Ben P" <BenP@.discussions.microsoft.com> wrote in message
news:C1760DC8-F77A-40D1-BC0E-F4C0146E6118@.microsoft.com...
Just to confirm - Does that mean we can upgrade the new Server to SP4, then
restore the user DBs from the SP3a server on to this new one with out any
issues? Obviusly Backing up the databases before hand and straight after the
restore
Ben
"Tom Moreau" wrote:
> You can do a simple backup/restore or detach/attach. However, for max
> uptime, consider log shipping. You're down only for the time it takes to
> kick out the users, and copy and restore the last log.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Ben P" <BenP@.discussions.microsoft.com> wrote in message
> news:B79F8D95-B0A9-46C6-B8C0-5F89BDEF02B9@.microsoft.com...
> Hi All,
> I have a recent requirement to move production databases from a Live
> Server
> running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
> move this one into production
> Currently, the new Server is running SQL 2000 SP3a (the same as the
> current
> Live SQL server) as we were going to move User Databases to this version
> until the requirement for SP4 came along.
> Please can you advise what is the best procedure to acheive this with
> minimal downtime and risk.
> - Can User databases be moved to the New Server which has been upgraded to
> SP4 or do all user databases need to be moved to the SP4 server, then the
> server upgraded ?
> - Clearly it would be more straightforward to upgrade the new Server to
> SP4
> before moving User databases to it, but do not have info of the issues
> concered with this.
> Thanks in advance for you help and I hope to received a speedy response
> --
> Ben
>|||Thanks for the update Tom
Will will be transferrring the logins, but creating new maintenance plan
jobs on the SP4 upgraded server.
Will these Maintenance plans work ok on the Databases transferred from the
SP3a server ?
Ben
"Tom Moreau" wrote:
> Yes. Be sure to transfer the logins first, as well as and SQL Server Agen
t
> jobs. You may also want to look at any DTS packages that have the server
> name hard-wired.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> "Ben P" <BenP@.discussions.microsoft.com> wrote in message
> news:C1760DC8-F77A-40D1-BC0E-F4C0146E6118@.microsoft.com...
> Just to confirm - Does that mean we can upgrade the new Server to SP4, the
n
> restore the user DBs from the SP3a server on to this new one with out any
> issues? Obviusly Backing up the databases before hand and straight after t
he
> restore
> --
> Ben
>
> "Tom Moreau" wrote:
>
>
>
I have a recent requirement to move production databases from a Live Server
running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
move this one into production
Currently, the new Server is running SQL 2000 SP3a (the same as the current
Live SQL server) as we were going to move User Databases to this version
until the requirement for SP4 came along.
Please can you advise what is the best procedure to acheive this with
minimal downtime and risk.
- Can User databases be moved to the New Server which has been upgraded to
SP4 or do all user databases need to be moved to the SP4 server, then the
server upgraded ?
- Clearly it would be more straightforward to upgrade the new Server to SP4
before moving User databases to it, but do not have info of the issues
concered with this.
Thanks in advance for you help and I hope to received a speedy response
BenYou can do a simple backup/restore or detach/attach. However, for max
uptime, consider log shipping. You're down only for the time it takes to
kick out the users, and copy and restore the last log.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Ben P" <BenP@.discussions.microsoft.com> wrote in message
news:B79F8D95-B0A9-46C6-B8C0-5F89BDEF02B9@.microsoft.com...
Hi All,
I have a recent requirement to move production databases from a Live Server
running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
move this one into production
Currently, the new Server is running SQL 2000 SP3a (the same as the current
Live SQL server) as we were going to move User Databases to this version
until the requirement for SP4 came along.
Please can you advise what is the best procedure to acheive this with
minimal downtime and risk.
- Can User databases be moved to the New Server which has been upgraded to
SP4 or do all user databases need to be moved to the SP4 server, then the
server upgraded ?
- Clearly it would be more straightforward to upgrade the new Server to SP4
before moving User databases to it, but do not have info of the issues
concered with this.
Thanks in advance for you help and I hope to received a speedy response
Ben|||Just to confirm - Does that mean we can upgrade the new Server to SP4, then
restore the user DBs from the SP3a server on to this new one with out any
issues? Obviusly Backing up the databases before hand and straight after the
restore
Ben
"Tom Moreau" wrote:
> You can do a simple backup/restore or detach/attach. However, for max
> uptime, consider log shipping. You're down only for the time it takes to
> kick out the users, and copy and restore the last log.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Ben P" <BenP@.discussions.microsoft.com> wrote in message
> news:B79F8D95-B0A9-46C6-B8C0-5F89BDEF02B9@.microsoft.com...
> Hi All,
> I have a recent requirement to move production databases from a Live Serve
r
> running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
> move this one into production
> Currently, the new Server is running SQL 2000 SP3a (the same as the curren
t
> Live SQL server) as we were going to move User Databases to this version
> until the requirement for SP4 came along.
> Please can you advise what is the best procedure to acheive this with
> minimal downtime and risk.
> - Can User databases be moved to the New Server which has been upgraded to
> SP4 or do all user databases need to be moved to the SP4 server, then the
> server upgraded ?
> - Clearly it would be more straightforward to upgrade the new Server to SP
4
> before moving User databases to it, but do not have info of the issues
> concered with this.
> Thanks in advance for you help and I hope to received a speedy response
> --
> Ben
>|||Yes. Be sure to transfer the logins first, as well as and SQL Server Agent
jobs. You may also want to look at any DTS packages that have the server
name hard-wired.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
"Ben P" <BenP@.discussions.microsoft.com> wrote in message
news:C1760DC8-F77A-40D1-BC0E-F4C0146E6118@.microsoft.com...
Just to confirm - Does that mean we can upgrade the new Server to SP4, then
restore the user DBs from the SP3a server on to this new one with out any
issues? Obviusly Backing up the databases before hand and straight after the
restore
Ben
"Tom Moreau" wrote:
> You can do a simple backup/restore or detach/attach. However, for max
> uptime, consider log shipping. You're down only for the time it takes to
> kick out the users, and copy and restore the last log.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Ben P" <BenP@.discussions.microsoft.com> wrote in message
> news:B79F8D95-B0A9-46C6-B8C0-5F89BDEF02B9@.microsoft.com...
> Hi All,
> I have a recent requirement to move production databases from a Live
> Server
> running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
> move this one into production
> Currently, the new Server is running SQL 2000 SP3a (the same as the
> current
> Live SQL server) as we were going to move User Databases to this version
> until the requirement for SP4 came along.
> Please can you advise what is the best procedure to acheive this with
> minimal downtime and risk.
> - Can User databases be moved to the New Server which has been upgraded to
> SP4 or do all user databases need to be moved to the SP4 server, then the
> server upgraded ?
> - Clearly it would be more straightforward to upgrade the new Server to
> SP4
> before moving User databases to it, but do not have info of the issues
> concered with this.
> Thanks in advance for you help and I hope to received a speedy response
> --
> Ben
>|||Thanks for the update Tom
Will will be transferrring the logins, but creating new maintenance plan
jobs on the SP4 upgraded server.
Will these Maintenance plans work ok on the Databases transferred from the
SP3a server ?
Ben
"Tom Moreau" wrote:
> Yes. Be sure to transfer the logins first, as well as and SQL Server Agen
t
> jobs. You may also want to look at any DTS packages that have the server
> name hard-wired.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> "Ben P" <BenP@.discussions.microsoft.com> wrote in message
> news:C1760DC8-F77A-40D1-BC0E-F4C0146E6118@.microsoft.com...
> Just to confirm - Does that mean we can upgrade the new Server to SP4, the
n
> restore the user DBs from the SP3a server on to this new one with out any
> issues? Obviusly Backing up the databases before hand and straight after t
he
> restore
> --
> Ben
>
> "Tom Moreau" wrote:
>
>
>
Monday, March 19, 2012
Moving SQL Server 2000 to a new Virtual Server
Hi,
I am moving the default instance of a SQL Server 2000 to a ESX Server
running on VMWare. Below are the specifications:
Current Server:
SQL Server 2000 Enterprise Edition Version 8.00.2187
Windows Advanced Server 2000 SP4
Intel Pentium III 1400 MHz
4 GB RAM
/3 GB switch enabled in boot.ini
AWE not enabled and SQL Server using a maximum of 3 GB of RAM.
Target Server:
SQL Server 2000 Enterprise Edition Version 8.00.2187
Windows Server 2003 Enterprise Edition SP2
Intel Xeon X7350 2.93 GHz
3.75 GB RAM
/PAE 3 GB switch enabled in boot.ini
AWE not enabled
The target server is running on VMWare and we will be adding more memory to
it if it is needed in the future. What AWE setting should I be using on the
target machine?
Your target BOOT.INI has the /PAE switch enabled. Remove it and use /3GB.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"ronnie" <ronnie@.discussions.microsoft.com> wrote in message
news:C14D97C4-6190-4632-9A7B-D619F992B5CB@.microsoft.com...
Hi,
I am moving the default instance of a SQL Server 2000 to a ESX Server
running on VMWare. Below are the specifications:
Current Server:
SQL Server 2000 Enterprise Edition Version 8.00.2187
Windows Advanced Server 2000 SP4
Intel Pentium III 1400 MHz
4 GB RAM
/3 GB switch enabled in boot.ini
AWE not enabled and SQL Server using a maximum of 3 GB of RAM.
Target Server:
SQL Server 2000 Enterprise Edition Version 8.00.2187
Windows Server 2003 Enterprise Edition SP2
Intel Xeon X7350 2.93 GHz
3.75 GB RAM
/PAE 3 GB switch enabled in boot.ini
AWE not enabled
The target server is running on VMWare and we will be adding more memory to
it if it is needed in the future. What AWE setting should I be using on the
target machine?
|||Thanks a lot Tom for the quick response. Can you please explain the reason
why you want to have that change so that I can have a better understanding of
what's going on? Also, the target server has a Windows 2003 server in
comparison to the current server that is running on Windows 2000 server.
What would happen if the AWE is enabled? Thanks in advance.
"Tom Moreau" wrote:
> Your target BOOT.INI has the /PAE switch enabled. Remove it and use /3GB.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "ronnie" <ronnie@.discussions.microsoft.com> wrote in message
> news:C14D97C4-6190-4632-9A7B-D619F992B5CB@.microsoft.com...
> Hi,
> I am moving the default instance of a SQL Server 2000 to a ESX Server
> running on VMWare. Below are the specifications:
> Current Server:
> SQL Server 2000 Enterprise Edition Version 8.00.2187
> Windows Advanced Server 2000 SP4
> Intel Pentium III 1400 MHz
> 4 GB RAM
> /3 GB switch enabled in boot.ini
> AWE not enabled and SQL Server using a maximum of 3 GB of RAM.
>
> Target Server:
> SQL Server 2000 Enterprise Edition Version 8.00.2187
> Windows Server 2003 Enterprise Edition SP2
> Intel Xeon X7350 2.93 GHz
> 3.75 GB RAM
> /PAE 3 GB switch enabled in boot.ini
> AWE not enabled
> The target server is running on VMWare and we will be adding more memory to
> it if it is needed in the future. What AWE setting should I be using on the
> target machine?
>
|||What was referring to was this:
"/PAE 3 GB switch enabled in boot.ini"
It is self-contradictory. /PAE is not 3GB.
Also, you don't have enough memory to take advantage of AWE.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"ronnie" <ronnie@.discussions.microsoft.com> wrote in message
news:FCBE95A4-E3E6-4FCE-9548-090B812D9EB6@.microsoft.com...
Thanks a lot Tom for the quick response. Can you please explain the reason
why you want to have that change so that I can have a better understanding
of
what's going on? Also, the target server has a Windows 2003 server in
comparison to the current server that is running on Windows 2000 server.
What would happen if the AWE is enabled? Thanks in advance.
"Tom Moreau" wrote:
> Your target BOOT.INI has the /PAE switch enabled. Remove it and use /3GB.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "ronnie" <ronnie@.discussions.microsoft.com> wrote in message
> news:C14D97C4-6190-4632-9A7B-D619F992B5CB@.microsoft.com...
> Hi,
> I am moving the default instance of a SQL Server 2000 to a ESX Server
> running on VMWare. Below are the specifications:
> Current Server:
> SQL Server 2000 Enterprise Edition Version 8.00.2187
> Windows Advanced Server 2000 SP4
> Intel Pentium III 1400 MHz
> 4 GB RAM
> /3 GB switch enabled in boot.ini
> AWE not enabled and SQL Server using a maximum of 3 GB of RAM.
>
> Target Server:
> SQL Server 2000 Enterprise Edition Version 8.00.2187
> Windows Server 2003 Enterprise Edition SP2
> Intel Xeon X7350 2.93 GHz
> 3.75 GB RAM
> /PAE 3 GB switch enabled in boot.ini
> AWE not enabled
> The target server is running on VMWare and we will be adding more memory
> to
> it if it is needed in the future. What AWE setting should I be using on
> the
> target machine?
>
|||I just got to know that the RAM is going to be increased to 6 GB on the
target server before it goes into Production. How does it affect the /PAE or
the /3GB switch in boot.ini file and the AWE enabled / disabled on SQL Server?
Thanks in advance.
"ronnie" wrote:
[vbcol=seagreen]
> Thanks a lot Tom for the quick response. Can you please explain the reason
> why you want to have that change so that I can have a better understanding of
> what's going on? Also, the target server has a Windows 2003 server in
> comparison to the current server that is running on Windows 2000 server.
> What would happen if the AWE is enabled? Thanks in advance.
> "Tom Moreau" wrote:
|||That's different. In That case, I'd turn on both - once you get the extra
memory. Above 12GB, remove the /3GB switch:
[url]http://groups.google.ca/group/microsoft.public.sqlserver.clustering/browse_thread/thread/5eef281ae5d7ff59/0e83b85ef5b91530?hl=en&lnk=st&q=pae+3gb+hiten#0e83 b85ef5b91530[/url]
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"ronnie" <ronnie@.discussions.microsoft.com> wrote in message
news:051D8B41-A6F2-49FA-93A4-4DE697956DEC@.microsoft.com...
I just got to know that the RAM is going to be increased to 6 GB on the
target server before it goes into Production. How does it affect the /PAE or
the /3GB switch in boot.ini file and the AWE enabled / disabled on SQL
Server?
Thanks in advance.
"ronnie" wrote:
[vbcol=seagreen]
> Thanks a lot Tom for the quick response. Can you please explain the reason
> why you want to have that change so that I can have a better understanding
> of
> what's going on? Also, the target server has a Windows 2003 server in
> comparison to the current server that is running on Windows 2000 server.
> What would happen if the AWE is enabled? Thanks in advance.
> "Tom Moreau" wrote:
|||Hi Tom,
I have put in both the /PAE and /3GB switches as you suggested. Now the SQL
Server is only using 3GB of memory. I want the SQL server to use 5 GB out of
6 GB of memory and leave the 1 GB memory for the OS. How can I achieve this?
Thanks in advance.
"Tom Moreau" wrote:
> That's different. In That case, I'd turn on both - once you get the extra
> memory. Above 12GB, remove the /3GB switch:
> [url]http://groups.google.ca/group/microsoft.public.sqlserver.clustering/browse_thread/thread/5eef281ae5d7ff59/0e83b85ef5b91530?hl=en&lnk=st&q=pae+3gb+hiten#0e83 b85ef5b91530[/url]
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "ronnie" <ronnie@.discussions.microsoft.com> wrote in message
> news:051D8B41-A6F2-49FA-93A4-4DE697956DEC@.microsoft.com...
> I just got to know that the RAM is going to be increased to 6 GB on the
> target server before it goes into Production. How does it affect the /PAE or
> the /3GB switch in boot.ini file and the AWE enabled / disabled on SQL
> Server?
> Thanks in advance.
> "ronnie" wrote:
>
>
|||Earlier, you said "the RAM is going to be increased to 6 GB". So does the
server have that much physical RAM now? If not, then wait until you have it
before turning on AWE.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"ronnie" <ronnie@.discussions.microsoft.com> wrote in message
news:B23DEDE0-4CE2-4119-BC6F-BB632C5FAE15@.microsoft.com...
Hi Tom,
I have put in both the /PAE and /3GB switches as you suggested. Now the SQL
Server is only using 3GB of memory. I want the SQL server to use 5 GB out of
6 GB of memory and leave the 1 GB memory for the OS. How can I achieve this?
Thanks in advance.
"Tom Moreau" wrote:
> That's different. In That case, I'd turn on both - once you get the extra
> memory. Above 12GB, remove the /3GB switch:
>
[url]http://groups.google.ca/group/microsoft.public.sqlserver.clustering/browse_thread/thread/5eef281ae5d7ff59/0e83b85ef5b91530?hl=en&lnk=st&q=pae+3gb+hiten#0e83 b85ef5b91530[/url]
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "ronnie" <ronnie@.discussions.microsoft.com> wrote in message
> news:051D8B41-A6F2-49FA-93A4-4DE697956DEC@.microsoft.com...
> I just got to know that the RAM is going to be increased to 6 GB on the
> target server before it goes into Production. How does it affect the /PAE
or[vbcol=seagreen]
> the /3GB switch in boot.ini file and the AWE enabled / disabled on SQL
> Server?
> Thanks in advance.
> "ronnie" wrote:
reason[vbcol=seagreen]
understanding[vbcol=seagreen]
memory[vbcol=seagreen]
on
>
|||The server now has 6 GB of RAM. So do I enable AWE and set maximum server
memory to
5 GB with sp_configure? I will leave the /PAE switch in the boot.ini file
and take out the
/3GB switch from it.
"Tom Moreau" wrote:
> Earlier, you said "the RAM is going to be increased to 6 GB". So does the
> server have that much physical RAM now? If not, then wait until you have it
> before turning on AWE.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "ronnie" <ronnie@.discussions.microsoft.com> wrote in message
> news:B23DEDE0-4CE2-4119-BC6F-BB632C5FAE15@.microsoft.com...
> Hi Tom,
> I have put in both the /PAE and /3GB switches as you suggested. Now the SQL
> Server is only using 3GB of memory. I want the SQL server to use 5 GB out of
> 6 GB of memory and leave the 1 GB memory for the OS. How can I achieve this?
> Thanks in advance.
> "Tom Moreau" wrote:
> [url]http://groups.google.ca/group/microsoft.public.sqlserver.clustering/browse_thread/thread/5eef281ae5d7ff59/0e83b85ef5b91530?hl=en&lnk=st&q=pae+3gb+hiten#0e83 b85ef5b91530[/url]
> or
> reason
> understanding
> memory
> on
>
>
|||Yes. Use:
sp_configure 'awe', 1
go
reconfigure with override
go
sp_configure 'max server memory', 5120
go
reconfigure with override
go
Then, stop and start SQL Server.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"ronnie" <ronnie@.discussions.microsoft.com> wrote in message
news:A461C42F-6D8B-4121-A127-7C568F5ECF93@.microsoft.com...
The server now has 6 GB of RAM. So do I enable AWE and set maximum server
memory to
5 GB with sp_configure? I will leave the /PAE switch in the boot.ini file
and take out the
/3GB switch from it.
"Tom Moreau" wrote:
> Earlier, you said "the RAM is going to be increased to 6 GB". So does the
> server have that much physical RAM now? If not, then wait until you have
it
> before turning on AWE.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "ronnie" <ronnie@.discussions.microsoft.com> wrote in message
> news:B23DEDE0-4CE2-4119-BC6F-BB632C5FAE15@.microsoft.com...
> Hi Tom,
> I have put in both the /PAE and /3GB switches as you suggested. Now the
SQL
> Server is only using 3GB of memory. I want the SQL server to use 5 GB out
of
> 6 GB of memory and leave the 1 GB memory for the OS. How can I achieve
this?[vbcol=seagreen]
> Thanks in advance.
> "Tom Moreau" wrote:
extra
>
[url]http://groups.google.ca/group/microsoft.public.sqlserver.clustering/browse_thread/thread/5eef281ae5d7ff59/0e83b85ef5b91530?hl=en&lnk=st&q=pae+3gb+hiten#0e83 b85ef5b91530[/url][vbcol=seagreen]
/PAE[vbcol=seagreen]
> or
> reason
> understanding
server.[vbcol=seagreen]
Server
> memory
> on
>
>
I am moving the default instance of a SQL Server 2000 to a ESX Server
running on VMWare. Below are the specifications:
Current Server:
SQL Server 2000 Enterprise Edition Version 8.00.2187
Windows Advanced Server 2000 SP4
Intel Pentium III 1400 MHz
4 GB RAM
/3 GB switch enabled in boot.ini
AWE not enabled and SQL Server using a maximum of 3 GB of RAM.
Target Server:
SQL Server 2000 Enterprise Edition Version 8.00.2187
Windows Server 2003 Enterprise Edition SP2
Intel Xeon X7350 2.93 GHz
3.75 GB RAM
/PAE 3 GB switch enabled in boot.ini
AWE not enabled
The target server is running on VMWare and we will be adding more memory to
it if it is needed in the future. What AWE setting should I be using on the
target machine?
Your target BOOT.INI has the /PAE switch enabled. Remove it and use /3GB.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"ronnie" <ronnie@.discussions.microsoft.com> wrote in message
news:C14D97C4-6190-4632-9A7B-D619F992B5CB@.microsoft.com...
Hi,
I am moving the default instance of a SQL Server 2000 to a ESX Server
running on VMWare. Below are the specifications:
Current Server:
SQL Server 2000 Enterprise Edition Version 8.00.2187
Windows Advanced Server 2000 SP4
Intel Pentium III 1400 MHz
4 GB RAM
/3 GB switch enabled in boot.ini
AWE not enabled and SQL Server using a maximum of 3 GB of RAM.
Target Server:
SQL Server 2000 Enterprise Edition Version 8.00.2187
Windows Server 2003 Enterprise Edition SP2
Intel Xeon X7350 2.93 GHz
3.75 GB RAM
/PAE 3 GB switch enabled in boot.ini
AWE not enabled
The target server is running on VMWare and we will be adding more memory to
it if it is needed in the future. What AWE setting should I be using on the
target machine?
|||Thanks a lot Tom for the quick response. Can you please explain the reason
why you want to have that change so that I can have a better understanding of
what's going on? Also, the target server has a Windows 2003 server in
comparison to the current server that is running on Windows 2000 server.
What would happen if the AWE is enabled? Thanks in advance.
"Tom Moreau" wrote:
> Your target BOOT.INI has the /PAE switch enabled. Remove it and use /3GB.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "ronnie" <ronnie@.discussions.microsoft.com> wrote in message
> news:C14D97C4-6190-4632-9A7B-D619F992B5CB@.microsoft.com...
> Hi,
> I am moving the default instance of a SQL Server 2000 to a ESX Server
> running on VMWare. Below are the specifications:
> Current Server:
> SQL Server 2000 Enterprise Edition Version 8.00.2187
> Windows Advanced Server 2000 SP4
> Intel Pentium III 1400 MHz
> 4 GB RAM
> /3 GB switch enabled in boot.ini
> AWE not enabled and SQL Server using a maximum of 3 GB of RAM.
>
> Target Server:
> SQL Server 2000 Enterprise Edition Version 8.00.2187
> Windows Server 2003 Enterprise Edition SP2
> Intel Xeon X7350 2.93 GHz
> 3.75 GB RAM
> /PAE 3 GB switch enabled in boot.ini
> AWE not enabled
> The target server is running on VMWare and we will be adding more memory to
> it if it is needed in the future. What AWE setting should I be using on the
> target machine?
>
|||What was referring to was this:
"/PAE 3 GB switch enabled in boot.ini"
It is self-contradictory. /PAE is not 3GB.
Also, you don't have enough memory to take advantage of AWE.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"ronnie" <ronnie@.discussions.microsoft.com> wrote in message
news:FCBE95A4-E3E6-4FCE-9548-090B812D9EB6@.microsoft.com...
Thanks a lot Tom for the quick response. Can you please explain the reason
why you want to have that change so that I can have a better understanding
of
what's going on? Also, the target server has a Windows 2003 server in
comparison to the current server that is running on Windows 2000 server.
What would happen if the AWE is enabled? Thanks in advance.
"Tom Moreau" wrote:
> Your target BOOT.INI has the /PAE switch enabled. Remove it and use /3GB.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "ronnie" <ronnie@.discussions.microsoft.com> wrote in message
> news:C14D97C4-6190-4632-9A7B-D619F992B5CB@.microsoft.com...
> Hi,
> I am moving the default instance of a SQL Server 2000 to a ESX Server
> running on VMWare. Below are the specifications:
> Current Server:
> SQL Server 2000 Enterprise Edition Version 8.00.2187
> Windows Advanced Server 2000 SP4
> Intel Pentium III 1400 MHz
> 4 GB RAM
> /3 GB switch enabled in boot.ini
> AWE not enabled and SQL Server using a maximum of 3 GB of RAM.
>
> Target Server:
> SQL Server 2000 Enterprise Edition Version 8.00.2187
> Windows Server 2003 Enterprise Edition SP2
> Intel Xeon X7350 2.93 GHz
> 3.75 GB RAM
> /PAE 3 GB switch enabled in boot.ini
> AWE not enabled
> The target server is running on VMWare and we will be adding more memory
> to
> it if it is needed in the future. What AWE setting should I be using on
> the
> target machine?
>
|||I just got to know that the RAM is going to be increased to 6 GB on the
target server before it goes into Production. How does it affect the /PAE or
the /3GB switch in boot.ini file and the AWE enabled / disabled on SQL Server?
Thanks in advance.
"ronnie" wrote:
[vbcol=seagreen]
> Thanks a lot Tom for the quick response. Can you please explain the reason
> why you want to have that change so that I can have a better understanding of
> what's going on? Also, the target server has a Windows 2003 server in
> comparison to the current server that is running on Windows 2000 server.
> What would happen if the AWE is enabled? Thanks in advance.
> "Tom Moreau" wrote:
|||That's different. In That case, I'd turn on both - once you get the extra
memory. Above 12GB, remove the /3GB switch:
[url]http://groups.google.ca/group/microsoft.public.sqlserver.clustering/browse_thread/thread/5eef281ae5d7ff59/0e83b85ef5b91530?hl=en&lnk=st&q=pae+3gb+hiten#0e83 b85ef5b91530[/url]
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"ronnie" <ronnie@.discussions.microsoft.com> wrote in message
news:051D8B41-A6F2-49FA-93A4-4DE697956DEC@.microsoft.com...
I just got to know that the RAM is going to be increased to 6 GB on the
target server before it goes into Production. How does it affect the /PAE or
the /3GB switch in boot.ini file and the AWE enabled / disabled on SQL
Server?
Thanks in advance.
"ronnie" wrote:
[vbcol=seagreen]
> Thanks a lot Tom for the quick response. Can you please explain the reason
> why you want to have that change so that I can have a better understanding
> of
> what's going on? Also, the target server has a Windows 2003 server in
> comparison to the current server that is running on Windows 2000 server.
> What would happen if the AWE is enabled? Thanks in advance.
> "Tom Moreau" wrote:
|||Hi Tom,
I have put in both the /PAE and /3GB switches as you suggested. Now the SQL
Server is only using 3GB of memory. I want the SQL server to use 5 GB out of
6 GB of memory and leave the 1 GB memory for the OS. How can I achieve this?
Thanks in advance.
"Tom Moreau" wrote:
> That's different. In That case, I'd turn on both - once you get the extra
> memory. Above 12GB, remove the /3GB switch:
> [url]http://groups.google.ca/group/microsoft.public.sqlserver.clustering/browse_thread/thread/5eef281ae5d7ff59/0e83b85ef5b91530?hl=en&lnk=st&q=pae+3gb+hiten#0e83 b85ef5b91530[/url]
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "ronnie" <ronnie@.discussions.microsoft.com> wrote in message
> news:051D8B41-A6F2-49FA-93A4-4DE697956DEC@.microsoft.com...
> I just got to know that the RAM is going to be increased to 6 GB on the
> target server before it goes into Production. How does it affect the /PAE or
> the /3GB switch in boot.ini file and the AWE enabled / disabled on SQL
> Server?
> Thanks in advance.
> "ronnie" wrote:
>
>
|||Earlier, you said "the RAM is going to be increased to 6 GB". So does the
server have that much physical RAM now? If not, then wait until you have it
before turning on AWE.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"ronnie" <ronnie@.discussions.microsoft.com> wrote in message
news:B23DEDE0-4CE2-4119-BC6F-BB632C5FAE15@.microsoft.com...
Hi Tom,
I have put in both the /PAE and /3GB switches as you suggested. Now the SQL
Server is only using 3GB of memory. I want the SQL server to use 5 GB out of
6 GB of memory and leave the 1 GB memory for the OS. How can I achieve this?
Thanks in advance.
"Tom Moreau" wrote:
> That's different. In That case, I'd turn on both - once you get the extra
> memory. Above 12GB, remove the /3GB switch:
>
[url]http://groups.google.ca/group/microsoft.public.sqlserver.clustering/browse_thread/thread/5eef281ae5d7ff59/0e83b85ef5b91530?hl=en&lnk=st&q=pae+3gb+hiten#0e83 b85ef5b91530[/url]
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "ronnie" <ronnie@.discussions.microsoft.com> wrote in message
> news:051D8B41-A6F2-49FA-93A4-4DE697956DEC@.microsoft.com...
> I just got to know that the RAM is going to be increased to 6 GB on the
> target server before it goes into Production. How does it affect the /PAE
or[vbcol=seagreen]
> the /3GB switch in boot.ini file and the AWE enabled / disabled on SQL
> Server?
> Thanks in advance.
> "ronnie" wrote:
reason[vbcol=seagreen]
understanding[vbcol=seagreen]
memory[vbcol=seagreen]
on
>
|||The server now has 6 GB of RAM. So do I enable AWE and set maximum server
memory to
5 GB with sp_configure? I will leave the /PAE switch in the boot.ini file
and take out the
/3GB switch from it.
"Tom Moreau" wrote:
> Earlier, you said "the RAM is going to be increased to 6 GB". So does the
> server have that much physical RAM now? If not, then wait until you have it
> before turning on AWE.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "ronnie" <ronnie@.discussions.microsoft.com> wrote in message
> news:B23DEDE0-4CE2-4119-BC6F-BB632C5FAE15@.microsoft.com...
> Hi Tom,
> I have put in both the /PAE and /3GB switches as you suggested. Now the SQL
> Server is only using 3GB of memory. I want the SQL server to use 5 GB out of
> 6 GB of memory and leave the 1 GB memory for the OS. How can I achieve this?
> Thanks in advance.
> "Tom Moreau" wrote:
> [url]http://groups.google.ca/group/microsoft.public.sqlserver.clustering/browse_thread/thread/5eef281ae5d7ff59/0e83b85ef5b91530?hl=en&lnk=st&q=pae+3gb+hiten#0e83 b85ef5b91530[/url]
> or
> reason
> understanding
> memory
> on
>
>
|||Yes. Use:
sp_configure 'awe', 1
go
reconfigure with override
go
sp_configure 'max server memory', 5120
go
reconfigure with override
go
Then, stop and start SQL Server.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"ronnie" <ronnie@.discussions.microsoft.com> wrote in message
news:A461C42F-6D8B-4121-A127-7C568F5ECF93@.microsoft.com...
The server now has 6 GB of RAM. So do I enable AWE and set maximum server
memory to
5 GB with sp_configure? I will leave the /PAE switch in the boot.ini file
and take out the
/3GB switch from it.
"Tom Moreau" wrote:
> Earlier, you said "the RAM is going to be increased to 6 GB". So does the
> server have that much physical RAM now? If not, then wait until you have
it
> before turning on AWE.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "ronnie" <ronnie@.discussions.microsoft.com> wrote in message
> news:B23DEDE0-4CE2-4119-BC6F-BB632C5FAE15@.microsoft.com...
> Hi Tom,
> I have put in both the /PAE and /3GB switches as you suggested. Now the
SQL
> Server is only using 3GB of memory. I want the SQL server to use 5 GB out
of
> 6 GB of memory and leave the 1 GB memory for the OS. How can I achieve
this?[vbcol=seagreen]
> Thanks in advance.
> "Tom Moreau" wrote:
extra
>
[url]http://groups.google.ca/group/microsoft.public.sqlserver.clustering/browse_thread/thread/5eef281ae5d7ff59/0e83b85ef5b91530?hl=en&lnk=st&q=pae+3gb+hiten#0e83 b85ef5b91530[/url][vbcol=seagreen]
/PAE[vbcol=seagreen]
> or
> reason
> understanding
server.[vbcol=seagreen]
Server
> memory
> on
>
>
Subscribe to:
Posts (Atom)