Best practices for remotely connecting

I have a Windows 2003 standard edition server with MSDE 2000 installed
at a client. I would like to be able to connect my SQL Enterprise
manager in case I need to do something in their database and I need to
do it remotely. I have the MSDE set to mixed mode authentication and
opened the ports (1433 and tried 2433 as well because client network
utility said it used that port) but I cannot connect for some reason.
Any clues what I still need to do?
The other question is: is it safe to connect a SQL server directly to
the net? The SQL Server is fully up to date with the latest patches.
Are there any guidelines that I need to follow when I want to do this
(in a safe way)?
Thanks in advance,
Stijn Verrept.You should consider establishing a VPN connection from your remote client.
Then use Terminal Server or Remote Desktop to administer the server.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin McDonnell [MSFT] wrote:

quote:

---

> You should consider establishing a VPN connection from your remote
> client. Then use Terminal Server or Remote Desktop to administer the
> server.

---

Thanks for your answer Kevin. I can login with TS but MSDE does not
include enterprise manager so I cannot install this on the clients pc!
Kind regards,
Stijn Verrept.|||So, unless the client as a Terminal Server that you can install the SQL
Client tools, your options are limited.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin McDonnell [MSFT] wrote:

quote:

---

> So, unless the client as a Terminal Server that you can install the
> SQL Client tools, your options are limited.

---

What do you mean? The client is running a terminal server. And I can
log in on that machine. The problem is that it does not have
Enterprise manager. This is why I need to connect with my enterprise
manager to the terminal server through the net. Isn't this possible?
Why doesn't it want to work?
Kind regards,
Stijn Verrept.|||Here's what I'm recommending:
1. Client -->VPN -->Terminal Server (with Enterprise Manager Installed)
-->MSDE
or
2. Client (with Enterprise Manager) -->VPN -->MSDE
Option 1 would be preferred.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Im having exactly the same problem.
However, we need access to both our SQL Server and their Server as we
do database design work as part of our web development and need to
upload databases we have created.
Weve tried the VPN route, but our policy is to keep our SQL Server
well behind the firewall, and there are no exceptions (Clients company
information kept on them so security is a big deal) so they cant see
our DB.
They have opened all ports for our IP address so all traffic is
allowed, but we can still not connect to their DB.
A simple yes or no is required, Can you connect to a remote MSDE
Server across the internet and register it in SQL Server Enterprise
manager?
TCPIP and Named Pipes are Installed and enabled on MSDE
kevmc@.online.microsoft.com (Kevin McDonnell [MSFT]) wrote in message news:<v40lyXs2DHA.3564@.cp
msftngxa07.phx.gbl>...
> Here's what I'm recommending:
> 1. Client -->VPN -->Terminal Server (with Enterprise Manager Installed)
> -->MSDE
> or
> 2. Client (with Enterprise Manager) -->VPN -->MSDE
> Option 1 would be preferred.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.|||Can you connect to a remote MSDE
Server across the internet and register it in SQL Server Enterprise
manager?
Simple Answer:
Yes. Over TCP. As long as the ports are open on the firewall.
287932 INF: TCP Ports Needed for Communication to SQL Server Through a
Firewall
http://support.microsoft.com/?id=287932
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thanks Kevin, Thats what I thought, but not what I wanted to hear!
This means we have a different problem which is going to be a nightmare
to sort out.
If SQL Server (MSDE) has the TCPIP netlib enabled and the default port
is being used (1433), do we need to have 1433 enabled on both firewalls
(theirs and ours) to enable enterprise manager to register this server?
Also, Do we need to open port 1434 (Ive heard that this is needed for 2
way communication)
Any other ideas why I can connect to our ISP hosted SQL Servers, but not
our clients (who hosts their own website) even though they have tried
with the server outside the firewall? Even If I make a vpn connection to
the SQL Server box, and can ping it by name, I still cant connect. I get
the error:
SQL Server does not exist or access is denied
ConnectionOpen(Connect())
Desperate to get this sorted now
Thanx again
remove 'REMOVESPAM.' for email
Karl Rhodes
Internet Solutions Architect
The Learning Business & Keywave
www.thelearningbiz.com
www.keywave.com
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||from previous post:
"This means we have a different problem which is going to be a nightmare
to sort out.
If SQL Server (MSDE) has the TCPIP netlib enabled and the default port
is being used (1433), do we need to have 1433 enabled on both firewalls
(theirs and ours) to enable enterprise manager to register this server?
Also, Do we need to open port 1434 (Ive heard that this is needed for 2
way communication)"
You would need 1433 open on the remote firewall. You client would open up
a tcp session to 1433 and communicate back to your
client on a random tcp port.
Ex. client opens port 2000 and sends traffic to the remote MSDE on 1433
The communication comes back from 1433 to your client port 2000.
"Any other ideas why I can connect to our ISP hosted SQL Servers, but not
our clients (who hosts their own website) even though they have tried
with the server outside the firewall? Even If I make a vpn connection to
the SQL Server box, and can ping it by name, I still cant connect. I get
the error:
SQL Server does not exist or access is denied
ConnectionOpen(Connect())
"
This error is meaningless without the OS error number.
Force a TCP sockets connection with ISQL.exe
Ex. ISQL -Stcp:ServerName -Uuserid -Ppassword
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.sql

Best practice for DR/Standby server

We use SQL2000 Standard Edition SP3a. We have a
Production Server and a DR Server that is off site.
Currently I have SPs coded that do log shipping to the DR
Server every hour from the log backups on the production
server. Is this the best way to keep the DR Server up to
date? I've explored Replication, but it seemed much more
complex and structure changes don't get replicated which
means a new shipment of the entire Production DBs anytime
a structure change is made. It seems like Replication
would be tough to support for this. There is also
Hardware Replication with the Production SAN to the SAN at
the DR site. That's not something I'm very familar with
or how it works exactly. Is Hardware Replication a better
way to do it? I've been told that they may need real time
updates to the DR Server in the future and I'm not sure if
that is realistic or not. I still think log shipping is
best. I could take it down to shipping every 15 min if
needed. Could someone post some opinions/suggestions for
me.
Thanks,
Van
Van,
If your DR server is only used for DR purposes this is what I would do - you should have less than 30 secs down time if you try what I propose.
1) Place your SQL Server data and log files into two separate LUNs on the SAN at your primary site. Start SQL Server and make sure it's running normally. You may even want to try putting the OS on the SAN too - up to you.
2) Image the server using an imaging tool and restore the image to your secondary server and attach it to your secondary SAN at your DR site.
3) Stop SQL Server service on the secondary server.
4) Set up replication at the block level using SAN replication software - replicate the LUNs that the log and data files reside on. You will need to do a full mirror to start with, and then stream replication from then on.
5) When the primary site goes down, make sure that replication gets stopped (it will stop anyway), perform a failover on your SAN to the secondary site, then start SQL Server on your secondary server. You will find that SQL Server will start normally and
there will be much, much, much less data loss than log shipping. Make sure that replication cannot go from source --> secondary should the source come back online, otherwise you will get data file corruption.
6) Step 5 can be scripted so that you can just "push a button" to fail over. The entire process to fail over shouldn't take more than 30 seconds - 1 minute.
The failback process once the primary is available again is a reverse of the above but in a more controlled manner.
I have implemented this solution across the atlantic and it works very, very well indeed, as long as the process is scripted with all manual steps removed. Also, make sure a DR test is performed regularly. Say goodbye to log shipping.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk

Best practice for DR/Standby server

We use SQL2000 Standard Edition SP3a. We have a
Production Server and a DR Server that is off site.
Currently I have SPs coded that do log shipping to the DR
Server every hour from the log backups on the production
server. Is this the best way to keep the DR Server up to
date? I've explored Replication, but it seemed much more
complex and structure changes don't get replicated which
means a new shipment of the entire Production DBs anytime
a structure change is made. It seems like Replication
would be tough to support for this. There is also
Hardware Replication with the Production SAN to the SAN at
the DR site. That's not something I'm very familar with
or how it works exactly. Is hardware Replication a better
way to do it? I've been told that they may need real time
updates to the DR Server in the future and I'm not sure if
that is realistic or not. I still think log shipping is
best. I could take it down to shipping every 15 min if
needed. Could someone post some opinions/suggestions for
me.
Thanks,
VanVan,
If your DR server is only used for DR purposes this is what I would do - you
should have less than 30 secs down time if you try what I propose.
1) Place your SQL Server data and log files into two separate LUNs on the SA
N at your primary site. Start SQL Server and make sure it's running normally
. You may even want to try putting the OS on the SAN too - up to you.
2) Image the server using an imaging tool and restore the image to your seco
ndary server and attach it to your secondary SAN at your DR site.
3) Stop SQL Server service on the secondary server.
4) Set up replication at the block level using SAN replication software - re
plicate the LUNs that the log and data files reside on. You will need to do
a full mirror to start with, and then stream replication from then on.
5) When the primary site goes down, make sure that replication gets stopped
(it will stop anyway), perform a failover on your SAN to the secondary site,
then start SQL Server on your secondary server. You will find that SQL Serv
er will start normally and
there will be much, much, much less data loss than log shipping. Make sure t
hat replication cannot go from source --> secondary should the source come b
ack online, otherwise you will get data file corruption.
6) Step 5 can be scripted so that you can just "push a button" to fail over.
The entire process to fail over shouldn't take more than 30 seconds - 1 min
ute.
The failback process once the primary is available again is a reverse of the
above but in a more controlled manner.
I have implemented this solution across the atlantic and it works very, very
well indeed, as long as the process is scripted with all manual steps remov
ed. Also, make sure a DR test is performed regularly. Say goodbye to log shi
pping.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk

