Moving Log Files: virtual

Showing posts with label virtual. Show all posts

Friday, March 30, 2012

Moving virtual server and instance names to a new server

We currently have a (2) node active/active cluster with each node ideally
hosting (2) virtual servers and their instances. We want to split the
cluster into (2) active/passive clusters and move what normally resides on a
given node to it's own cluster. Here is the catch. We have cross
server/instances queries/procedures and Access database/queries with the
Virtual Server and instance name hard coded, and creating new names isn't
really an viable option.
Here is the current setup:
Current Cluster:
NODE01
VSQL1\sqlsrv01
VSQL1\sqlsrv02
NODE02
VSQL1\sqlsrv03
VSQL1\sqlsrv04
And here is the proposed setup::
New Cluster 1:
NODE01 - active
VSQL1\sqlsrv01
VSQL1\sqlsrv02
NODE02 - inactive
New Cluster 2:
NODE01 - active
VSQL1\sqlsrv03
VSQL1\sqlsrv04
NODE02 - inactive
Can we create the servers in a different domain, moving them to our
production domain when testing has been completed? And if so, how do we
handle the fact that the VSQLx and named instances already exists in Active
Directory? Can the old server just be turned off, the new one brought up and
added to the domain by resetting the current domain accounts and re-joining?
Of course. Does anyone have a good solution, I'm all ears. Thanks
> Here is the current setup:
> Current Cluster:
> NODE01
> VSQL1\sqlsrv01
> VSQL1\sqlsrv02
> NODE02
> VSQL1\sqlsrv03
> VSQL1\sqlsrv04
That can't be your current setup. Your current setup is probably more like:
NODE01
VSQL01\sqlsrv01
VSQL02\sqlsrv02
NODE02
VSQL03\sqlsrv03
VSQL04\sqlsrv04
I'd probably just do a switchover with the current cluster. First, get the
necessary database files to a staging server. Then, remove the cluster from
the network. But keep it as your rollback plan. Create two new clusters and
install SQL instances as follows:
New Cluster 1:
NODE01 - active
VSQL01\sqlsrv01
VSQL02\sqlsrv02
NODE02 - inactive
New Cluster 2:
NODE01 - active
VSQL03\sqlsrv03
VSQL04\sqlsrv04
And finally get the database files from the staging server to their
respective new servers.
Linchi
"randall_dh" wrote:

> We currently have a (2) node active/active cluster with each node ideally
> hosting (2) virtual servers and their instances. We want to split the
> cluster into (2) active/passive clusters and move what normally resides on a
> given node to it's own cluster. Here is the catch. We have cross
> server/instances queries/procedures and Access database/queries with the
> Virtual Server and instance name hard coded, and creating new names isn't
> really an viable option.
> Here is the current setup:
> Current Cluster:
> NODE01
> VSQL1\sqlsrv01
> VSQL1\sqlsrv02
> NODE02
> VSQL1\sqlsrv03
> VSQL1\sqlsrv04
>
> And here is the proposed setup::
> New Cluster 1:
> NODE01 - active
> VSQL1\sqlsrv01
> VSQL1\sqlsrv02
> NODE02 - inactive
> New Cluster 2:
> NODE01 - active
> VSQL1\sqlsrv03
> VSQL1\sqlsrv04
> NODE02 - inactive
> Can we create the servers in a different domain, moving them to our
> production domain when testing has been completed? And if so, how do we
> handle the fact that the VSQLx and named instances already exists in Active
> Directory? Can the old server just be turned off, the new one brought up and
> added to the domain by resetting the current domain accounts and re-joining?
> Of course. Does anyone have a good solution, I'm all ears. Thanks
|||Yes, you are correct regarding the Virtual Server naming (careless cutting
and pasting on my part). Ideally, we would like to test the new cluster for
several days prior to bringing it live. My main concern is that the reusing
of the names doesn't cause a problem. Am I correct in my assumtions that AD
isn't involved in the virtual server or instance naming and that the only
network ties are through the DNS entries?
ALso, would you expect that any issues with restoring the master and msdb to
the new cluster instances (any references to the old nodes etc...)?
Thank you.
"Linchi Shea" wrote:
[vbcol=seagreen]
> That can't be your current setup. Your current setup is probably more like:
> NODE01
> VSQL01\sqlsrv01
> VSQL02\sqlsrv02
> NODE02
> VSQL03\sqlsrv03
> VSQL04\sqlsrv04
> I'd probably just do a switchover with the current cluster. First, get the
> necessary database files to a staging server. Then, remove the cluster from
> the network. But keep it as your rollback plan. Create two new clusters and
> install SQL instances as follows:
> New Cluster 1:
> NODE01 - active
> VSQL01\sqlsrv01
> VSQL02\sqlsrv02
> NODE02 - inactive
> New Cluster 2:
> NODE01 - active
> VSQL03\sqlsrv03
> VSQL04\sqlsrv04
> And finally get the database files from the staging server to their
> respective new servers.
> Linchi
> "randall_dh" 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:
> 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?
> >
> >|||That's different. In That case, I'd turn on both - once you get the extra
memory. Above 12GB, remove the /3GB switch:
http://groups.google.ca/group/microsoft.public.sqlserver.clustering/browse_thread/thread/5eef281ae5d7ff59/0e83b85ef5b91530?hl=en&lnk=st&q=pae+3gb+hiten#0e83b85ef5b91530
--
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:
> 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?
> >
> >|||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:
> http://groups.google.ca/group/microsoft.public.sqlserver.clustering/browse_thread/thread/5eef281ae5d7ff59/0e83b85ef5b91530?hl=en&lnk=st&q=pae+3gb+hiten#0e83b85ef5b91530
> --
> 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:
> > 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?
> > >
> > >
>|||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:
>
http://groups.google.ca/group/microsoft.public.sqlserver.clustering/browse_thread/thread/5eef281ae5d7ff59/0e83b85ef5b91530?hl=en&lnk=st&q=pae+3gb+hiten#0e83b85ef5b91530
> --
> 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:
> > 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?
> > >
> > >
>|||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:
> > That's different. In That case, I'd turn on both - once you get the extra
> > memory. Above 12GB, remove the /3GB switch:
> >
> >
> http://groups.google.ca/group/microsoft.public.sqlserver.clustering/browse_thread/thread/5eef281ae5d7ff59/0e83b85ef5b91530?hl=en&lnk=st&q=pae+3gb+hiten#0e83b85ef5b91530
> >
> > --
> > 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:
> >
> > > 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?
> > > >
> > > >
> >
> >
>
>|||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?
> 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:
> >
> >
>
http://groups.google.ca/group/microsoft.public.sqlserver.clustering/browse_thread/thread/5eef281ae5d7ff59/0e83b85ef5b91530?hl=en&lnk=st&q=pae+3gb+hiten#0e83b85ef5b91530
> >
> > --
> > 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:
> >
> > > 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?
> > > >
> > > >
> >
> >
>
>|||Thanks for the quick response, Tom. I have made the changes as you suggested
and
rebooted the server. What I have noticed now in the Task Manager is that
sqlservr.exe is
only using about 120 MB of the 6 GB memory while the CPU usage has gone to
almost
100 % whilst earlier with the /3GB switch in place the memory used by
sqlservr.exe
was almost 2700 MB and the CPU usage was below 10 %.
I haven't heard any user complaints about the system being slow but I am
very puzzled
by this SQL Server behavior.
Current Server configuration:
SQL Server 2000 Enterprise Edition Version 8.00.2187
Windows Server 2003 Enterprise Edition SP2
Intel Xeon X7350 2.93 GHz
6 GB RAM
/PAE enabled in boot.ini
AWE enabled and max server memory is 5GB
(Earlier it had the /3GB switch in boot.ini and AWE disabled)
Old Server configuration:
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.
"Tom Moreau" wrote:
> 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?
> >
> > 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:
> > >
> > >
> >
> http://groups.google.ca/group/microsoft.public.sqlserver.clustering/browse_thread/thread/5eef281ae5d7ff59/0e83b85ef5b91530?hl=en&lnk=st&q=pae+3gb+hiten#0e83b85ef5b91530
> > >
> > > --
> > > 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:
> > >
> > > > 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?
> > > > >
> > > > >
> > >
> > >
> >
> >
> >
>
>|||Task Mgr is not reliable when it comes to AWE. What you want is to use Perf
Mon and there is a SQL Server object - Memory Manager. It has a counter
called Total Server Memory (KB) that reports what SQL Server is really
using.
Also, you can try using the /3GB switch in conjunction with the /PAE switch.
Once you get to 12GB, then go with /PAE only.
High CPU usage can result from the fact that there is no longer a memory or
disk bottleneck and the CPU does not have to wait for data to process.
--
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:C697319B-4F09-4DCD-AD28-2E4BF51EDA41@.microsoft.com...
Thanks for the quick response, Tom. I have made the changes as you suggested
and
rebooted the server. What I have noticed now in the Task Manager is that
sqlservr.exe is
only using about 120 MB of the 6 GB memory while the CPU usage has gone to
almost
100 % whilst earlier with the /3GB switch in place the memory used by
sqlservr.exe
was almost 2700 MB and the CPU usage was below 10 %.
I haven't heard any user complaints about the system being slow but I am
very puzzled
by this SQL Server behavior.
Current Server configuration:
SQL Server 2000 Enterprise Edition Version 8.00.2187
Windows Server 2003 Enterprise Edition SP2
Intel Xeon X7350 2.93 GHz
6 GB RAM
/PAE enabled in boot.ini
AWE enabled and max server memory is 5GB
(Earlier it had the /3GB switch in boot.ini and AWE disabled)
Old Server configuration:
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.
"Tom Moreau" wrote:
> 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?
> >
> > 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:
> > >
> > >
> >
>
http://groups.google.ca/group/microsoft.public.sqlserver.clustering/browse_thread/thread/5eef281ae5d7ff59/0e83b85ef5b91530?hl=en&lnk=st&q=pae+3gb+hiten#0e83b85ef5b91530
> > >
> > > --
> > > 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:
> > >
> > > > 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?
> > > > >
> > > > >
> > >
> > >
> >
> >
> >
>
>

