What SQL Server edition should we be using
-
Hi Everyone,
I'm not an SQL Server expert and I'm looking for some help.
We outsource our IT and were told that to take advantage of the 16GB RAM on our server (Windows 2003 Enterprise Edition) we would need to use SQL Server Enteprise Edition. From the reading I've done this doesn't seem to be the case: we could use SQL Server Standard Edition and still take advantage of the extra memory. Given the huge difference in cost it doesn't seem smart to go to Enterprise Edition unless we need to.
Just a bit about what we're doing with SQL Server - it supports a single application that will be used by about 30 people around the world (ie only about 10 maximum at any one time); the projected growth is only about 4GB per year; and it runs on a single dual core, dual CPU server.
Any advice would be very welcome.
Thanks
Wendy
-
As Standard Edition supports a maximum of 2Gb of memory, the outsourcing vendor is correct that Enterprise edition must be used.
SQL = Scarcely Qualifies as a Language
-
Scalability and Performance Feature Express Workgroup Standard Enterprise Comments Number of CPUs
1
2
4
No Limit
Includes support for multicore processors.
RAM
1 gigabyte (GB)
3 GB
Operating system maximum
Operating system maximum
Memory limited to maximum supported by operating system.
64-bit Support
Windows on Windows (WOW)
WOW
Database Size
4 GB
No Limit
No Limit
No Limit
Partitioning
Support for large-scale databases
Parallel Index Operations
Parallel processing of indexing operations
Indexed Views
Indexed view creation is supported in all editions. Indexed view matching by the query processor is supported only in Enterprise Edition.
The 2GB limit went out with Sql2000.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again? -
Seems to me, based on the chart that Matt posted and the low volume of your anticipated connection/data plans, standard edition would do.
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally) -
Hmm... I guess that part of the response got chopped off.
What Jeff Said!
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again? -
Windows 2003 (Standard) 64bit and SQL Server 2005 (Standard) 64bit will both address 16gb of RAM. This is assuming you are running on 64bit processor(s).
-
Thanks everyone, you've certainly answered all my questions.
-
There used to be a limitation of memory of 2GB for standard edition, but that is no longer the case for 2005 as the chart indicates.
Steve
-
with 64 bit sql 2005 standard will support ludicrous amounts of memory. the only real differences are online indexing and a few other features that you need in a 24x7 operation
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply