Future of OLEDB for OLAP and XMLA
From: gabhan (gabhan_at_discussions.microsoft.com)
Date: 10/27/04
- Previous message: PeteSweden: "Deserialization, java and xmla"
- Next in thread: Jéjé: "Re: Future of OLEDB for OLAP and XMLA"
- Reply: Jéjé: "Re: Future of OLEDB for OLAP and XMLA"
- Reply: Akshai Mirchandani [MS]: "Re: Future of OLEDB for OLAP and XMLA"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 27 Oct 2004 12:51:03 -0700
I am interested in peoples' opinions on the future of OLEDB for OLAP and XMLA.
XMLA seems great for interoperability but does not match MSOLAP and PTS on
LAN speed networks. Sure, http compression can help ... but still, XMLA still
(in my experince at least) is slower.
What will MS offer with Yukon? If MS use XMLA internally within the next
MSOLAP provider then would there be any point in third parties using it
rather than writing their own client using the XMLA protocol directly? If the
MSOLAP provider simply mapped the OLEDB for OLAP calls to XMLA calls then
surely clients should just use XMLA directly .. (an easier API to code
against)? Also, if this is the case, wouldn't the Yukon MS provider be slower
on LAN speed networks than the current MSOLAP.2 provider?
Or will Yukon provide a means for clients to continue to use a binary
protocol over the wire and offer XMLA as an addition?
Can anyone from MS shed some light here?
- Previous message: PeteSweden: "Deserialization, java and xmla"
- Next in thread: Jéjé: "Re: Future of OLEDB for OLAP and XMLA"
- Reply: Jéjé: "Re: Future of OLEDB for OLAP and XMLA"
- Reply: Akshai Mirchandani [MS]: "Re: Future of OLEDB for OLAP and XMLA"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|