Friday, March 9, 2012

Moving Reporting Services Virtual Directories

Hi
I have followed the aritcle
http://www.sqljunkies.com/HowTo/525B575A-7F61-483A-AC8F-FEC700C34674.scuk to
a tee, but when i run the new web site i get a page not found for
http://localhost/reports/home.aspx
If i run it on the default web server everything is fine.
I tried testing it by placing an html file in the report manager folder eg
test.html and http://localhost/reports/test.html worked fine.
Has anyone successfully completed this operation? I can access
http://localhost/reportserver/ ok
I'm guessing it's a permissions/execution problem.
Any ideas?
Cheers
JonnyIt's okay
I've sorted it. I hadn't got the ASP.NET server extension enabled in IIS.
Not sure how it worked at all?
Jonny
"Jonny" <jonny@.nospam.jonnywilk.co.uk> wrote in message
news:d8crpk$6d0$1$8300dec7@.news.demon.co.uk...
> Hi
> I have followed the aritcle
> http://www.sqljunkies.com/HowTo/525B575A-7F61-483A-AC8F-FEC700C34674.scuk
> to a tee, but when i run the new web site i get a page not found for
> http://localhost/reports/home.aspx
> If i run it on the default web server everything is fine.
> I tried testing it by placing an html file in the report manager folder eg
> test.html and http://localhost/reports/test.html worked fine.
> Has anyone successfully completed this operation? I can access
> http://localhost/reportserver/ ok
> I'm guessing it's a permissions/execution problem.
> Any ideas?
> Cheers
> Jonny
>

Moving report server to new virtual server

Hi
I've about had it trying to mix WSS and report server so I'd like to create
a new virtual server and put report server on it. Do I have to reinstall
the whole thing or can I just move it?
TIA
BillYou can move them. The following article tells you how:
http://www.sqljunkies.com/HowTo/525B575A-7F61-483A-AC8F-FEC700C34674.scuk
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
<sutphinwb@.nospam.nospam> wrote in message
news:OjOS%23dHEFHA.3580@.TK2MSFTNGP10.phx.gbl...
> Hi
> I've about had it trying to mix WSS and report server so I'd like to
> create a new virtual server and put report server on it. Do I have to
> reinstall the whole thing or can I just move it?
> TIA
> Bill
>

Friday, March 30, 2012

Moving virtual server and instance names to a new server

Monday, March 19, 2012

Moving SQL Server 2000 to a new Virtual Server

Moving SQL Server 2000 to a new Virtual Server

Friday, March 9, 2012

Moving Reporting Services Virtual Directories

Moving report server to new virtual server

Moving Log Files

Blog Archive

About Me