SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


New server configuration. SQL Standard vs Enterprise question


New server configuration. SQL Standard vs Enterprise question

Author
Message
bcmat
bcmat
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 6
Hello. We are getting a new server with the following specs:

Dell PowerEdge R710
12GB Memory 1333MHZ
(2) Xeon E5503, 2.0GHZ, 4M Chache, 800MHZ, Max Mem Processors

We need to run SQL 2000 and possibly SQL 2005. I am planning on turning this into a virtual server. I would like to get the most robust SQL environment and trying to decide on SQL Enterprise vs Standard. My question revolves around the processors.

If I creat a Virtual server with:
-64 Bit Server 2003
-6 GB Ram
-2 Processors

What should I do with SQL? Should I get enterprise version so it can use more than 2gb of RAM? I noticed that enterprise is only licensed for 1 processor. Am I correct in assuming that SQL 2000 Standard will use both processors, but only 2gb of RAM. But, SQL Enterprise will use only one processor but more than 2gb of RAM? Do I have to decide on Processor power vs memory power?

Any other words of wisdom related to my setup would be greatly appreciated.
Sqlchicken
Sqlchicken
Mr or Mrs. 500
Mr or Mrs. 500 (579 reputation)Mr or Mrs. 500 (579 reputation)Mr or Mrs. 500 (579 reputation)Mr or Mrs. 500 (579 reputation)Mr or Mrs. 500 (579 reputation)Mr or Mrs. 500 (579 reputation)Mr or Mrs. 500 (579 reputation)Mr or Mrs. 500 (579 reputation)

Group: General Forum Members
Points: 579 Visits: 671
Standard edition can support up to 64 GB of memory: http://msdn.microsoft.com/en-us/library/ms143685.aspx

As far as deciding CPU vs Memory it depends on what your systems are doing. Are your processes CPU bound (i.e. lots of aggregations)? If not, with SQL Server more memory is pretty much always better. Some things to watch out for when virtualizing is that when you setup the VM with X amount of memory, talk with your VM admin and make sure you're ACTUALLY getting that much. VM admins can restrict how much memory your system actually uses as opposed to how much it "sees", same thing goes with processing power.

Also why do you need to run SQL 2000 and SQL 2005? Can your 2000 databases just live on 2005 instance and the databases stay running in 2000 compatibility mode? If so, try that out. Also if you're separating versions for the sake of breaking them apart, look into creating named instances on the highest version level you can and have your applications point there instead. Hopefully this makes sense and helps you out.

=============================================================
/* Backups are worthless, Restores are priceless */

Get your learn on at SQL University!
Follow me on Twitter | Connect on LinkedIn
My blog: http://sqlchicken.com
My book: Pro Server 2008 Policy-Based Management
Elliott Whitlow
Elliott Whitlow
SSC-Insane
SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)

Group: General Forum Members
Points: 24812 Visits: 5314
bcmat (5/13/2011)
Hello. We are getting a new server with the following specs:

Dell PowerEdge R710
12GB Memory 1333MHZ
(2) Xeon E5503, 2.0GHZ, 4M Chache, 800MHZ, Max Mem Processors

We need to run SQL 2000 and possibly SQL 2005. I am planning on turning this into a virtual server. I would like to get the most robust SQL environment and trying to decide on SQL Enterprise vs Standard. My question revolves around the processors.

If I creat a Virtual server with:
-64 Bit Server 2003
-6 GB Ram
-2 Processors

What should I do with SQL? Should I get enterprise version so it can use more than 2gb of RAM? I noticed that enterprise is only licensed for 1 processor. Am I correct in assuming that SQL 2000 Standard will use both processors, but only 2gb of RAM. But, SQL Enterprise will use only one processor but more than 2gb of RAM? Do I have to decide on Processor power vs memory power?

Any other words of wisdom related to my setup would be greatly appreciated.
I gotta say that going virtual might be a bit troubling. You have 2procs X 2cores/proc and only 12GB of RAM. You could build a couple probably not more than 4 servers total and more like 2-3. Enterprise is licensed BY processor, so $ x Procs, so in your case $ x 2 if you run it on bare metal. In a virtual environment you will need to reference: http://download.microsoft.com/download/2/7/0/270B6380-8B38-4268-8AD0-F480A139AB19/SQL2008R2_LicensingQuickReference-updated.pdf Which basically says if you want to only license 1 processor in a virtualized scenario you can.
Any of the editions can use more than 2GB of RAM but it is easier to do with 64-bit implementations.

If you are going to virtualize don't build the host OS as less than 2008, guest OSs can be something else, but don't handicap yourself at the host side.

CEWII
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search