Best Performance

We're looking to upgrade our SQL Server - We have two options - A dual
processor machine running Enterprise edition, or a quad processor machine
running standard edition.
The question I'd like to ask is which is likely to be the faster - Obviously
Enterprise edition will allow us to have more memory and should therefore
hopefully cut down the number of recompiles, but having four processors...
Help !!!
AndyFYI: There can be many reasons for a recompile. But you must be using
really many stored procedures and very little memory. SQL-Server will
make the tradeoff how to use the available memory and it knows a
recompilation is expensive. Because of that, there will be few
recompiles because of memory constraints.
Gert-Jan
Andy Reilly wrote:

quote:

---

> We're looking to upgrade our SQL Server - We have two options - A dual
> processor machine running Enterprise edition, or a quad processor machine
> running standard edition.
> The question I'd like to ask is which is likely to be the faster - Obvious
ly
> Enterprise edition will allow us to have more memory and should therefore
> hopefully cut down the number of recompiles, but having four processors...
.
> Help !!!
> Andy

---

|||the corrent answer to almost any performance queestion is 'it depends'. <g>
I don't have enough info to say with certainty... no one does...
but generally speaking... I would be SHOCKED if the 4X Standard box didn't
perform better than the 2X Enterprise. Enterprise can support more mem,
but... the Standard limits are pretty darn good. IF you can get adequte
performance on a 2X box... that almost implies to me that your app and data
set isn't bing enough to worry about going beyond 2G anyway...
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Andy Reilly" <ReillyA@.ThomasNoSpam-Sanderson.co.uk> wrote in message
news:%23F4GHBC5DHA.2188@.TK2MSFTNGP10.phx.gbl...

quote:

---

> We're looking to upgrade our SQL Server - We have two options - A dual
> processor machine running Enterprise edition, or a quad processor machine
> running standard edition.
> The question I'd like to ask is which is likely to be the faster -

---

Obviously

quote:

---

> Enterprise edition will allow us to have more memory and should therefore
> hopefully cut down the number of recompiles, but having four

---

processors...

quote:

---

> Help !!!
> Andy
>

---

Best Performance

We're looking to upgrade our SQL Server - We have two options - A dual
processor machine running Enterprise edition, or a quad processor machine
running standard edition.
The question I'd like to ask is which is likely to be the faster - Obviously
Enterprise edition will allow us to have more memory and should therefore
hopefully cut down the number of recompiles, but having four processors...
Help !!!
AndyEnterprise is not necessarily faster than standard.
Check the following for further details :-
http://www.microsoft.com/technet/treeview/default.asp?
url=/technet/prodtechnol/sql/evaluate/choose.asp
If you think about it for a moment the speed of any
application is going to as fast as the slowest component,
which is normally (in order of slowest) Network, Hard
Disk, then CPU.
So before getting your CPU's sorted you should have a look
at the other two.
If you would like further details then feel free to email
me at little_flowery_me<REMOVETHIS>.@.hotmail.com
In the meanwhile have a quick look at this...
http://www.tpc.org/
J
>--Original Message--
>We're looking to upgrade our SQL Server - We have two
options - A dual
>processor machine running Enterprise edition, or a quad
processor machine
>running standard edition.
>The question I'd like to ask is which is likely to be the
faster - Obviously
>Enterprise edition will allow us to have more memory and
should therefore
>hopefully cut down the number of recompiles, but having
four processors...
>Help !!!
>Andy
>
>.
>|||FYI: There can be many reasons for a recompile. But you must be using
really many stored procedures and very little memory. SQL-Server will
make the tradeoff how to use the available memory and it knows a
recompilation is expensive. Because of that, there will be few
recompiles because of memory constraints.
Gert-Jan
Andy Reilly wrote:
> We're looking to upgrade our SQL Server - We have two options - A dual
> processor machine running Enterprise edition, or a quad processor machine
> running standard edition.
> The question I'd like to ask is which is likely to be the faster - Obviously
> Enterprise edition will allow us to have more memory and should therefore
> hopefully cut down the number of recompiles, but having four processors...
> Help !!!
> Andy|||the corrent answer to almost any performance queestion is 'it depends'. <g>
I don't have enough info to say with certainty... no one does...
but generally speaking... I would be SHOCKED if the 4X Standard box didn't
perform better than the 2X Enterprise. Enterprise can support more mem,
but... the Standard limits are pretty darn good. IF you can get adequte
performance on a 2X box... that almost implies to me that your app and data
set isn't bing enough to worry about going beyond 2G anyway...
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Andy Reilly" <ReillyA@.ThomasNoSpam-Sanderson.co.uk> wrote in message
news:%23F4GHBC5DHA.2188@.TK2MSFTNGP10.phx.gbl...
> We're looking to upgrade our SQL Server - We have two options - A dual
> processor machine running Enterprise edition, or a quad processor machine
> running standard edition.
> The question I'd like to ask is which is likely to be the faster -
Obviously
> Enterprise edition will allow us to have more memory and should therefore
> hopefully cut down the number of recompiles, but having four
processors...
> Help !!!
> Andy
>

Best Method to Document Database?

I have SQL Server 2005 Developer edition. What is the best way to create a
data dictionary for an existing database? Does reporting services or other
tools provide canned reports that include all objects including keys,
constraints etc? Do I need to write my own queries to generate the meta
data or do I need to use another vendor's custom app?
txOn Wed, 22 Feb 2006 12:03:34 -0800, Simon Shutter wrote:

> I have SQL Server 2005 Developer edition. What is the best way to create
a
> data dictionary for an existing database? Does reporting services or othe
r
> tools provide canned reports that include all objects including keys,
> constraints etc? Do I need to write my own queries to generate the meta
> data or do I need to use another vendor's custom app?
> tx
Personally, I'd use another vendors too... ApexSQL Doc is what I'm
currently evaluating|||Simon Shutter wrote:
> I have SQL Server 2005 Developer edition. What is the best way to create
a
> data dictionary for an existing database? Does reporting services or othe
r
> tools provide canned reports that include all objects including keys,
> constraints etc? Do I need to write my own queries to generate the meta
> data or do I need to use another vendor's custom app?
> tx
You might want to try SchemaToDoc at http://www.schematodoc.com. It's
output is a Word document that includes information about your tables
(primary keys), fields (type, size, defaults, nullable), indexes, check
constraints, foreign key constraints, stored procedures, and views. It
also lets you annotate your tables and fields, and include those
annotations in the Word output.

Best Method to Document Database?

I have SQL Server 2005 Developer edition. What is the best way to create a
data dictionary for an existing database? Does reporting services or other
tools provide canned reports that include all objects including keys,
constraints etc? Do I need to write my own queries to generate the meta
data or do I need to use another vendor's custom app?
txOn Wed, 22 Feb 2006 12:03:34 -0800, Simon Shutter wrote:
> I have SQL Server 2005 Developer edition. What is the best way to create a
> data dictionary for an existing database? Does reporting services or other
> tools provide canned reports that include all objects including keys,
> constraints etc? Do I need to write my own queries to generate the meta
> data or do I need to use another vendor's custom app?
> tx
Personally, I'd use another vendors too... ApexSQL Doc is what I'm
currently evaluating|||Simon Shutter wrote:
> I have SQL Server 2005 Developer edition. What is the best way to create a
> data dictionary for an existing database? Does reporting services or other
> tools provide canned reports that include all objects including keys,
> constraints etc? Do I need to write my own queries to generate the meta
> data or do I need to use another vendor's custom app?
> tx
You might want to try SchemaToDoc at http://www.schematodoc.com. It's
output is a Word document that includes information about your tables
(primary keys), fields (type, size, defaults, nullable), indexes, check
constraints, foreign key constraints, stored procedures, and views. It
also lets you annotate your tables and fields, and include those
annotations in the Word output.

Best Method to Document Database?

I have SQL Server 2005 Developer edition. What is the best way to create a
data dictionary for an existing database? Does reporting services or other
tools provide canned reports that include all objects including keys,
constraints etc? Do I need to write my own queries to generate the meta
data or do I need to use another vendor's custom app?
tx
On Wed, 22 Feb 2006 12:03:34 -0800, Simon Shutter wrote:

> I have SQL Server 2005 Developer edition. What is the best way to create a
> data dictionary for an existing database? Does reporting services or other
> tools provide canned reports that include all objects including keys,
> constraints etc? Do I need to write my own queries to generate the meta
> data or do I need to use another vendor's custom app?
> tx
Personally, I'd use another vendors too... ApexSQL Doc is what I'm
currently evaluating
|||Simon Shutter wrote:
> I have SQL Server 2005 Developer edition. What is the best way to create a
> data dictionary for an existing database? Does reporting services or other
> tools provide canned reports that include all objects including keys,
> constraints etc? Do I need to write my own queries to generate the meta
> data or do I need to use another vendor's custom app?
> tx
You might want to try SchemaToDoc at http://www.schematodoc.com. It's
output is a Word document that includes information about your tables
(primary keys), fields (type, size, defaults, nullable), indexes, check
constraints, foreign key constraints, stored procedures, and views. It
also lets you annotate your tables and fields, and include those
annotations in the Word output.

