Can any help me addition of article in runnning merge replication in MSSQL SERVER 2000 with SP3.
Any step by step help is realy great for me.
Thanks
R.MallSp_addMergeArticle is one system procedure, which may be workable, but I don't know detail step by step methods for same.
Showing posts with label sp3. Show all posts
Showing posts with label sp3. Show all posts
Sunday, March 25, 2012
Tuesday, March 6, 2012
Adding New Column & updating bulk data in merge replication
Hi,
We have about 50 databases (SQL Server 2000, SP3) which are merge
replicated. We merge replicate about 100 odd tables in each of these
database. We need to add couple of columns in one of our major transaction
table where most insert/updates are being done. This table presently on
average has 5 lacs records.
During testing, we noticed that it takes about 60-80 minutes to add a
column in this table. Considering the # of database we have where the change
need to implemented, we will not be able to plan the upgrade without
production downtime. For upgrade 50 database it will take about 50 hours.
What are the options available in Replication so this can be done quickly
w/o any production downtime.
Adding to this, in one of the column we have added to the transaction table
, we need to update a new value. On testing we found that for 5 lacs records
it takes anyway between 2-3 hours. This takes roughly another 75 hours for
us to do this update after adding the new column in the table. How can this
be speeded up ?
thanks,
Soura
What's a lacs?
Basically there is probably no good solution for this. I would look at doing
a sync. Then creating my publication and then backing it up and restoring it
to all the subscribers and doing a no sync subscription, or I would look at
regenerating a snapshot and distributing it after you have made the column
change.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"SouRa" <SouRa@.discussions.microsoft.com> wrote in message
news:A19172BF-E8AC-4BB7-9FED-87EEC5353D89@.microsoft.com...
> Hi,
> We have about 50 databases (SQL Server 2000, SP3) which are merge
> replicated. We merge replicate about 100 odd tables in each of these
> database. We need to add couple of columns in one of our major transaction
> table where most insert/updates are being done. This table presently on
> average has 5 lacs records.
> During testing, we noticed that it takes about 60-80 minutes to add a
> column in this table. Considering the # of database we have where the
> change
> need to implemented, we will not be able to plan the upgrade without
> production downtime. For upgrade 50 database it will take about 50 hours.
> What are the options available in Replication so this can be done quickly
> w/o any production downtime.
> Adding to this, in one of the column we have added to the transaction
> table
> , we need to update a new value. On testing we found that for 5 lacs
> records
> it takes anyway between 2-3 hours. This takes roughly another 75 hours for
> us to do this update after adding the new column in the table. How can
> this
> be speeded up ?
> thanks,
> Soura
|||5 lacs is 500 K or 500 thousand i.e 500,000
lacs is primarily an indian unit of measurment. 1 lac is 0.1 million
"Hilary Cotter" wrote:
> What's a lacs?
> Basically there is probably no good solution for this. I would look at doing
> a sync. Then creating my publication and then backing it up and restoring it
> to all the subscribers and doing a no sync subscription, or I would look at
> regenerating a snapshot and distributing it after you have made the column
> change.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "SouRa" <SouRa@.discussions.microsoft.com> wrote in message
> news:A19172BF-E8AC-4BB7-9FED-87EEC5353D89@.microsoft.com...
>
>
We have about 50 databases (SQL Server 2000, SP3) which are merge
replicated. We merge replicate about 100 odd tables in each of these
database. We need to add couple of columns in one of our major transaction
table where most insert/updates are being done. This table presently on
average has 5 lacs records.
During testing, we noticed that it takes about 60-80 minutes to add a
column in this table. Considering the # of database we have where the change
need to implemented, we will not be able to plan the upgrade without
production downtime. For upgrade 50 database it will take about 50 hours.
What are the options available in Replication so this can be done quickly
w/o any production downtime.
Adding to this, in one of the column we have added to the transaction table
, we need to update a new value. On testing we found that for 5 lacs records
it takes anyway between 2-3 hours. This takes roughly another 75 hours for
us to do this update after adding the new column in the table. How can this
be speeded up ?
thanks,
Soura
What's a lacs?
Basically there is probably no good solution for this. I would look at doing
a sync. Then creating my publication and then backing it up and restoring it
to all the subscribers and doing a no sync subscription, or I would look at
regenerating a snapshot and distributing it after you have made the column
change.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"SouRa" <SouRa@.discussions.microsoft.com> wrote in message
news:A19172BF-E8AC-4BB7-9FED-87EEC5353D89@.microsoft.com...
> Hi,
> We have about 50 databases (SQL Server 2000, SP3) which are merge
> replicated. We merge replicate about 100 odd tables in each of these
> database. We need to add couple of columns in one of our major transaction
> table where most insert/updates are being done. This table presently on
> average has 5 lacs records.
> During testing, we noticed that it takes about 60-80 minutes to add a
> column in this table. Considering the # of database we have where the
> change
> need to implemented, we will not be able to plan the upgrade without
> production downtime. For upgrade 50 database it will take about 50 hours.
> What are the options available in Replication so this can be done quickly
> w/o any production downtime.
> Adding to this, in one of the column we have added to the transaction
> table
> , we need to update a new value. On testing we found that for 5 lacs
> records
> it takes anyway between 2-3 hours. This takes roughly another 75 hours for
> us to do this update after adding the new column in the table. How can
> this
> be speeded up ?
> thanks,
> Soura
|||5 lacs is 500 K or 500 thousand i.e 500,000
lacs is primarily an indian unit of measurment. 1 lac is 0.1 million
"Hilary Cotter" wrote:
> What's a lacs?
> Basically there is probably no good solution for this. I would look at doing
> a sync. Then creating my publication and then backing it up and restoring it
> to all the subscribers and doing a no sync subscription, or I would look at
> regenerating a snapshot and distributing it after you have made the column
> change.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "SouRa" <SouRa@.discussions.microsoft.com> wrote in message
> news:A19172BF-E8AC-4BB7-9FED-87EEC5353D89@.microsoft.com...
>
>
Adding more RAM for MS SQL Server 2000
Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
hand. The SQL Server is configured for dynamic memory allocation. The machine
had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
more gigabytes of RAM into the machine and I want to allow the SQL Server to
use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling it to
use the additional gigabyte of RAM?
Many thanks,
Oskar
No. All you have to do is add the /3GB switch to boot.ini and reboot.
If you wanted to address > 4GB of RAM then you would have to start
playing with AWE but <= 4GB is addressable with normal windows memory
addressing & therefore normal MSSQL dynamic memory management.
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Oskar wrote:
>Hi
>I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
>hand. The SQL Server is configured for dynamic memory allocation. The machine
>had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
>more gigabytes of RAM into the machine and I want to allow the SQL Server to
>use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
>boot.ini).
>Do I also have to reconfigure any SQL Server parameters after enabling it to
>use the additional gigabyte of RAM?
>--
>Many thanks,
>Oskar
>
>
|||Hi,
This will work out if your SQL server 2000 edition is Enterprise or Developer. Standard edition can support a maximum of 2 GB only.
Thanks
Hari
SQL Server MVP
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message news:OvpsIwbZFHA.4088@.TK2MSFTNGP15.phx.gbl...
No. All you have to do is add the /3GB switch to boot.ini and reboot. If you wanted to address > 4GB of RAM then you would have to start playing with AWE but <= 4GB is addressable with normal windows memory addressing & therefore normal MSSQL dynamic memory management.
mike hodgson | database administrator | mallesons stephen jaques
T +61 (2) 9296 3668 | F +61 (2) 9296 3885 | M +61 (408) 675 907
E mailto:mike.hodgson@.mallesons.nospam.com | W http://www.mallesons.com
Oskar wrote:
Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
hand. The SQL Server is configured for dynamic memory allocation. The machine
had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
more gigabytes of RAM into the machine and I want to allow the SQL Server to
use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling it to
use the additional gigabyte of RAM?
Many thanks,
Oskar
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
hand. The SQL Server is configured for dynamic memory allocation. The machine
had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
more gigabytes of RAM into the machine and I want to allow the SQL Server to
use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling it to
use the additional gigabyte of RAM?
Many thanks,
Oskar
No. All you have to do is add the /3GB switch to boot.ini and reboot.
If you wanted to address > 4GB of RAM then you would have to start
playing with AWE but <= 4GB is addressable with normal windows memory
addressing & therefore normal MSSQL dynamic memory management.
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Oskar wrote:
>Hi
>I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
>hand. The SQL Server is configured for dynamic memory allocation. The machine
>had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
>more gigabytes of RAM into the machine and I want to allow the SQL Server to
>use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
>boot.ini).
>Do I also have to reconfigure any SQL Server parameters after enabling it to
>use the additional gigabyte of RAM?
>--
>Many thanks,
>Oskar
>
>
|||Hi,
This will work out if your SQL server 2000 edition is Enterprise or Developer. Standard edition can support a maximum of 2 GB only.
Thanks
Hari
SQL Server MVP
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message news:OvpsIwbZFHA.4088@.TK2MSFTNGP15.phx.gbl...
No. All you have to do is add the /3GB switch to boot.ini and reboot. If you wanted to address > 4GB of RAM then you would have to start playing with AWE but <= 4GB is addressable with normal windows memory addressing & therefore normal MSSQL dynamic memory management.
mike hodgson | database administrator | mallesons stephen jaques
T +61 (2) 9296 3668 | F +61 (2) 9296 3885 | M +61 (408) 675 907
E mailto:mike.hodgson@.mallesons.nospam.com | W http://www.mallesons.com
Oskar wrote:
Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
hand. The SQL Server is configured for dynamic memory allocation. The machine
had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
more gigabytes of RAM into the machine and I want to allow the SQL Server to
use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling it to
use the additional gigabyte of RAM?
Many thanks,
Oskar
Adding more RAM for MS SQL Server 2000
Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
hand. The SQL Server is configured for dynamic memory allocation. The machine
had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
more gigabytes of RAM into the machine and I want to allow the SQL Server to
use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling it to
use the additional gigabyte of RAM?
--
Many thanks,
OskarThis is a multi-part message in MIME format.
--060508000204080606090209
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
No. All you have to do is add the /3GB switch to boot.ini and reboot.
If you wanted to address > 4GB of RAM then you would have to start
playing with AWE but <= 4GB is addressable with normal windows memory
addressing & therefore normal MSSQL dynamic memory management.
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Oskar wrote:
>Hi
>I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
>hand. The SQL Server is configured for dynamic memory allocation. The machine
>had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
>more gigabytes of RAM into the machine and I want to allow the SQL Server to
>use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
>boot.ini).
>Do I also have to reconfigure any SQL Server parameters after enabling it to
>use the additional gigabyte of RAM?
>--
>Many thanks,
>Oskar
>
>
--060508000204080606090209
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>No. All you have to do is add the /3GB switch to boot.ini and
reboot. If you wanted to address > 4GB of RAM then you would have
to start playing with AWE but <= 4GB is addressable with normal
windows memory addressing & therefore normal MSSQL dynamic memory
management.</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font> </span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"> <font face="Tahoma"
size="2">|</font><i><font face="Tahoma"> </font><font face="Tahoma"
size="2"> database administrator</font></i><font face="Tahoma" size="2">
| mallesons</font><font face="Tahoma"> </font><font face="Tahoma"
size="2">stephen</font><font face="Tahoma"> </font><font face="Tahoma"
size="2"> jaques</font><font face="Tahoma"><br>
</font><b><font face="Tahoma" size="2">T</font></b><font face="Tahoma"
size="2"> +61 (2) 9296 3668 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2"> F</font></b><font face="Tahoma" size="2"> +61
(2) 9296 3885 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2">M</font></b><font face="Tahoma" size="2"> +61
(408) 675 907</font><br>
<b><font face="Tahoma" size="2">E</font></b><font face="Tahoma" size="2">
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> |</font><b><font
face="Tahoma"> </font><font face="Tahoma" size="2">W</font></b><font
face="Tahoma" size="2"> <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a></font></span> </p>
</div>
<br>
<br>
Oskar wrote:
<blockquote cite="midDA9DCAEE-A7F3-4E04-986C-97D1E43CDE91@.microsoft.com"
type="cite">
<pre wrap="">Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
hand. The SQL Server is configured for dynamic memory allocation. The machine
had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
more gigabytes of RAM into the machine and I want to allow the SQL Server to
use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling it to
use the additional gigabyte of RAM?
--
Many thanks,
Oskar
</pre>
</blockquote>
</body>
</html>
--060508000204080606090209--|||This is a multi-part message in MIME format.
--=_NextPart_000_004D_01C565EC.8E52DE90
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Hi,
This will work out if your SQL server 2000 edition is Enterprise or =Developer. Standard edition can support a maximum of 2 GB only.
Thanks
Hari
SQL Server MVP
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message =news:OvpsIwbZFHA.4088@.TK2MSFTNGP15.phx.gbl...
No. All you have to do is add the /3GB switch to boot.ini and reboot. = If you wanted to address > 4GB of RAM then you would have to start =playing with AWE but <=3D 4GB is addressable with normal windows memory =addressing & therefore normal MSSQL dynamic memory management.
--
mike hodgson | database administrator | mallesons stephen jaques
T +61 (2) 9296 3668 | F +61 (2) 9296 3885 | M +61 (408) 675 907
E mailto:mike.hodgson@.mallesons.nospam.com | W =http://www.mallesons.com=20
Oskar wrote: Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at =my hand. The SQL Server is configured for dynamic memory allocation. The =machine had 2GB of RAM in it when I installed the SQL Server. Now I've installed =two more gigabytes of RAM into the machine and I want to allow the SQL =Server to use a total of 3GB of RAM (by means of turning on the /3GB switch in =Windows boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling =it to use the additional gigabyte of RAM?
--
Many thanks,
Oskar
--=_NextPart_000_004D_01C565EC.8E52DE90
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hi,
This will work out if your SQL server =2000 edition is Enterprise or Developer. Standard edition can support a maximum of 2 =GB only.
Thanks
Hari
SQL Server MVP
"Mike Hodgson" wrote in message news:OvpsIwbZFHA.4088=@.TK2MSFTNGP15.phx.gbl...No. All you have to do is add the /3GB switch to boot.ini and =reboot. If you wanted to address > 4GB of RAM then you would have to start playing =with AWE but <=3D 4GB is addressable with normal windows memory =addressing & therefore normal MSSQL dynamic memory management.
--mike =hodgson | database =administrator | mallesons =stephen jaquesT +61 (2) 9296 3668 | F +61 (2) 9296 3885 | M +61 (408) 675 907E mailto:mike.hodgson@.mal=lesons.nospam.com | W http://www.mallesons.com Oskar wrote: Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at =my hand. The SQL Server is configured for dynamic memory allocation. The =machine had 2GB of RAM in it when I installed the SQL Server. Now I've installed =two more gigabytes of RAM into the machine and I want to allow the SQL =Server to use a total of 3GB of RAM (by means of turning on the /3GB switch in =Windows boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling =it to use the additional gigabyte of RAM?
--
Many thanks,
Oskar
--=_NextPart_000_004D_01C565EC.8E52DE90--
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
hand. The SQL Server is configured for dynamic memory allocation. The machine
had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
more gigabytes of RAM into the machine and I want to allow the SQL Server to
use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling it to
use the additional gigabyte of RAM?
--
Many thanks,
OskarThis is a multi-part message in MIME format.
--060508000204080606090209
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
No. All you have to do is add the /3GB switch to boot.ini and reboot.
If you wanted to address > 4GB of RAM then you would have to start
playing with AWE but <= 4GB is addressable with normal windows memory
addressing & therefore normal MSSQL dynamic memory management.
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Oskar wrote:
>Hi
>I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
>hand. The SQL Server is configured for dynamic memory allocation. The machine
>had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
>more gigabytes of RAM into the machine and I want to allow the SQL Server to
>use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
>boot.ini).
>Do I also have to reconfigure any SQL Server parameters after enabling it to
>use the additional gigabyte of RAM?
>--
>Many thanks,
>Oskar
>
>
--060508000204080606090209
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>No. All you have to do is add the /3GB switch to boot.ini and
reboot. If you wanted to address > 4GB of RAM then you would have
to start playing with AWE but <= 4GB is addressable with normal
windows memory addressing & therefore normal MSSQL dynamic memory
management.</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font> </span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"> <font face="Tahoma"
size="2">|</font><i><font face="Tahoma"> </font><font face="Tahoma"
size="2"> database administrator</font></i><font face="Tahoma" size="2">
| mallesons</font><font face="Tahoma"> </font><font face="Tahoma"
size="2">stephen</font><font face="Tahoma"> </font><font face="Tahoma"
size="2"> jaques</font><font face="Tahoma"><br>
</font><b><font face="Tahoma" size="2">T</font></b><font face="Tahoma"
size="2"> +61 (2) 9296 3668 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2"> F</font></b><font face="Tahoma" size="2"> +61
(2) 9296 3885 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2">M</font></b><font face="Tahoma" size="2"> +61
(408) 675 907</font><br>
<b><font face="Tahoma" size="2">E</font></b><font face="Tahoma" size="2">
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> |</font><b><font
face="Tahoma"> </font><font face="Tahoma" size="2">W</font></b><font
face="Tahoma" size="2"> <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a></font></span> </p>
</div>
<br>
<br>
Oskar wrote:
<blockquote cite="midDA9DCAEE-A7F3-4E04-986C-97D1E43CDE91@.microsoft.com"
type="cite">
<pre wrap="">Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
hand. The SQL Server is configured for dynamic memory allocation. The machine
had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
more gigabytes of RAM into the machine and I want to allow the SQL Server to
use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling it to
use the additional gigabyte of RAM?
--
Many thanks,
Oskar
</pre>
</blockquote>
</body>
</html>
--060508000204080606090209--|||This is a multi-part message in MIME format.
--=_NextPart_000_004D_01C565EC.8E52DE90
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Hi,
This will work out if your SQL server 2000 edition is Enterprise or =Developer. Standard edition can support a maximum of 2 GB only.
Thanks
Hari
SQL Server MVP
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message =news:OvpsIwbZFHA.4088@.TK2MSFTNGP15.phx.gbl...
No. All you have to do is add the /3GB switch to boot.ini and reboot. = If you wanted to address > 4GB of RAM then you would have to start =playing with AWE but <=3D 4GB is addressable with normal windows memory =addressing & therefore normal MSSQL dynamic memory management.
--
mike hodgson | database administrator | mallesons stephen jaques
T +61 (2) 9296 3668 | F +61 (2) 9296 3885 | M +61 (408) 675 907
E mailto:mike.hodgson@.mallesons.nospam.com | W =http://www.mallesons.com=20
Oskar wrote: Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at =my hand. The SQL Server is configured for dynamic memory allocation. The =machine had 2GB of RAM in it when I installed the SQL Server. Now I've installed =two more gigabytes of RAM into the machine and I want to allow the SQL =Server to use a total of 3GB of RAM (by means of turning on the /3GB switch in =Windows boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling =it to use the additional gigabyte of RAM?
--
Many thanks,
Oskar
--=_NextPart_000_004D_01C565EC.8E52DE90
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hi,
This will work out if your SQL server =2000 edition is Enterprise or Developer. Standard edition can support a maximum of 2 =GB only.
Thanks
Hari
SQL Server MVP
"Mike Hodgson"
--mike =hodgson | database =administrator | mallesons =stephen jaquesT +61 (2) 9296 3668 | F +61 (2) 9296 3885 | M +61 (408) 675 907E mailto:mike.hodgson@.mal=lesons.nospam.com | W http://www.mallesons.com Oskar wrote: Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at =my hand. The SQL Server is configured for dynamic memory allocation. The =machine had 2GB of RAM in it when I installed the SQL Server. Now I've installed =two more gigabytes of RAM into the machine and I want to allow the SQL =Server to use a total of 3GB of RAM (by means of turning on the /3GB switch in =Windows boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling =it to use the additional gigabyte of RAM?
--
Many thanks,
Oskar
--=_NextPart_000_004D_01C565EC.8E52DE90--
Adding more RAM for MS SQL Server 2000
Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
hand. The SQL Server is configured for dynamic memory allocation. The machin
e
had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
more gigabytes of RAM into the machine and I want to allow the SQL Server to
use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling it to
use the additional gigabyte of RAM?
Many thanks,
OskarNo. All you have to do is add the /3GB switch to boot.ini and reboot.
If you wanted to address > 4GB of RAM then you would have to start
playing with AWE but <= 4GB is addressable with normal windows memory
addressing & therefore normal MSSQL dynamic memory management.
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Oskar wrote:
>Hi
>I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
>hand. The SQL Server is configured for dynamic memory allocation. The machi
ne
>had 2GB of RAM in it when I installed the SQL Server. Now I've installed tw
o
>more gigabytes of RAM into the machine and I want to allow the SQL Server t
o
>use a total of 3GB of RAM (by means of turning on the /3GB switch in Window
s
>boot.ini).
>Do I also have to reconfigure any SQL Server parameters after enabling it t
o
>use the additional gigabyte of RAM?
>--
>Many thanks,
>Oskar
>
>|||Hi,
This will work out if your SQL server 2000 edition is Enterprise or Develope
r. Standard edition can support a maximum of 2 GB only.
Thanks
Hari
SQL Server MVP
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message news:Ovp
sIwbZFHA.4088@.TK2MSFTNGP15.phx.gbl...
No. All you have to do is add the /3GB switch to boot.ini and reboot. If yo
u wanted to address > 4GB of RAM then you would have to start playing with A
WE but <= 4GB is addressable with normal windows memory addressing & therefo
re normal MSSQL dynamic memory management.
mike hodgson | database administrator | mallesons stephen jaques
T +61 (2) 9296 3668 | F +61 (2) 9296 3885 | M +61 (408) 675 907
E mailto:mike.hodgson@.mallesons.nospam.com | W http://www.mallesons.com
Oskar wrote:
Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
hand. The SQL Server is configured for dynamic memory allocation. The machin
e
had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
more gigabytes of RAM into the machine and I want to allow the SQL Server to
use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling it to
use the additional gigabyte of RAM?
Many thanks,
Oskar
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
hand. The SQL Server is configured for dynamic memory allocation. The machin
e
had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
more gigabytes of RAM into the machine and I want to allow the SQL Server to
use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling it to
use the additional gigabyte of RAM?
Many thanks,
OskarNo. All you have to do is add the /3GB switch to boot.ini and reboot.
If you wanted to address > 4GB of RAM then you would have to start
playing with AWE but <= 4GB is addressable with normal windows memory
addressing & therefore normal MSSQL dynamic memory management.
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Oskar wrote:
>Hi
>I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
>hand. The SQL Server is configured for dynamic memory allocation. The machi
ne
>had 2GB of RAM in it when I installed the SQL Server. Now I've installed tw
o
>more gigabytes of RAM into the machine and I want to allow the SQL Server t
o
>use a total of 3GB of RAM (by means of turning on the /3GB switch in Window
s
>boot.ini).
>Do I also have to reconfigure any SQL Server parameters after enabling it t
o
>use the additional gigabyte of RAM?
>--
>Many thanks,
>Oskar
>
>|||Hi,
This will work out if your SQL server 2000 edition is Enterprise or Develope
r. Standard edition can support a maximum of 2 GB only.
Thanks
Hari
SQL Server MVP
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message news:Ovp
sIwbZFHA.4088@.TK2MSFTNGP15.phx.gbl...
No. All you have to do is add the /3GB switch to boot.ini and reboot. If yo
u wanted to address > 4GB of RAM then you would have to start playing with A
WE but <= 4GB is addressable with normal windows memory addressing & therefo
re normal MSSQL dynamic memory management.
mike hodgson | database administrator | mallesons stephen jaques
T +61 (2) 9296 3668 | F +61 (2) 9296 3885 | M +61 (408) 675 907
E mailto:mike.hodgson@.mallesons.nospam.com | W http://www.mallesons.com
Oskar wrote:
Hi
I have a MS SQL Server 2000 SP3 on MS Windows Server 2003 SP1 machine at my
hand. The SQL Server is configured for dynamic memory allocation. The machin
e
had 2GB of RAM in it when I installed the SQL Server. Now I've installed two
more gigabytes of RAM into the machine and I want to allow the SQL Server to
use a total of 3GB of RAM (by means of turning on the /3GB switch in Windows
boot.ini).
Do I also have to reconfigure any SQL Server parameters after enabling it to
use the additional gigabyte of RAM?
Many thanks,
Oskar
Subscribe to:
Posts (Atom)