674 Delivering Business Intelligence with Microsoft SQL Server 2005
If you want to make beautiful music, you must play the black and the white notes
—Richard Milhous Nixon
eporting Services provides us with a capable tool for delivering Business
Intelligence (BI) to decision makers. In some situations, however, our
business intelligence solution must be more than a paper report; even more
than an interactive report available in a browser. At times, our business intelligence
must integrate tightly with other programs and solutions.
Once again, SQL Server 2005 provides us with the tools to fulﬁ ll this need. The
ADOMD.NET data provider enables us to execute MDX queries against OLAP
cubes on Analysis Services servers. Analysis Management Objects (AMO) provides
a programming interface for the management of an Analysis Services server and the
objects residing on that server. Reporting Services offers a number of methods for
integrating reports with applications.
With these features, we can provide our users with the complete package, the
integrated solution, the all-in-one application, the tightly coupled, well-oiled . . . well,
you get the picture.
ADOMD.NET, the multidimensional counterpart to ADO.NET, is our means to
programmatically access the wealth of business intelligence we have been creating
on the Analysis Services server. With ADOMD.NET, our client applications can
query databases on an Analysis Services server. ADOMD.NET also allows these
applications to programmatically view and manipulate the structures residing in
Analysis Services databases.
ADOMD.NET uses XML for Analysis (XML/A) to interact with the Analysis
The structure of ADOMD.NET is similar to the structure of ADO.NET. Both use a
connection object to manage the connection string and set up access to the server.
And both use a command object to execute queries against a database. And both
provide structures for connected and disconnected access to data.