I'm not an expert on OLAP or SQL Server, but I do know that SQL Server 2005 offers significantly better support for SOAP than SQL Server 2000 did. It also includes a lot more native OLAP capabilities. One would hope that you should be able to use your existing XMLA application with SQL Server 2005 without code modification—assuming that Microsoft continues to support XMLA. (The XMLA.org group has been pretty quite since 2002.) XMLA uses RPC/encoded, so from a Java client perspective, you need to use SAAJ or JAX-RPC rather than JAX-WS. RPC/encoded often causes interoperability problems, but considering that you have a working application based on SQL Server 2000, I'm thinking that interoperability won't be your issue. If you encounter problems, it would be because Microsoft changed its support of XMLA.
You might try asking this question on a BI discussion list.
Dig Deeper on Service-oriented architecture (SOA)
Related Q&A from Anne Thomas Manes
Anne Thomas Manes explains the differences between open source clients and open source implementations. Continue Reading
Anne Thomas Manes discusses the best way to go about creating an enterprise data dictionary and why the systems works well. Continue Reading
Anne Thomas Manes explains the difference between 'hard' real time and 'live' real time systems. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.