What features are the experts looking at? These things: Is the report development mechanism robust enough for power users? Gile finds the report development function of Reporting Services to be "pretty lame," since it requires a Visual Studio .Net add-in. Berry was concerned about the same thing, but when his people got it into the lab, they found that there are a number of third-party tools you can swap in for use as a front end, such as those from ProClarity. Such tools give you much easier interfaces to work with, Berry said.This isnt Microsofts fault per se and instead has to do with how architectures have evolved, as vendors have attempted to shield hapless end users from the complexity of working in too close a proximity to the convoluted back end of the database. Thus we get tools from Brio, Cognos and Hyperion that are, as Khartabil put it, self-serving from a database standpoint, grabbing data from databases and staging it for reporting. But then came upstarts such as Brio and Crystal, which allowed users to go directly against the database and get reports fast. Now, we have a situation where every company has its own approach with metadata schemes, since all of those metadata layers are proprietary and prevent sharing. Microsoft isnt to blame, but it could and perhaps should take the lead in creating adapters that allow users to seamlessly share reports back and forth. One thing thats holding up others from working in that direction is what Gile says is a paranoia within BI vendors who think that opening up to Microsoft would put them out of business. An understandable fear, but one thats likely short-sighted. What will bring us to the holy grail of switching between reporting tools? XML-based reporting, of course. Berry said he knows of at least one company thats got a potential XML-based solution, so keep your eyes peeled for announcements in that direction. Tight integration with Office components. Enterprises now need Office developers, Visual Studio developers and SQL Server DBAs, Gile noted. Why isnt Microsofts Office group working more closely with the SQL Server group to make life more cost-effective? Why does the Office group have separate drivers? Why is it a separate group at all? If BI vendors are shaking now, just wait until the day when Microsoft pulls all of its disparate parts together and turns out BI tools that bridge the gap between all of those technology islands. Write to me at firstname.lastname@example.org. eWEEK.com Associate Editor Lisa Vaas has written about enterprise applications since 1997. Check out eWEEK.coms Database Center at http://database.eweek.com for the latest database news, reviews and analysis.
No sharing of metadata between reporting platforms. Many of the various proprietary platforms create their own metadata level, meaning you cant leverage that data component from one tool to another. You cant create a Reporting Services report, hit a button and bring it up to work on in Crystal, for instance.