Best method of Restoring a SQL 2005 Desktop Edition

For a SQL 2005 Desktop edition that has a user database and some user
accounts and linked servers. What is the best method of backing this
up and restoring to a different SQL Server?Robin9876 wrote:
> For a SQL 2005 Desktop edition that has a user database and some user
> accounts and linked servers. What is the best method of backing this
> up and restoring to a different SQL Server?
See: http://vyaskn.tripod.com/moving_sql_server.htm
--
Razvan Socol
SQL Server MVP

Best Edition & Licensing Option(s)

Hi there:

I'm an independent developer with a few projects for which I'd like to use SQL Server 2000, but I'm not exactly sure which licensing option to choose.

I've got a single-processor machine on which I'll be running the SQL Server instance, and this single instance will support up to a dozen or so separate databases, each of which will be used to power a small public Web site. From what I've read thus far, it appears the Standard Edition single-processor version & license would be most appropriate, but $5,000 is a little more than my budget can handle right now. Is there another viable option available for a situation like this?

Many thanks,
ChrisHave you considered MSDE (SQL Desktop Engine). It is ditributed free with Microsoft Office 2000/XP. There is no licensing.

The only limit is that a dtabase can't grow bigger than 1.5GB hich could be sufficient in your case.

Try these links

Choosing an edition
http://www.microsoft.com/sql/techinfo/planning/SQLResKChooseEd.asp

More about msde:
http://www.microsoft.com/sql/techinfo/development/2000/MSDE2000.asp|||Can MSDE be licensed to run in production? (From what I've read, it appears it can, as long as one possesses a properly licensed version of one of a number of MS products, including VS.NET.)

Any help is sincerely appreciated.

Thanks,
Chris|||Let say you develop an application using MS VS.NET, you can include MSDE as part of your application as the Data Engine.

So in your case it's fine if you are using ASP.Net

Benchmark for different edition SQL 2000

We want to select the edition between standard and enterprise. Our usage:
1) 10 users/application connect to the server at the same time
2) 5000 row insert per day
3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000 server
4) One database will be installed
5) The size of the database around 10GB
Because we want to replace the existing SQL6.5 with 400MHz 256MRAM database server.
Please advise. Thanks
Hi,
Based on your configurations and settings I will recommend you to go for SQL
Server standard edition.
Have a look into the below link in choosing the edition of sql server:-
http://www.microsoft.com/sql/techinf...skChooseEd.asp
Thanks
Hari
MCDBA
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> We want to select the edition between standard and enterprise. Our usage:
> 1) 10 users/application connect to the server at the same time
> 2) 5000 row insert per day
> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000 server
> 4) One database will be installed
> 5) The size of the database around 10GB
> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
database server.
> Please advise. Thanks
|||Hari,
Thanks for your advice. However, I have read the page before and without any idea. The point of availability is confused me. In fact, the standard edition and enterprise edition is no different except?
--Scalability ( useless to us because we only have 1 CPU machine with 512MRAM)
--Availability/uptime (useless to us because we don't have a standby or cluster machine)
--Performance (Time is not so critical because we are just using the 6.5 version now with no complain)
--Advanced analysis ( Analysis is not so critical because we are just using the 6.5 version now with no complain)
I just concern, is it enterprise edition is more stable? or standard edition is easy to down?
Wanchun
-- Hari Prasad wrote: --
Hi,
Based on your configurations and settings I will recommend you to go for SQL
Server standard edition.
Have a look into the below link in choosing the edition of sql server:-
http://www.microsoft.com/sql/techinf...skChooseEd.asp
Thanks
Hari
MCDBA
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...[vbcol=seagreen]
> We want to select the edition between standard and enterprise. Our usage:
> 1) 10 users/application connect to the server at the same time
> 2) 5000 row insert per day
> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000 server
> 4) One database will be installed
> 5) The size of the database around 10GB
database server.
> Please advise. Thanks
|||No edition is any more or less stable than any others. It is mainly
features and capacity. Standard edition will do just fine for your needs.
Andrew J. Kelly SQL MVP
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> Hari,
> Thanks for your advice. However, I have read the page before and without
any idea. The point of availability is confused me. In fact, the standard
edition and enterprise edition is no different except?
> --Scalability ( useless to us because we only have 1 CPU machine with
512MRAM)
> --Availability/uptime (useless to us because we don't have a standby or
cluster machine)
> --Performance (Time is not so critical because we are just using the 6.5
version now with no complain)
> --Advanced analysis ( Analysis is not so critical because we are just
using the 6.5 version now with no complain)
> I just concern, is it enterprise edition is more stable? or standard
edition is easy to down?
> Wanchun
>
> -- Hari Prasad wrote: --
> Hi,
> Based on your configurations and settings I will recommend you to go
for SQL
> Server standard edition.
> Have a look into the below link in choosing the edition of sql
server:-[vbcol=seagreen]
> http://www.microsoft.com/sql/techinf...skChooseEd.asp
> Thanks
> Hari
> MCDBA
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
usage:[vbcol=seagreen]
server
> database server.
>
>
|||Andrew,
That mean from our requirement, standard edition is enough for us?
Also, the memory arrangement is the same between standard and enterprise? I am testing with standard edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I re-boot the machine, the memory back to 10M..... Is it I nee
d to re-boot the machine every week to prevent the memory to grow? Or enterprise edition can handle it better?
Any other Enterprise features that better than Standard?
Thanks
-- Andrew J. Kelly wrote: --
No edition is any more or less stable than any others. It is mainly
features and capacity. Standard edition will do just fine for your needs.
Andrew J. Kelly SQL MVP
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...[vbcol=seagreen]
> Hari,
any idea. The point of availability is confused me. In fact, the standard
edition and enterprise edition is no different except?[vbcol=seagreen]
512MRAM)
> --Availability/uptime (useless to us because we don't have a standby or
cluster machine)
> --Performance (Time is not so critical because we are just using the 6.5
version now with no complain)
> --Advanced analysis ( Analysis is not so critical because we are just
using the 6.5 version now with no complain)[vbcol=seagreen]
edition is easy to down?[vbcol=seagreen]
for SQL[vbcol=seagreen]
> Server standard edition.
server:-[vbcol=seagreen]
> Hari
> MCDBA
> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
usage:[vbcol=seagreen]
server[vbcol=seagreen]
> database server.
|||Enterprise edition has some distinct features that SE doesn't. You find them at:
http://msdn.microsoft.com/library/de...ar_ts_1cdv.asp
As for memory, please read below:
INF: SQL Server Memory Usage
http://support.microsoft.com/default...;en-us;q321363
http://www.mssqlserver.com/faq/troub...memoryleak.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> Andrew,
> That mean from our requirement, standard edition is enough for us?
> Also, the memory arrangement is the same between standard and enterprise? I am testing with standard
edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I re-boot the
machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent the memory to
grow? Or enterprise edition can handle it better?[vbcol=seagreen]
> Any other Enterprise features that better than Standard?
> Thanks
>
>
> -- Andrew J. Kelly wrote: --
> No edition is any more or less stable than any others. It is mainly
> features and capacity. Standard edition will do just fine for your needs.
> --
> Andrew J. Kelly SQL MVP
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> any idea. The point of availability is confused me. In fact, the standard
> edition and enterprise edition is no different except?
> 512MRAM)
> cluster machine)
> version now with no complain)
> using the 6.5 version now with no complain)
> edition is easy to down?
> for SQL
> server:-
> usage:
> server
|||Tibor,
My concern is how to prevent the SQL server that increase the memory usage continuously? Or We need to reboot the machine periodically? Please advise.
Wanchun
-- Tibor Karaszi wrote: --
Enterprise edition has some distinct features that SE doesn't. You find them at:
http://msdn.microsoft.com/library/de...ar_ts_1cdv.asp
As for memory, please read below:
INF: SQL Server Memory Usage
http://support.microsoft.com/default...;en-us;q321363
http://www.mssqlserver.com/faq/troub...memoryleak.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> Andrew,
> Also, the memory arrangement is the same between standard and enterprise? I am testing with standard
edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I re-boot the
machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent the memory to
grow? Or enterprise edition can handle it better?[vbcol=seagreen]
> features and capacity. Standard edition will do just fine for your needs.
> Andrew J. Kelly SQL MVP
> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> any idea. The point of availability is confused me. In fact, the standard
> edition and enterprise edition is no different except?
> 512MRAM)
> cluster machine)
> version now with no complain)
> using the 6.5 version now with no complain)
> edition is easy to down?
> for SQL
> server:-
> usage:
> server
|||Please read the links I posted about memory allocation algorithms in SQL Server. This is normal, and no reboot
is necessary.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> Tibor,
> My concern is how to prevent the SQL server that increase the memory usage continuously? Or We need to
reboot the machine periodically? Please advise.
> Wanchun
> -- Tibor Karaszi wrote: --
> Enterprise edition has some distinct features that SE doesn't. You find them at:
> http://msdn.microsoft.com/library/de...ar_ts_1cdv.asp
> As for memory, please read below:
> INF: SQL Server Memory Usage
> http://support.microsoft.com/default...;en-us;q321363
> http://www.mssqlserver.com/faq/troub...memoryleak.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I re-boot
the
> machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent the
memory to[vbcol=seagreen]
> grow? Or enterprise edition can handle it better?
|||As Tibor points out that is normal behavior and will be the same for both
Std and EE.
Andrew J. Kelly SQL MVP
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> Tibor,
> My concern is how to prevent the SQL server that increase the memory
usage continuously? Or We need to reboot the machine periodically? Please
advise.
> Wanchun
> -- Tibor Karaszi wrote: --
> Enterprise edition has some distinct features that SE doesn't. You
find them at:
>
http://msdn.microsoft.com/library/de...ar_ts_1cdv.asp[vbcol=seagreen]
> As for memory, please read below:
> INF: SQL Server Memory Usage
> http://support.microsoft.com/default...;en-us;q321363
> http://www.mssqlserver.com/faq/troub...memoryleak.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
enterprise? I am testing with standard
> edition, the memory continue to grow from 10M to 110M after I
inserted 3000 records. After I re-boot the
> machine, the memory back to 10M..... Is it I need to re-boot the
machine every week to prevent the memory to[vbcol=seagreen]
> grow? Or enterprise edition can handle it better?
mainly[vbcol=seagreen]
your needs.[vbcol=seagreen]
message[vbcol=seagreen]
without[vbcol=seagreen]
the standard[vbcol=seagreen]
with[vbcol=seagreen]
standby or[vbcol=seagreen]
the 6.5[vbcol=seagreen]
just[vbcol=seagreen]
standard[vbcol=seagreen]
you to go[vbcol=seagreen]
sql[vbcol=seagreen]
http://www.microsoft.com/sql/techinf...skChooseEd.asp[vbcol=seagreen]
message[vbcol=seagreen]
Our[vbcol=seagreen]
2000[vbcol=seagreen]
256MRAM[vbcol=seagreen]
|||Thanks again Tibor, however, if SQL used all the physical memory of the machine, then the SQL can still run smoothly? or better reboot the machine?
Wanchun
-- Tibor Karaszi wrote: --
Please read the links I posted about memory allocation algorithms in SQL Server. This is normal, and no reboot
is necessary.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> Tibor,
> My concern is how to prevent the SQL server that increase the memory usage continuously? Or We need to
reboot the machine periodically? Please advise.
> http://msdn.microsoft.com/library/de...ar_ts_1cdv.asp
> http://support.microsoft.com/default...;en-us;q321363
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I re-boot
the
> machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent the
memory to[vbcol=seagreen]
> grow? Or enterprise edition can handle it better?

Benchmark for different edition SQL 2000

We want to select the edition between standard and enterprise. Our usage:
1) 10 users/application connect to the server at the same time
2) 5000 row insert per day
3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000 server
4) One database will be installed
5) The size of the database around 10GB
Because we want to replace the existing SQL6.5 with 400MHz 256MRAM database
server.
Please advise. ThanksHi,
Based on your configurations and settings I will recommend you to go for SQL
Server standard edition.
Have a look into the below link in choosing the edition of sql server:-
http://www.microsoft.com/sql/techin...eskChooseEd.asp
Thanks
Hari
MCDBA
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> We want to select the edition between standard and enterprise. Our usage:
> 1) 10 users/application connect to the server at the same time
> 2) 5000 row insert per day
> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000 server
> 4) One database will be installed
> 5) The size of the database around 10GB
> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
database server.
> Please advise. Thanks|||Hari,
Thanks for your advice. However, I have read the page before and without any
idea. The point of availability is confused me. In fact, the standard editi
on and enterprise edition is no different except?
--Scalability ( useless to us because we only have 1 CPU machine with 512MRA
M)
--Availability/uptime (useless to us because we don't have a standby or clus
ter machine)
--Performance (Time is not so critical because we are just using the 6.5 ver
sion now with no complain)
--Advanced analysis ( Analysis is not so critical because we are just using
the 6.5 version now with no complain)
I just concern, is it enterprise edition is more stable? or standard edition
is easy to down?
Wanchun
-- Hari Prasad wrote: --
Hi,
Based on your configurations and settings I will recommend you to go for SQL
Server standard edition.
Have a look into the below link in choosing the edition of sql server:-
http://www.microsoft.com/sql/techin...eskChooseEd.asp
Thanks
Hari
MCDBA
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> We want to select the edition between standard and enterprise. Our usage:
> 1) 10 users/application connect to the server at the same time
> 2) 5000 row insert per day
> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000 server
> 4) One database will be installed
> 5) The size of the database around 10GB
database server.[vbcol=seagreen]
> Please advise. Thanks|||No edition is any more or less stable than any others. It is mainly
features and capacity. Standard edition will do just fine for your needs.
Andrew J. Kelly SQL MVP
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> Hari,
> Thanks for your advice. However, I have read the page before and without
any idea. The point of availability is confused me. In fact, the standard
edition and enterprise edition is no different except?
> --Scalability ( useless to us because we only have 1 CPU machine with
512MRAM)
> --Availability/uptime (useless to us because we don't have a standby or
cluster machine)
> --Performance (Time is not so critical because we are just using the 6.5
version now with no complain)
> --Advanced analysis ( Analysis is not so critical because we are just
using the 6.5 version now with no complain)
> I just concern, is it enterprise edition is more stable? or standard
edition is easy to down?
> Wanchun
>
> -- Hari Prasad wrote: --
> Hi,
> Based on your configurations and settings I will recommend you to go
for SQL
> Server standard edition.
> Have a look into the below link in choosing the edition of sql
server:-
> http://www.microsoft.com/sql/techin...eskChooseEd.asp
> Thanks
> Hari
> MCDBA
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
usage:[vbcol=seagreen]
server[vbcol=seagreen]
> database server.
>
>|||Andrew,
That mean from our requirement, standard edition is enough for us?
Also, the memory arrangement is the same between standard and enterprise? I
am testing with standard edition, the memory continue to grow from 10M to 11
0M after I inserted 3000 records. After I re-boot the machine, the memory ba
ck to 10M..... Is it I nee
d to re-boot the machine every week to prevent the memory to grow' Or enter
prise edition can handle it better?
Any other Enterprise features that better than Standard?
Thanks
-- Andrew J. Kelly wrote: --
No edition is any more or less stable than any others. It is mainly
features and capacity. Standard edition will do just fine for your needs.
Andrew J. Kelly SQL MVP
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> Hari,
any idea. The point of availability is confused me. In fact, the standard
edition and enterprise edition is no different except?[vbcol=seagreen]
512MRAM)[vbcol=seagreen]
> --Availability/uptime (useless to us because we don't have a standby or
cluster machine)
> --Performance (Time is not so critical because we are just using the 6.5
version now with no complain)
> --Advanced analysis ( Analysis is not so critical because we are just
using the 6.5 version now with no complain)[vbcol=seagreen]
edition is easy to down?[vbcol=seagreen]
for SQL[vbcol=seagreen]
> Server standard edition.
server:-[vbcol=seagreen]
> Hari
> MCDBA
> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
usage:[vbcol=seagreen]
server[vbcol=seagreen]
> database server.|||Enterprise edition has some distinct features that SE doesn't. You find them
at:
1cdv.asp" target="_blank">http://msdn.microsoft.com/library/d...br />
1cdv.asp
As for memory, please read below:
INF: SQL Server Memory Usage
http://support.microsoft.com/defaul...b;en-us;q321363
http://www.mssqlserver.com/faq/trou...-memoryleak.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> Andrew,
> That mean from our requirement, standard edition is enough for us?
> Also, the memory arrangement is the same between standard and enterprise? I am tes
ting with standard
edition, the memory continue to grow from 10M to 110M after I inserted 3000
records. After I re-boot the
machine, the memory back to 10M..... Is it I need to re-boot the machine ev
ery week to prevent the memory to
grow' Or enterprise edition can handle it better?[vbcol=seagreen]
> Any other Enterprise features that better than Standard?
> Thanks
>
>
> -- Andrew J. Kelly wrote: --
> No edition is any more or less stable than any others. It is mainly
> features and capacity. Standard edition will do just fine for your n
eeds.
> --
> Andrew J. Kelly SQL MVP
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> any idea. The point of availability is confused me. In fact, the stan
dard
> edition and enterprise edition is no different except?
> 512MRAM)
> cluster machine)
> version now with no complain)
> using the 6.5 version now with no complain)
> edition is easy to down?
> for SQL
> server:-
> usage:
> server|||Tibor,
My concern is how to prevent the SQL server that increase the memory usage c
ontinuously? Or We need to reboot the machine periodically? Please advise.
Wanchun
-- Tibor Karaszi wrote: --
Enterprise edition has some distinct features that SE doesn't. You find them
at:
1cdv.asp" target="_blank">http://msdn.microsoft.com/library/d...br />
1cdv.asp
As for memory, please read below:
INF: SQL Server Memory Usage
http://support.microsoft.com/defaul...b;en-us;q321363
http://www.mssqlserver.com/faq/trou...-memoryleak.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> Andrew,
> Also, the memory arrangement is the same between standard and enterprise? I am tes
ting with standard
edition, the memory continue to grow from 10M to 110M after I inserted 3000
records. After I re-boot the
machine, the memory back to 10M..... Is it I need to re-boot the machine ev
ery week to prevent the memory to
grow' Or enterprise edition can handle it better?[vbcol=seagreen]
> features and capacity. Standard edition will do just fine for your n
eeds.
> Andrew J. Kelly SQL MVP
> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> any idea. The point of availability is confused me. In fact, the stan
dard
> edition and enterprise edition is no different except?
> 512MRAM)
> cluster machine)
> version now with no complain)
> using the 6.5 version now with no complain)
> edition is easy to down?
> for SQL
> server:-
> usage:
> server|||Please read the links I posted about memory allocation algorithms in SQL Ser
ver. This is normal, and no reboot
is necessary.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> Tibor,
> My concern is how to prevent the SQL server that increase the memory usage con
tinuously? Or We need to
reboot the machine periodically? Please advise.
> Wanchun
> -- Tibor Karaszi wrote: --
> Enterprise edition has some distinct features that SE doesn't. You fi
nd them at:
> _ar_ts_1cdv.asp" target="_blank">http://msdn.microsoft.com/library/d..._ar_ts_1cdv.asp
> As for memory, please read below:
> INF: SQL Server Memory Usage
> http://support.microsoft.com/defaul...b;en-us;q321363
> http://www.mssqlserver.com/faq/trou...-memoryleak.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> edition, the memory continue to grow from 10M to 110M after I inserted 3000 r
ecords. After I re-boot
the
> machine, the memory back to 10M..... Is it I need to re-boot the machine eve
ry week to prevent the
memory to[vbcol=seagreen]
> grow' Or enterprise edition can handle it better?|||As Tibor points out that is normal behavior and will be the same for both
Std and EE.
Andrew J. Kelly SQL MVP
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> Tibor,
> My concern is how to prevent the SQL server that increase the memory
usage continuously? Or We need to reboot the machine periodically? Please
advise.
> Wanchun
> -- Tibor Karaszi wrote: --
> Enterprise edition has some distinct features that SE doesn't. You
find them at:
>
http://msdn.microsoft.com/library/d..._ar_ts_1cdv.asp[v
bcol=seagreen]
> As for memory, please read below:
> INF: SQL Server Memory Usage
> http://support.microsoft.com/defaul...b;en-us;q321363
> http://www.mssqlserver.com/faq/trou...-memoryleak.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
enterprise? I am testing with standard
> edition, the memory continue to grow from 10M to 110M after I
inserted 3000 records. After I re-boot the
> machine, the memory back to 10M..... Is it I need to re-boot the
machine every week to prevent the memory to[vbcol=seagreen]
> grow' Or enterprise edition can handle it better?
mainly[vbcol=seagreen]
your needs.[vbcol=seagreen]
message[vbcol=seagreen]
without[vbcol=seagreen]
the standard[vbcol=seagreen]
with[vbcol=seagreen]
standby or[vbcol=seagreen]
the 6.5[vbcol=seagreen]
just[vbcol=seagreen]
standard[vbcol=seagreen]
you to go[vbcol=seagreen]
sql[vbcol=seagreen]
http://www.microsoft.com/sql/techin...eskChooseEd.asp[vbcol=seagreen]
message[vbcol=seagreen]
Our[vbcol=seagreen]
2000[vbcol=seagreen]
256MRAM[vbcol=seagreen]|||Thanks again Tibor, however, if SQL used all the physical memory of the mach
ine, then the SQL can still run smoothly? or better reboot the machine?
Wanchun
-- Tibor Karaszi wrote: --
Please read the links I posted about memory allocation algorithms in SQL Ser
ver. This is normal, and no reboot
is necessary.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> Tibor,
> My concern is how to prevent the SQL server that increase the memory usage con
tinuously? Or We need to
reboot the machine periodically? Please advise.
> _ar_ts_1cdv.asp" target="_blank">http://msdn.microsoft.com/library/d..._ar_ts_1cdv.asp
> http://support.microsoft.com/defaul...b;en-us;q321363
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> edition, the memory continue to grow from 10M to 110M after I inserted 3000 r
ecords. After I re-boot
the
> machine, the memory back to 10M..... Is it I need to re-boot the machine eve
ry week to prevent the
memory to[vbcol=seagreen]
> grow' Or enterprise edition can handle it better?

