November 16, 2010 at 9:28 am
Hi folks,
Myself and a collegue are in a situation where we have prototyped a system using SQL Server 2008R2 developer edition to provide a view of what 'could' be done.
We are now in the position where there is a desire to take what we have prototyped and to 'productionise it'
The system takes Near real-time feeds from disparate automation equipment spread around the UK (about 1000 machines) at around 5 minute intervals, carries out an ETL process qritten in VB.NET which stages the data. Then it is promoted into reporting tables.
It is currently running on a dual processor 2x 2.8 Xeon with 8GB RAM.
The inbound data volumes are high interms of transactions - 100,000 files per day/nightWe need to take this proof of concept and scale it to support 1200 users with a concurrency of 300-500.
Price is of course key but I am struggling to work out how to size and structure the solution. I believe that we probably need a couple of SQL server and a couple of scaled-out reporting services servers with some sort of NLB server but this is speculation on my part.
The licensing costs in the above example appear to be horrendous as if we put Enterprise edition on each box we would need a license per-processor and at 27500 dollars per CPU this seems expensive.
All ideas gratefully received..
Regards
Steve
November 18, 2010 at 9:02 am
steve.pritchard 25079 (11/16/2010)
The inbound data volumes are high interms of transactions - 100,000 files per day/nightWe need to take this proof of concept and scale it to support 1200 users with a concurrency of 300-500.
Concurrency probably isnt going to be an issue. How you benchmarked your system? Do you know the transactions volumes in terms of data size? How frequently are the clients going to query the databases and what volumes of data are they retrieving?
steve.pritchard 25079 (11/16/2010)
Price is of course key but I am struggling to work out how to size and structure the solution. I believe that we probably need a couple of SQL server and a couple of scaled-out reporting services servers with some sort of NLB server but this is speculation on my part.
This would help prevent import contention. I would look at transactional replication as you suggest multiple scaled out servers. This isnt necessarily required and you may find it is more cost effective to buy a single highly specced server and a single sql server license (per CPU) and tune your import/client queries.
steve.pritchard 25079 (11/16/2010)
The licensing costs in the above example appear to be horrendous as if we put Enterprise edition on each box we would need a license per-processor and at 27500 dollars per CPU this seems expensive.
Are you using any of the Enterprise features to justify this cost or will standard edition work for you?
November 18, 2010 at 9:53 am
I agree... scale UP a box for SQL Server and move SSRS to its own server as you will likely have to scale SSRS OUT. No mention of your considerations on purchasing fast disks, but sounds like you are going to have to handle a lot of writes; i'd plan on alot of spindles.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply