Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Jaapie
Starting Member
7 Posts |
 Posted - 2005-03-31 : 05:04:52
|
| I am wanting to maximise server resources whilst not having to outlaylarge sums of money for Ent. edition.I have a DB that will be around 800GB. The server 4 X CPU, 5GB RAMI was thinking of running to sql instances of STD. edition allocatingeach 2GB RAM leaving 1GB for OS , using CPU affinity (2 per instance) and having each instance on a seperate HDD Raid array on seperate Controler channels.We estimate average write/read I/O (if you can quantify average)Has anyone done a similar setup, whats performace like, am I mad and do I just outlay for ent. edition for that size DB. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-04-01 : 13:55:18
|
| 5GB of RAM is extremely limiting for a database that is going to be around 800GB. You really should reconsider using Enterprise Edition. I'd recommend Win2k3 with SQL Server 2000 Ent. Edition. I'd also recommend that you look into partitioned views over federated database servers to improve performance. 800GB is going to be a major performance problem if you don't plan for it now.Tara |
 |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2005-04-01 : 19:37:22
|
Also, if you use standard edition, you have to pay for each instance. You would eat up any money you're saving very quickly. RAM, RAM, RAM The value of it can't be overstated. Usable RAM is well worth the price of Ent Edition for a database that size.quote:
We estimate average write/read I/O (if you can quantify average)
You can't. You'll have to be way more specific than that for any type of real help. Besides, that's more related to disk and network capacity than memory. Memory is related to processing requests and efficiency of cache for serving data and plans. That's where your real issue lies on trying to run fairly large databases on small amounts of RAM.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-04-02 : 02:39:28
|
| what sort of application is this for? is this a datawarehouse or an oltp environment?-ec |
|
|
|
scullee
Posting Yak Master
103 Posts |
Posted - 2005-04-02 : 03:26:33
|
| Your other option is to wait until 2005 comes out, sql 2005 std doesnt have the ram limitation. |
|
|
|
Jaapie
Starting Member
7 Posts |
Posted - 2005-04-06 : 10:22:39
|
| thanks for all your inputIt is OLTP and maybe best would be to wait till SQL 2005But it all comes down to big deliverables = bigger budgetCutting corners will cost in the long runthanks again |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2005-04-06 : 13:56:48
|
quote:
But it all comes down to big deliverables = bigger budgetCutting corners will cost in the long run
Nice to hear a new poster understand this.  MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
|
|
|
|
|
SQL Instances