February 27, 2015 at 9:22 am
Good staff late!
In April/15 will begin testing for migration of our ERP Dynamics AX 2009 to 2012 version.
Today we have the Microsoft SQL Server 2008 R2 (SP3) - 10.50.6000.34 (X64).
We have a server with 2 processors octacore, totaling 16 cores.
Because of the new license value SQL 2014, we think that making the Standard version rather than the Enterprise.
What would it mean in terms of this limitations Standard version in relation to the Enterprise?
hugs,
Mateus
February 27, 2015 at 9:37 am
Many things change from Standard to Enterprise.
Here's a full feature comparison: https://msdn.microsoft.com/en-us/library/cc645993.aspx
-- Gianluca Sartori
February 27, 2015 at 12:42 pm
matfurrier (2/27/2015)
Good staff late!In April/15 will begin testing for migration of our ERP Dynamics AX 2009 to 2012 version.
Today we have the Microsoft SQL Server 2008 R2 (SP3) - 10.50.6000.34 (X64).
We have a server with 2 processors octacore, totaling 16 cores.
Because of the new license value SQL 2014, we think that making the Standard version rather than the Enterprise.
What would it mean in terms of this limitations Standard version in relation to the Enterprise?
hugs,
Mateus
Do you use online rebuilding? Do you use table partitioning?
There are much more differences, but those two (besides max memory settings) are probably the ones that push people more to one or the other.
February 27, 2015 at 12:45 pm
Thanks for the feedback.
We do not use online reconstruction and also do not use table partitioning .
We are concerned with the performance, as the DAX 2012 is more robust.
February 27, 2015 at 12:58 pm
matfurrier (2/27/2015)
Thanks for the feedback.We do not use online reconstruction and also do not use table partitioning .
We are concerned with the performance, as the DAX 2012 is more robust.
My suggestion: get some performance metrics using Perfmon. Let it run for a day. Or, even better, collect data for a week. Capture CPU, RAM, Network, Several SQL counters. Once you are done with that, you may have a better picture of what your system uses and what are your hot areas.
We moved from metal to VMware 2 years ago and on my case, our SQL servers had disk bottleneck. RAM was 2nd and we did not have CPU problems with those bare metal servers.
On your case, if you establish a baseline and you see that your SQL servers require lots of RAM, any downgrade may be detrimental, as you may not be able to squeeze that last drop of available RAM due Standard edition limitations.
You should read Microsoft comparison between both. But what I really miss from Enterprise (I used to have that in my previous job) is the amount of RAM, based on hardware, that I was able to use for my databases.
February 27, 2015 at 1:59 pm
Yep. To me, the RAM restrictions and the lack of data compression are the big factors in Standard Edition. Snapshots not being available isn't that bad, although it does effect how efficiently CHECKDB can run.
If you use SSRS, the lack of data driven report subscriptions is really crippling. You might consider BI edition just for that feature, if you need it.
SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.
February 27, 2015 at 4:34 pm
ScottPletcher (2/27/2015)
Snapshots not being available isn't that bad, although it does effect how efficiently CHECKDB can run.
CHECKDB runs on a snapshot on all editions. What you lose in STD is the ability to create the snapshot manually and run CHECKDB against it.
-- Gianluca Sartori
February 28, 2015 at 2:36 am
Quick point, run this query on the existing server to list the enterprise features in use
😎
SELECT
PF.feature_id
,PF.feature_name
FROM sys.dm_db_persisted_sku_features PF;
March 2, 2015 at 5:10 am
Good day.
By select no corporate resources in use.
My major concern in itself, is that there may be a very great limitation in Standard version with respect to Enterprise for the AX 2012.
Today our servers are virtual and physical intend to leave them because they say that you can have a gain of 25% performace with it.
I believe that we will continue with SQL 2008 Enterprise same because an update is with the highest value.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply