Big Database

I need Help!
My dabase has aproximately 45 GB and in the last weeks MSSQL started to
consume all the resources, basically all the RAM of the server. My server
has 8 GB of RAM. It keep consuming more and more ram memory without release
the RAM. It get to the point that I must reboot the server, sometimes with a
lot of users connected to it.
I have Windows 2000 Server and my MSSQL is a 2000 Standard Edition 8.00.194
RTM.
Before my server was very fast. I don't understand what is happening here.
I will appreciate your comments.
RRafael,
First question you are using SQL 2000 RTM? Why are you not on SP 3 or SP 4?
There are many bugs fixed between RTM and SP 3 and SP 4. One of these could
be the issue.
Second, is this a single instance of SQL 2000?
SQL 2000 standard can only address 2 GB. If you want to be able to address
more RAM in SQL 2000 you will need to upgrade to the Enterprise Edition.
Then you will need to enable AWE, read BOL: Using AWE Memory on Windows
2000.
If you were running multiple instances of Standard then they each can
address 2 GB of RAM.
Third, you can allow SQL to dynamically control memory or you can set it. If
you use AWE to use more than 2 GB of RAM you will have to manually set it.
As your short term fix, you could try manually setting the amount of RAM for
SQL Server at 2 GB. Then I would load up SP 3 if not SP 4 as soon as
possible, don't forget to try it in your test environment first to make
certain that it does not break anything else. Then I would consider
Enterprise Edition so that I could actually take advantage of all of the
RAM!
David Lundell
Principal Consultant and Trainer
www.MutuallyBeneficial.com
David@.MutuallyBeneficial.com
"Rafael Tejera" <rafaeltejera@.hotmail.com> wrote in message
news:%23tZbWtAgGHA.5088@.TK2MSFTNGP02.phx.gbl...
>I need Help!
> My dabase has aproximately 45 GB and in the last weeks MSSQL started to
> consume all the resources, basically all the RAM of the server. My server
> has 8 GB of RAM. It keep consuming more and more ram memory without
> release the RAM. It get to the point that I must reboot the server,
> sometimes with a lot of users connected to it.
> I have Windows 2000 Server and my MSSQL is a 2000 Standard Edition
> 8.00.194 RTM.
> Before my server was very fast. I don't understand what is happening here.
> I will appreciate your comments.
>
> R
>
>

Big Database

I need Help!
My dabase has aproximately 45 GB and in the last weeks MSSQL started to
consume all the resources, basically all the RAM of the server. My server
has 8 GB of RAM. It keep consuming more and more ram memory without release
the RAM. It get to the point that I must reboot the server, sometimes with a
lot of users connected to it.
I have Windows 2000 Server and my MSSQL is a 2000 Standard Edition 8.00.194
RTM.
Before my server was very fast. I don't understand what is happening here.
I will appreciate your comments.
RRafael,
First question you are using SQL 2000 RTM? Why are you not on SP 3 or SP 4?
There are many bugs fixed between RTM and SP 3 and SP 4. One of these could
be the issue.
Second, is this a single instance of SQL 2000?
SQL 2000 standard can only address 2 GB. If you want to be able to address
more RAM in SQL 2000 you will need to upgrade to the Enterprise Edition.
Then you will need to enable AWE, read BOL: Using AWE Memory on Windows
2000.
If you were running multiple instances of Standard then they each can
address 2 GB of RAM.
Third, you can allow SQL to dynamically control memory or you can set it. If
you use AWE to use more than 2 GB of RAM you will have to manually set it.
As your short term fix, you could try manually setting the amount of RAM for
SQL Server at 2 GB. Then I would load up SP 3 if not SP 4 as soon as
possible, don't forget to try it in your test environment first to make
certain that it does not break anything else. Then I would consider
Enterprise Edition so that I could actually take advantage of all of the
RAM!
David Lundell
Principal Consultant and Trainer
www.MutuallyBeneficial.com
David@.MutuallyBeneficial.com
"Rafael Tejera" <rafaeltejera@.hotmail.com> wrote in message
news:%23tZbWtAgGHA.5088@.TK2MSFTNGP02.phx.gbl...
>I need Help!
> My dabase has aproximately 45 GB and in the last weeks MSSQL started to
> consume all the resources, basically all the RAM of the server. My server
> has 8 GB of RAM. It keep consuming more and more ram memory without
> release the RAM. It get to the point that I must reboot the server,
> sometimes with a lot of users connected to it.
> I have Windows 2000 Server and my MSSQL is a 2000 Standard Edition
> 8.00.194 RTM.
> Before my server was very fast. I don't understand what is happening here.
> I will appreciate your comments.
>
> R
>
>

Best way to implement "warm" standby? - considering log shipping

Hi Larry,
Log Shipping is the ultimate solution if you are on SQL
Server Enterprise Edition. Follow these Resources..
Log Shipping in SQL Server 2000 - Part 1
http://www.microsoft.com/technet/treeview/default.asp?
url=/technet/prodtechnol/sql/deploy/prodspecs/logship1.asp
Log Shipping in SQL Server 2000 - Part 2
http://www.microsoft.com/technet/treeview/default.asp?
url=/technet/prodtechnol/sql/deploy/prodspecs/logship1.asp
How to Perform SQL Server Log Shipping
http://www.sql-server-
performance.com/sql_server_log_shipping.asp
HTH
THIRUMAL REDDY MARAM
Sys Amin / SQL DBA

quote:

---

>--Original Message--
>I have TWO networked servers; one production, and one

---

backup. I want to be

quote:

---

>able to use the backup in case of a production server

---

failure. The loss of

quote:

---

>a "little" data is acceptable in case of failure. Log

---

Shipping looks like

quote:

---

>the easiest but there seems to be a lot of warnings about

---

(1) having a

quote:

---

>monitor server, and (2) having this server NOT be either

---

the production

quote:

---

>server nor the backup. I only have two servers so I

---

can't do this.

quote:

---

>Is Log Shipping the best solution? Also--and this might

---

affect your

quote:

---

>response--it is possible that the backup system might

---

not be available 100%

quote:

---

>of the time. I bring this up because I don't know what

---

will happen if the

quote:

---

>production system wants to ship a log, and the backup

---

computer isn't

quote:

---

>available to accept it. (')
>Any help, recommendations?
>TIA,
>Larry Woods
>
>.
>

---

Thanks, Thirumal,
I've printed off all three articles and I will study them.
Larry
"Thirumal" <treddym@.hotmail.nospam.com> wrote in message
news:129a01c3df61$ab5c71d0$a601280a@.phx.gbl...[QUOTE]
> Hi Larry,
> Log Shipping is the ultimate solution if you are on SQL
> Server Enterprise Edition. Follow these Resources..
> Log Shipping in SQL Server 2000 - Part 1
> http://www.microsoft.com/technet/treeview/default.asp?
> url=/technet/prodtechnol/sql/deploy/prodspecs/logship1.asp
> Log Shipping in SQL Server 2000 - Part 2
> http://www.microsoft.com/technet/treeview/default.asp?
> url=/technet/prodtechnol/sql/deploy/prodspecs/logship1.asp
> How to Perform SQL Server Log Shipping
> http://www.sql-server-
> performance.com/sql_server_log_shipping.asp
> HTH
> --
> THIRUMAL REDDY MARAM
> Sys Amin / SQL DBA
> backup. I want to be
> failure. The loss of
> Shipping looks like
> (1) having a
> the production
> can't do this.
> affect your
> not be available 100%
> will happen if the
> computer isn't