William Vaughn


William (Bill) Vaughn is an industry-recognized author, mentor, trainer, and subject-matter expert on Visual Studio, SQL Server, and ADO.NET. He’s worked in the computer industry for more than 30 years, including 14 years at Microsoft. He's available for mentoring and custom training (see Beta V Corporation or William Vaughn's Musings for more information). He’s written seven editions of the Hitchhiker’s Guide to Visual Basic and SQL Server (Microsoft Press)—the 7th edition is on Visual Studio—and three editions of ADO.NET and ADO Examples and Best Practices (Apress). Bill and Peter Blackburn also wrote the best-selling Hitchhiker’s Guide to SQL Server 2000 Reporting Services (Addison-Wesley Professional). More recently, he’s written The Owl Wrangler and Guardians of the Sacred Seven (Beta V Corporation), the first two books in his fantasy fiction trilogy

Are You Ready for Report Builder 2.0?

Report Builder 2.0 isn’t right for every environment. To decide whether the application will benefit your organization, you need to determine whether your report developers and end users can perform the following operations:

Report Builder 2.0 Security

Using Report Builder 2.0 to create reports against data from base tables, views, and stored procedures is easy—perhaps too easy. When users create reports, they can specify raw SQL code to fetch data for a report. Unfortunately, users don’t always write efficient queries.

Report Builder 2.0
This reincarnated tool is easy to use but creates certain security risks when users modify reports.
Report Builder vs. ReportViewer

There are some notable differences between Report Builder 2.0 and the Windows Forms or ASP.NET-hosted ReportViewer control. Report Builder handles all connection operations and executes the Report Definition Language (RDL)-embedded queries from the client. In the ReportViewer control, your code handles these operations. You must write and execute client-side code to open a connection and return a suitable data structure (e.g., a data table) to be passed to the ReportViewer control’s Local Report Processor.

Join the Conversation

Get answers to questions, share tips, and engage with the IT professional community at myITforum. Are you a data center professional? Join AFCOM for the best data center insights.

Sponsored Introduction Continue on to (or wait seconds) ×