X64 or IA64

Question

Wasn't sure whether to post this on the SQL forum but feel it is relevant especially as regards SQL 2005.
We're currently running SAP R/3 4.7 on W2K3 and SQL2000 on x86 hardware. The application servers are already running on 64-bit hw, o/s and SAP kernel. The next step is for us to upgrade the backend CI and database server platform to 64-bit hw, o/s and SQL 2005.
In our case, the preferred target is industry standard HP D585 servers running 4-way AMD64 dual-core CPUs and W2K3 64-bit. More specifically the very latest DL585's that will have the upgrade path to quad-core when it is released.
We are also considering the Integrity/Itanium option and this is what I'd be interested in people's views on.
Basically, from a pure SAPS sizing point of view the dual-core DL585 give us plenty of scope for growth, especially with the quad-core upgrade available. So there's no reason to choose Integrity from a pure power point of view. Yes, there may well be a time (4 years + away) when we outgrow the 585 but maybe we think about that nearer the time.
The alternative - and there are other drivers for this which I'll explain - would be to put in two superdomes now and grown into them. The other key driver is that we will shortly be starting BW and EP projects which will require their own infrstructure. Consolidating all of this onto 2 Integrity's is obviously quite appealing. And expensive. Haven't got the exact price details in yet but reckon is about 50% more for equivalent SAPS. Mmmm. Tricky one. (50% more of the X64 option isn't necessarily a huge number but still more)
Any thoughts?

Answer 1

Hi NPC,
Thanks for your response. Yes, I would be interested in a more detailed review.
Our R/3 Production System is currently 2.2TB used and growing at around 100GB per month. So I'd expect to be 3TB by next summer.
We have about 150 concurrent users (600 named) and this may grow to 600 concurrent by 2Q 2008.
In terms of availability we're currently live in two timezones - GMT (BST) and JST (Tokyo). The next implementation on the single instance will be to U.S - New York and LA.
We have 3 hours of planned maintenance a month and 24 hours reserved every quarter - although we don't always use this. I would expect these availability requirements to remain broadly the same even with the USA on board. In  temrms of unplanned downtime our SLA target is Achieve > 99.5 % of planned availability, however, we aim much higher and unplanned downtime is rare.
It would be interesting to hear your views on a comparison of the two architectures.
My own personal view has always been to regard Integrity as an expensive, proprietary technology that not many people purchased. The recent HP Integrity Event in London would have you believe otherwise but then why would they go to so much effort if it was selling well?
The key advantage I can see for us would be that it would allow us a greater level of flexibility in the face of rapidly changing and often increasing requirements. It would also I imagine reduce the frequency of technology refreshes as we could remain on a common platform and still scale up the DB server CPU beyond that available on a 585.
Anyway, look forward to hearing from you.
Thanks,
CJH