Instead, they say, "Im doing my job today." Thats the mass audience Microsoft is targeting with its latest business intelligence offerings, which include new SQL Server Report Packs for Exchange and Business Solutions CRM; Report Builder, a tool that enables simple report creation via a drag-and-drop environment; and Integration Services, which is a rechristened version of DTS (Data Transformation Services) that will reach into nonpersistent data stores such as those found in RSS (Really Simple Syndication) feeds or Web services.
Baker sat down with eWEEK.com Associate Editor Lisa Vaas at the PASS (Professional Association for SQL Server) user conference in Orlando, Fla., to refute the common user misconception that enabling end users with report building will crush the infrastructure under a data deluge, and to talk about Microsofts latest BI advances.
Is it a legitimate concern to worry about end users flooding the system with reports after they get their hands on Report Builder?
[It] is a legitimate concern for DBAs [database administrators] to have. If 10,000 people randomly started writing reports, life could get interesting. But the first thing to understand is DBAs have to give users permission before they write reports. Thats part of role-based permission. You can shut that off for a lot of reasons, and there are a lot of reasons to do that: compliance, for example, or whatever a given corporate policy is.
The second thing is, we cache very cleverly. If you and I pull the same report, we only keep one copy if its cached. We cache the smallest number of reports possible.
Is it true, though, that youll wind up with three report versions, as users tell me? As in, the original report in the OLTP [online transactional processing] system, the flattened Reporting Services version and the rendered report in database cache?
You definitely will have [the data stored in] operational sources—whether thats in order systems, inventory systems or whatever. Its very common to have a data warehouse, [for example,] for a lot of good reasons. And that data warehouse often represents more data than [the original operational sources].