SQL Server Edition

aliasghar

Hi.
I have data of around 55-60 GB, We have around 25 user which can in future go to 50. I want to know which edition of SQL server I will use(standrad or enterprise). :?:



Thanks in advance

kine

May be it is just question of your budget :-) Are you talking about MS SQL 2000 or MS SQL 2005?

ssingla

Ali is looking for SQL Server 2005.

kine

In this case, if you look at this table:http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx

You will find out that Enterprise is for Nav same as Standard with only one difference - Standard support just 4 CPUs. Other features are not used in NAW.

Nobody

A popular combinmation for NAV is SQL Server 2005 x64 Stnd Edition with Windows Server 2003 R2 x64 Stnd Edition. This will support upto 32 gigs of RAM, 4 processors sockets (not cores you can use 4 dual cores or 4 quad cores or 4 single cores), and a 2 node cluster.

This is so much better than SQL 2000 where if you wanted to use more than 1.7 gigs of RAM you had to buy SQL Enterprise which cost two - three times as much.

ssingla

Thanks for the info.

kriki

[Topic moved from Navision forum to SQL General forum]

Heltborg

Been checking up on MS homepage on win 2003 x64 std edt. As far as i can find std. edt. doesnt support cluster only NLB. Need to buy win 2003 ent. edt. to get the cluster support

But you can use SQL 2005 std edt. as database server on top on 2003 ent edt.

Bo Heltborg

Nobody

Windows Server clustetring and SQL Server Failover clustering are two different things.

Heltborg

In order to support SQL server failover clustering you need to install MSCS.

Windows 2003 server x64 std edition do not support this. So if you want to implement SQL 2005 failover cluster you need windows 2003 ent. edt. not standard edt.

http://msdn2.microsoft.com/en-us/librar ... 910(SQL.90).aspx

colin_leversuch-roberts

you should make sure you go full 64bit as the memory model being flat gives you gains all around, basically gets rid of that 2gb memory limit .
For a small database you'll probably not gain much using Enterprise SQL and you could spend the money saved on licensing on memory and storage and get much better ROI. A four way dual core is effectively an 8 way box which I'd probably say was way over the top for a 50 user system - before dual core I'm sure you'd never have made a choice for an 8 way box. Most of the real benefits of multiple cores/procs are exploited by ent sql btw. I'd suggest a 2 way dual core and spend the money on memory and fast storage - I'm running a terrabyte + several hundred users on a four way ( single core box ) Don't be led into over specifying server hardware.