Benchmark for different edition SQL 2000

We want to select the edition between standard and enterprise. Our usage
1) 10 users/application connect to the server at the same tim
2) 5000 row insert per da
3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000 serve
4) One database will be installe
5) The size of the database around 10G
Because we want to replace the existing SQL6.5 with 400MHz 256MRAM database server
Please advise. ThanksHi,
Based on your configurations and settings I will recommend you to go for SQL
Server standard edition.
Have a look into the below link in choosing the edition of sql server:-
http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
Thanks
Hari
MCDBA
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> We want to select the edition between standard and enterprise. Our usage:
> 1) 10 users/application connect to the server at the same time
> 2) 5000 row insert per day
> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000 server
> 4) One database will be installed
> 5) The size of the database around 10GB
> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
database server.
> Please advise. Thanks|||Hari
Thanks for your advice. However, I have read the page before and without any idea. The point of availability is confused me. In fact, the standard edition and enterprise edition is no different except
--Scalability ( useless to us because we only have 1 CPU machine with 512MRAM
--Availability/uptime (useless to us because we don't have a standby or cluster machine
--Performance (Time is not so critical because we are just using the 6.5 version now with no complain
--Advanced analysis ( Analysis is not so critical because we are just using the 6.5 version now with no complain
I just concern, is it enterprise edition is more stable? or standard edition is easy to down
Wanchu
-- Hari Prasad wrote: --
Hi
Based on your configurations and settings I will recommend you to go for SQ
Server standard edition
Have a look into the below link in choosing the edition of sql server:
http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.as
Thank
Har
MCDB
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com..
> We want to select the edition between standard and enterprise. Our usage
> 1) 10 users/application connect to the server at the same tim
> 2) 5000 row insert per da
> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000 serve
> 4) One database will be installe
> 5) The size of the database around 10G
>> Because we want to replace the existing SQL6.5 with 400MHz 256MRA
database server
> Please advise. Thank|||No edition is any more or less stable than any others. It is mainly
features and capacity. Standard edition will do just fine for your needs.
--
Andrew J. Kelly SQL MVP
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> Hari,
> Thanks for your advice. However, I have read the page before and without
any idea. The point of availability is confused me. In fact, the standard
edition and enterprise edition is no different except?
> --Scalability ( useless to us because we only have 1 CPU machine with
512MRAM)
> --Availability/uptime (useless to us because we don't have a standby or
cluster machine)
> --Performance (Time is not so critical because we are just using the 6.5
version now with no complain)
> --Advanced analysis ( Analysis is not so critical because we are just
using the 6.5 version now with no complain)
> I just concern, is it enterprise edition is more stable? or standard
edition is easy to down?
> Wanchun
>
> -- Hari Prasad wrote: --
> Hi,
> Based on your configurations and settings I will recommend you to go
for SQL
> Server standard edition.
> Have a look into the below link in choosing the edition of sql
server:-
> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> Thanks
> Hari
> MCDBA
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> > We want to select the edition between standard and enterprise. Our
usage:
> > 1) 10 users/application connect to the server at the same time
> > 2) 5000 row insert per day
> > 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
server
> > 4) One database will be installed
> > 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
> database server.
> > Please advise. Thanks
>
>|||Andrew
That mean from our requirement, standard edition is enough for us
Also, the memory arrangement is the same between standard and enterprise? I am testing with standard edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I re-boot the machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent the memory to grow' Or enterprise edition can handle it better
Any other Enterprise features that better than Standard
Thank
-- Andrew J. Kelly wrote: --
No edition is any more or less stable than any others. It is mainl
features and capacity. Standard edition will do just fine for your needs
--
Andrew J. Kelly SQL MV
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com..
> Hari
>> Thanks for your advice. However, I have read the page before and withou
any idea. The point of availability is confused me. In fact, the standar
edition and enterprise edition is no different except
>> --Scalability ( useless to us because we only have 1 CPU machine wit
512MRAM
> --Availability/uptime (useless to us because we don't have a standby o
cluster machine
> --Performance (Time is not so critical because we are just using the 6.
version now with no complain
> --Advanced analysis ( Analysis is not so critical because we are jus
using the 6.5 version now with no complain
>> I just concern, is it enterprise edition is more stable? or standar
edition is easy to down
>> Wanchu
>> -- Hari Prasad wrote: --
>> Hi
>> Based on your configurations and settings I will recommend you to g
for SQ
> Server standard edition
>> Have a look into the below link in choosing the edition of sq
server:
>> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.as
>> Thank
> Har
> MCDB
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com..
>> We want to select the edition between standard and enterprise. Ou
usage
>> 1) 10 users/application connect to the server at the same tim
>> 2) 5000 row insert per da
>> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 200
serve
>> 4) One database will be installe
>> 5) The size of the database around 10G
>> Because we want to replace the existing SQL6.5 with 400MHz 256MRA
> database server
>> Please advise. Thank
>>|||Enterprise edition has some distinct features that SE doesn't. You find them at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.asp
As for memory, please read below:
INF: SQL Server Memory Usage
http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> Andrew,
> That mean from our requirement, standard edition is enough for us?
> Also, the memory arrangement is the same between standard and enterprise? I am testing with standard
edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I re-boot the
machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent the memory to
grow' Or enterprise edition can handle it better?
> Any other Enterprise features that better than Standard?
> Thanks
>
>
> -- Andrew J. Kelly wrote: --
> No edition is any more or less stable than any others. It is mainly
> features and capacity. Standard edition will do just fine for your needs.
> --
> Andrew J. Kelly SQL MVP
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> > Hari,
> >> Thanks for your advice. However, I have read the page before and without
> any idea. The point of availability is confused me. In fact, the standard
> edition and enterprise edition is no different except?
> >> --Scalability ( useless to us because we only have 1 CPU machine with
> 512MRAM)
> > --Availability/uptime (useless to us because we don't have a standby or
> cluster machine)
> > --Performance (Time is not so critical because we are just using the 6.5
> version now with no complain)
> > --Advanced analysis ( Analysis is not so critical because we are just
> using the 6.5 version now with no complain)
> >> I just concern, is it enterprise edition is more stable? or standard
> edition is easy to down?
> >> Wanchun
> >> -- Hari Prasad wrote: --
> >> Hi,
> >> Based on your configurations and settings I will recommend you to go
> for SQL
> > Server standard edition.
> >> Have a look into the below link in choosing the edition of sql
> server:-
> >> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> >> Thanks
> > Hari
> > MCDBA
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> > news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> >> We want to select the edition between standard and enterprise. Our
> usage:
> >> 1) 10 users/application connect to the server at the same time
> >> 2) 5000 row insert per day
> >> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
> server
> >> 4) One database will be installed
> >> 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
> > database server.
> >> Please advise. Thanks
> >>|||Tibor
My concern is how to prevent the SQL server that increase the memory usage continuously? Or We need to reboot the machine periodically? Please advise
Wanchu
-- Tibor Karaszi wrote: --
Enterprise edition has some distinct features that SE doesn't. You find them at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.as
As for memory, please read below
INF: SQL Server Memory Usag
http://support.microsoft.com/default.aspx?scid=kb;en-us;q32136
http://www.mssqlserver.com/faq/troubleshooting-memoryleak.as
--
Tibor Karaszi, SQL Server MV
http://www.karaszi.com/sqlserver/default.as
http://www.solidqualitylearning.com
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com..
> Andrew
>> That mean from our requirement, standard edition is enough for us
> Also, the memory arrangement is the same between standard and enterprise? I am testing with standar
edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I re-boot th
machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent the memory t
grow' Or enterprise edition can handle it better
>> Any other Enterprise features that better than Standard
>> Thank
>> -- Andrew J. Kelly wrote: --
>> No edition is any more or less stable than any others. It is mainl
> features and capacity. Standard edition will do just fine for your needs
>> --
> Andrew J. Kelly SQL MV
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com..
>> Hari
>> Thanks for your advice. However, I have read the page before and withou
> any idea. The point of availability is confused me. In fact, the standar
> edition and enterprise edition is no different except
>> --Scalability ( useless to us because we only have 1 CPU machine wit
> 512MRAM
>> --Availability/uptime (useless to us because we don't have a standby o
> cluster machine
>> --Performance (Time is not so critical because we are just using the 6.
> version now with no complain
>> --Advanced analysis ( Analysis is not so critical because we are jus
> using the 6.5 version now with no complain
>> I just concern, is it enterprise edition is more stable? or standar
> edition is easy to down
>> Wanchu
>> -- Hari Prasad wrote: --
>> Hi
>> Based on your configurations and settings I will recommend you to g
> for SQ
>> Server standard edition
>> Have a look into the below link in choosing the edition of sq
> server:
>> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.as
>> Thank
>> Har
>> MCDB
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
>> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com..
>> We want to select the edition between standard and enterprise. Ou
> usage
>> 1) 10 users/application connect to the server at the same tim
>> 2) 5000 row insert per da
>> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 200
> serve
>> 4) One database will be installe
>> 5) The size of the database around 10G
>> Because we want to replace the existing SQL6.5 with 400MHz 256MRA
>> database server
>> Please advise. Thank
>>|||Please read the links I posted about memory allocation algorithms in SQL Server. This is normal, and no reboot
is necessary.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> Tibor,
> My concern is how to prevent the SQL server that increase the memory usage continuously? Or We need to
reboot the machine periodically? Please advise.
> Wanchun
> -- Tibor Karaszi wrote: --
> Enterprise edition has some distinct features that SE doesn't. You find them at:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.asp
> As for memory, please read below:
> INF: SQL Server Memory Usage
> http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
> http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> > Andrew,
> >> That mean from our requirement, standard edition is enough for us?
> > Also, the memory arrangement is the same between standard and enterprise? I am testing with standard
> edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I re-boot
the
> machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent the
memory to
> grow' Or enterprise edition can handle it better?
> >> Any other Enterprise features that better than Standard?
> >> Thanks
> >> -- Andrew J. Kelly wrote: --
> >> No edition is any more or less stable than any others. It is mainly
> > features and capacity. Standard edition will do just fine for your needs.
> >> --
> > Andrew J. Kelly SQL MVP
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> > news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> >> Hari,
> >> Thanks for your advice. However, I have read the page before and without
> > any idea. The point of availability is confused me. In fact, the standard
> > edition and enterprise edition is no different except?
> >> --Scalability ( useless to us because we only have 1 CPU machine with
> > 512MRAM)
> >> --Availability/uptime (useless to us because we don't have a standby or
> > cluster machine)
> >> --Performance (Time is not so critical because we are just using the 6.5
> > version now with no complain)
> >> --Advanced analysis ( Analysis is not so critical because we are just
> > using the 6.5 version now with no complain)
> >> I just concern, is it enterprise edition is more stable? or standard
> > edition is easy to down?
> >> Wanchun
> >> -- Hari Prasad wrote: --
> >> Hi,
> >> Based on your configurations and settings I will recommend you to go
> > for SQL
> >> Server standard edition.
> >> Have a look into the below link in choosing the edition of sql
> > server:-
> >> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> >> Thanks
> >> Hari
> >> MCDBA
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> >> We want to select the edition between standard and enterprise. Our
> > usage:
> >> 1) 10 users/application connect to the server at the same time
> >> 2) 5000 row insert per day
> >> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
> > server
> >> 4) One database will be installed
> >> 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
> >> database server.
> >> Please advise. Thanks
> >>|||As Tibor points out that is normal behavior and will be the same for both
Std and EE.
Andrew J. Kelly SQL MVP
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> Tibor,
> My concern is how to prevent the SQL server that increase the memory
usage continuously? Or We need to reboot the machine periodically? Please
advise.
> Wanchun
> -- Tibor Karaszi wrote: --
> Enterprise edition has some distinct features that SE doesn't. You
find them at:
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.asp
> As for memory, please read below:
> INF: SQL Server Memory Usage
> http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
> http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> > Andrew,
> >> That mean from our requirement, standard edition is enough for us?
> > Also, the memory arrangement is the same between standard and
enterprise? I am testing with standard
> edition, the memory continue to grow from 10M to 110M after I
inserted 3000 records. After I re-boot the
> machine, the memory back to 10M..... Is it I need to re-boot the
machine every week to prevent the memory to
> grow' Or enterprise edition can handle it better?
> >> Any other Enterprise features that better than Standard?
> >> Thanks
> >> -- Andrew J. Kelly wrote: --
> >> No edition is any more or less stable than any others. It is
mainly
> > features and capacity. Standard edition will do just fine for
your needs.
> >> --
> > Andrew J. Kelly SQL MVP
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in
message
> > news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> >> Hari,
> >> Thanks for your advice. However, I have read the page before and
without
> > any idea. The point of availability is confused me. In fact,
the standard
> > edition and enterprise edition is no different except?
> >> --Scalability ( useless to us because we only have 1 CPU machine
with
> > 512MRAM)
> >> --Availability/uptime (useless to us because we don't have a
standby or
> > cluster machine)
> >> --Performance (Time is not so critical because we are just using
the 6.5
> > version now with no complain)
> >> --Advanced analysis ( Analysis is not so critical because we are
just
> > using the 6.5 version now with no complain)
> >> I just concern, is it enterprise edition is more stable? or
standard
> > edition is easy to down?
> >> Wanchun
> >> -- Hari Prasad wrote: --
> >> Hi,
> >> Based on your configurations and settings I will recommend
you to go
> > for SQL
> >> Server standard edition.
> >> Have a look into the below link in choosing the edition of
sql
> > server:-
> >>
http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> >> Thanks
> >> Hari
> >> MCDBA
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in
message
> >> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> >> We want to select the edition between standard and enterprise.
Our
> > usage:
> >> 1) 10 users/application connect to the server at the same time
> >> 2) 5000 row insert per day
> >> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window
2000
> > server
> >> 4) One database will be installed
> >> 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz
256MRAM
> >> database server.
> >> Please advise. Thanks
> >>|||Thanks again Tibor, however, if SQL used all the physical memory of the machine, then the SQL can still run smoothly? or better reboot the machine
Wanchu
-- Tibor Karaszi wrote: --
Please read the links I posted about memory allocation algorithms in SQL Server. This is normal, and no reboo
is necessary
--
Tibor Karaszi, SQL Server MV
http://www.karaszi.com/sqlserver/default.as
http://www.solidqualitylearning.com
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com..
> Tibor
> My concern is how to prevent the SQL server that increase the memory usage continuously? Or We need t
reboot the machine periodically? Please advise
>> Wanchu
>> -- Tibor Karaszi wrote: --
>> Enterprise edition has some distinct features that SE doesn't. You find them at
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.as
>> As for memory, please read below
>> INF: SQL Server Memory Usag
> http://support.microsoft.com/default.aspx?scid=kb;en-us;q32136
>> http://www.mssqlserver.com/faq/troubleshooting-memoryleak.as
>> --
> Tibor Karaszi, SQL Server MV
> http://www.karaszi.com/sqlserver/default.as
> http://www.solidqualitylearning.com
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com..
>> Andrew
>> That mean from our requirement, standard edition is enough for us
>> Also, the memory arrangement is the same between standard and enterprise? I am testing with standar
> edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I re-boo
th
> machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent th
memory t
> grow' Or enterprise edition can handle it better
>> Any other Enterprise features that better than Standard
>> Thank
>>> -- Andrew J. Kelly wrote: --
>> No edition is any more or less stable than any others. It is mainl
>> features and capacity. Standard edition will do just fine for your needs
>> --
>> Andrew J. Kelly SQL MV
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
>> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com..
>> Hari
>> Thanks for your advice. However, I have read the page before and withou
>> any idea. The point of availability is confused me. In fact, the standar
>> edition and enterprise edition is no different except
>> --Scalability ( useless to us because we only have 1 CPU machine wit
>> 512MRAM
>> --Availability/uptime (useless to us because we don't have a standby o
>> cluster machine
>> --Performance (Time is not so critical because we are just using the 6.
>> version now with no complain
>> --Advanced analysis ( Analysis is not so critical because we are jus
>> using the 6.5 version now with no complain
>> I just concern, is it enterprise edition is more stable? or standar
>> edition is easy to down
>> Wanchu
>> -- Hari Prasad wrote: --
>> Hi
>> Based on your configurations and settings I will recommend you to g
>> for SQ
>> Server standard edition
>> Have a look into the below link in choosing the edition of sq
>> server:
>> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.as
>> Thank
>> Har
>> MCDB
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
>> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com..
>> We want to select the edition between standard and enterprise. Our
>> usage:
>> 1) 10 users/application connect to the server at the same time
>> 2) 5000 row insert per day
>> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
>> server
>> 4) One database will be installed
>> 5) The size of the database around 10GB
>> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
>> database server.
>> Please advise. Thanks
>>|||The purpose if buying memory is for it to be used. SQL Server does just that. Yes, it is normal for a SQL
Server installation to see all memory being used. :-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wanhcun" <anonymous@.discussions.microsoft.com> wrote in message
news:70CBBAD5-7E54-4EB8-9A9C-3EBDEBF2A674@.microsoft.com...
> Thanks again Tibor, however, if SQL used all the physical memory of the machine, then the SQL can still run
smoothly? or better reboot the machine?
> Wanchun
> -- Tibor Karaszi wrote: --
> Please read the links I posted about memory allocation algorithms in SQL Server. This is normal, and no
reboot
> is necessary.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> > Tibor,
> > My concern is how to prevent the SQL server that increase the memory usage continuously? Or We
need to
> reboot the machine periodically? Please advise.
> >> Wanchun
> >> -- Tibor Karaszi wrote: --
> >> Enterprise edition has some distinct features that SE doesn't. You find them at:
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.asp
> >> As for memory, please read below:
> >> INF: SQL Server Memory Usage
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
> >> http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
> >> --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> > news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> >> Andrew,
> >> That mean from our requirement, standard edition is enough for us?
> >> Also, the memory arrangement is the same between standard and enterprise? I am testing with standard
> > edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I
re-boot
> the
> > machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent
the
> memory to
> > grow' Or enterprise edition can handle it better?
> >> Any other Enterprise features that better than Standard?
> >> Thanks
> >>> -- Andrew J. Kelly wrote: --
> >> No edition is any more or less stable than any others. It is mainly
> >> features and capacity. Standard edition will do just fine for your needs.
> >> --
> >> Andrew J. Kelly SQL MVP
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> >> Hari,
> >> Thanks for your advice. However, I have read the page before and without
> >> any idea. The point of availability is confused me. In fact, the standard
> >> edition and enterprise edition is no different except?
> >> --Scalability ( useless to us because we only have 1 CPU machine with
> >> 512MRAM)
> >> --Availability/uptime (useless to us because we don't have a standby or
> >> cluster machine)
> >> --Performance (Time is not so critical because we are just using the 6.5
> >> version now with no complain)
> >> --Advanced analysis ( Analysis is not so critical because we are just
> >> using the 6.5 version now with no complain)
> >> I just concern, is it enterprise edition is more stable? or standard
> >> edition is easy to down?
> >> Wanchun
> >> -- Hari Prasad wrote: --
> >> Hi,
> >> Based on your configurations and settings I will recommend you to go
> >> for SQL
> >> Server standard edition.
> >> Have a look into the below link in choosing the edition of sql
> >> server:-
> >> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> >> Thanks
> >> Hari
> >> MCDBA
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> >> We want to select the edition between standard and enterprise. Our
> >> usage:
> >> 1) 10 users/application connect to the server at the same time
> >> 2) 5000 row insert per day
> >> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
> >> server
> >> 4) One database will be installed
> >> 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
> >> database server.
> >> Please advise. Thanks
> >>|||Tibor
This is because my machine only contain 512 MRAM... then we need to set the "maximun memory" of SQL server around 400M and let 100M memory that can be used by the OS? Please advise.Thanks...
Regards
Wanchu
-- Tibor Karaszi wrote: --
The purpose if buying memory is for it to be used. SQL Server does just that. Yes, it is normal for a SQ
Server installation to see all memory being used. :-
--
Tibor Karaszi, SQL Server MV
http://www.karaszi.com/sqlserver/default.as
http://www.solidqualitylearning.com
"Wanhcun" <anonymous@.discussions.microsoft.com> wrote in messag
news:70CBBAD5-7E54-4EB8-9A9C-3EBDEBF2A674@.microsoft.com..
> Thanks again Tibor, however, if SQL used all the physical memory of the machine, then the SQL can still ru
smoothly? or better reboot the machine
>> Wanchu
>> -- Tibor Karaszi wrote: --
>> Please read the links I posted about memory allocation algorithms in SQL Server. This is normal, and n
reboo
> is necessary
>> --
> Tibor Karaszi, SQL Server MV
> http://www.karaszi.com/sqlserver/default.as
> http://www.solidqualitylearning.com
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
> news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com..
>> Tibor
>> My concern is how to prevent the SQL server that increase the memory usage continuously? Or W
need t
> reboot the machine periodically? Please advise
>> Wanchu
>> -- Tibor Karaszi wrote: --
>> Enterprise edition has some distinct features that SE doesn't. You find them at
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.as
>> As for memory, please read below
>> INF: SQL Server Memory Usag
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;q32136
>> http://www.mssqlserver.com/faq/troubleshooting-memoryleak.as
>> --
>> Tibor Karaszi, SQL Server MV
>> http://www.karaszi.com/sqlserver/default.as
>> http://www.solidqualitylearning.com
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
>> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com..
>> Andrew
>> That mean from our requirement, standard edition is enough for us
>> Also, the memory arrangement is the same between standard and enterprise? I am testing with standar
>> edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After
re-boo
> th
>> machine, the memory back to 10M..... Is it I need to re-boot the machine every week to preven
th
> memory t
>> grow' Or enterprise edition can handle it better
>> Any other Enterprise features that better than Standard
>> Thank
>>> -- Andrew J. Kelly wrote: --
>> No edition is any more or less stable than any others. It is mainl
>> features and capacity. Standard edition will do just fine for your needs
>> --
>> Andrew J. Kelly SQL MV
>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in messag
>> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com..
>> Hari
>> Thanks for your advice. However, I have read the page before and withou
>> any idea. The point of availability is confused me. In fact, the standar
>> edition and enterprise edition is no different except
>> --Scalability ( useless to us because we only have 1 CPU machine wit
>> 512MRAM
>> --Availability/uptime (useless to us because we don't have a standby o
>> cluster machine
>> --Performance (Time is not so critical because we are just using the 6.
>> version now with no complain
>> --Advanced analysis ( Analysis is not so critical because we are just
>> using the 6.5 version now with no complain)
>> I just concern, is it enterprise edition is more stable? or standard
>> edition is easy to down?
>> Wanchun
>> -- Hari Prasad wrote: --
>> Hi,
>> Based on your configurations and settings I will recommend you to go
>> for SQL
>> Server standard edition.
>> Have a look into the below link in choosing the edition of sql
>> server:-
>> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
>> Thanks
>> Hari
>> MCDBA
>>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
>> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
>> We want to select the edition between standard and enterprise. Our
>> usage:
>> 1) 10 users/application connect to the server at the same time
>> 2) 5000 row insert per day
>> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
>> server
>> 4) One database will be installed
>> 5) The size of the database around 10GB
>> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
>> database server.
>> Please advise. Thanks
>>|||The fact that you only have 512 MB doesn't change the memory allocation algorithms. SQL Server will use the
memory in the machine (but of course leave space for OS and a little bit more). But sure, you can set a max if
you absolutely want to...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:3D73FA4A-D85C-40BF-BC30-D2F32E57602B@.microsoft.com...
> Tibor,
> This is because my machine only contain 512 MRAM... then we need to set the "maximun memory" of SQL server
around 400M and let 100M memory that can be used by the OS? Please advise.Thanks....
> Regards,
> Wanchun
> -- Tibor Karaszi wrote: --
> The purpose if buying memory is for it to be used. SQL Server does just that. Yes, it is normal for a
SQL
> Server installation to see all memory being used. :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wanhcun" <anonymous@.discussions.microsoft.com> wrote in message
> news:70CBBAD5-7E54-4EB8-9A9C-3EBDEBF2A674@.microsoft.com...
> > Thanks again Tibor, however, if SQL used all the physical memory of the machine, then the SQL can
still run
> smoothly? or better reboot the machine?
> >> Wanchun
> >> -- Tibor Karaszi wrote: --
> >> Please read the links I posted about memory allocation algorithms in SQL Server. This is
normal, and no
> reboot
> > is necessary.
> >> --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> > news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> >> Tibor,
> >> My concern is how to prevent the SQL server that increase the memory usage continuously? Or We
> need to
> > reboot the machine periodically? Please advise.
> >> Wanchun
> >> -- Tibor Karaszi wrote: --
> >> Enterprise edition has some distinct features that SE doesn't. You find them at:
> >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.asp
> >> As for memory, please read below:
> >> INF: SQL Server Memory Usage
> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
> >> http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> >> Andrew,
> >> That mean from our requirement, standard edition is enough for us?
> >> Also, the memory arrangement is the same between standard and enterprise? I am testing with
standard
> >> edition, the memory continue to grow from 10M to 110M after I inserted 3000 records. After I
> re-boot
> > the
> >> machine, the memory back to 10M..... Is it I need to re-boot the machine every week to prevent
> the
> > memory to
> >> grow' Or enterprise edition can handle it better?
> >> Any other Enterprise features that better than Standard?
> >> Thanks
> >>> -- Andrew J. Kelly wrote: --
> >> No edition is any more or less stable than any others. It is mainly
> >> features and capacity. Standard edition will do just fine for your needs.
> >> --
> >> Andrew J. Kelly SQL MVP
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> >> Hari,
> >> Thanks for your advice. However, I have read the page before and without
> >> any idea. The point of availability is confused me. In fact, the standard
> >> edition and enterprise edition is no different except?
> >> --Scalability ( useless to us because we only have 1 CPU machine with
> >> 512MRAM)
> >> --Availability/uptime (useless to us because we don't have a standby or
> >> cluster machine)
> >> --Performance (Time is not so critical because we are just using the 6.5
> >> version now with no complain)
> >> --Advanced analysis ( Analysis is not so critical because we are just
> >> using the 6.5 version now with no complain)
> >> I just concern, is it enterprise edition is more stable? or standard
> >> edition is easy to down?
> >> Wanchun
> >> -- Hari Prasad wrote: --
> >> Hi,
> >> Based on your configurations and settings I will recommend you to go
> >> for SQL
> >> Server standard edition.
> >> Have a look into the below link in choosing the edition of sql
> >> server:-
> >> http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> >> Thanks
> >> Hari
> >> MCDBA
> >>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> >> We want to select the edition between standard and enterprise. Our
> >> usage:
> >> 1) 10 users/application connect to the server at the same time
> >> 2) 5000 row insert per day
> >> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window 2000
> >> server
> >> 4) One database will be installed
> >> 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz 256MRAM
> >> database server.
> >> Please advise. Thanks
> >>|||The max memory only sets an upper limit for the memory pool. There is an
area called the mem to leave that gets allocated first. By default it can
use to to 256MB so if you set the max memory to 400 you will most likely
still swap with the OS. While it may be better than not changing anything I
would set it even lower. You stated you only do 5000 inserts a day so you
should not require a lot of memory to operate properly. Try setting it to
300MB and see if that helps. Memory is cheap these days and you might want
to look into adding more later on.
--
Andrew J. Kelly SQL MVP
"Wanchun" <anonymous@.discussions.microsoft.com> wrote in message
news:3D73FA4A-D85C-40BF-BC30-D2F32E57602B@.microsoft.com...
> Tibor,
> This is because my machine only contain 512 MRAM... then we need to set
the "maximun memory" of SQL server around 400M and let 100M memory that can
be used by the OS? Please advise.Thanks....
> Regards,
> Wanchun
> -- Tibor Karaszi wrote: --
> The purpose if buying memory is for it to be used. SQL Server does
just that. Yes, it is normal for a SQL
> Server installation to see all memory being used. :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Wanhcun" <anonymous@.discussions.microsoft.com> wrote in message
> news:70CBBAD5-7E54-4EB8-9A9C-3EBDEBF2A674@.microsoft.com...
> > Thanks again Tibor, however, if SQL used all the physical memory of
the machine, then the SQL can still run
> smoothly? or better reboot the machine?
> >> Wanchun
> >> -- Tibor Karaszi wrote: --
> >> Please read the links I posted about memory allocation
algorithms in SQL Server. This is normal, and no
> reboot
> > is necessary.
> >> --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in
message
> > news:DF073FD2-4A17-4122-BCEC-E9FB5E5AF5EF@.microsoft.com...
> >> Tibor,
> >> My concern is how to prevent the SQL server that increase the
memory usage continuously? Or We
> need to
> > reboot the machine periodically? Please advise.
> >> Wanchun
> >> -- Tibor Karaszi wrote: --
> >> Enterprise edition has some distinct features that SE
doesn't. You find them at:
> >>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.asp
> >> As for memory, please read below:
> >> INF: SQL Server Memory Usage
> >>
http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
> >>
http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in
message
> >> news:36E3DDB7-B674-4AFA-8A7C-3B7C1A336E3E@.microsoft.com...
> >> Andrew,
> >> That mean from our requirement, standard edition is enough for
us?
> >> Also, the memory arrangement is the same between standard and
enterprise? I am testing with standard
> >> edition, the memory continue to grow from 10M to 110M after I
inserted 3000 records. After I
> re-boot
> > the
> >> machine, the memory back to 10M..... Is it I need to re-boot
the machine every week to prevent
> the
> > memory to
> >> grow' Or enterprise edition can handle it better?
> >> Any other Enterprise features that better than Standard?
> >> Thanks
> >>> -- Andrew J. Kelly wrote: --
> >> No edition is any more or less stable than any others. It
is mainly
> >> features and capacity. Standard edition will do just fine
for your needs.
> >> --
> >> Andrew J. Kelly SQL MVP
> >> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in
message
> >> news:8E5E6311-B5DF-4D1E-9797-92DD6413C57C@.microsoft.com...
> >> Hari,
> >> Thanks for your advice. However, I have read the page before
and without
> >> any idea. The point of availability is confused me. In fact,
the standard
> >> edition and enterprise edition is no different except?
> >> --Scalability ( useless to us because we only have 1 CPU
machine with
> >> 512MRAM)
> >> --Availability/uptime (useless to us because we don't have a
standby or
> >> cluster machine)
> >> --Performance (Time is not so critical because we are just using
the 6.5
> >> version now with no complain)
> >> --Advanced analysis ( Analysis is not so critical because we are
just
> >> using the 6.5 version now with no complain)
> >> I just concern, is it enterprise edition is more stable? or
standard
> >> edition is easy to down?
> >> Wanchun
> >> -- Hari Prasad wrote: --
> >> Hi,
> >> Based on your configurations and settings I will recommend
you to go
> >> for SQL
> >> Server standard edition.
> >> Have a look into the below link in choosing the edition of
sql
> >> server:-
> >>
http://www.microsoft.com/sql/techinfo/planning/SQLReskChooseEd.asp
> >> Thanks
> >> Hari
> >> MCDBA
> >>> "Wanchun" <anonymous@.discussions.microsoft.com> wrote in
message
> >> news:08540023-9C99-4569-9A26-F765151912A2@.microsoft.com...
> >> We want to select the edition between standard and enterprise.
Our
> >> usage:
> >> 1) 10 users/application connect to the server at the same time
> >> 2) 5000 row insert per day
> >> 3) Our machine is only 1CPU 2.6GHz and 512 MB RAM with window
2000
> >> server
> >> 4) One database will be installed
> >> 5) The size of the database around 10GB
> >> Because we want to replace the existing SQL6.5 with 400MHz
256MRAM
> >> database server.
> >> Please advise. Thanks
> >>