Add reporting to your database in minutes with no HTML Coding, SQL Reporting Services etc

Apex SQL Report is a data driven, web reporting solution for Microsoft SQL Server. Imagine the ability to leverage off an existing database and begin offering your users literally hundreds of web based, HTML reports in a few minutes rather than weeks or even months.

Apex SQL Report is the first and only reporting solution designed specifically for SQL database developers.

If you have a SQL Server database you can be generating sophisticated HTML reports, graphs and Microsoft Excel spreadsheets without complicated server component installations, steep learning curves or expensive software. Apex SQL Report works with your existing stored procedure base to extend their output directly to your user's desktops.

Product Information ApexSQL Report News ApexSQL Report FAQs ApexSQL Report Datasheet

ApexSQL Report Help File ApexSQL Report Knowledge Base

Screen Shots

Features

• Support for new FusionCharts 2.0. Here are screen shots of FusionCharts 2.0 Chart Gallery.
• Column level aggregate functions.
• Support for reports in pop up windows.
• Export to Excel.
• Supports outputting data in graph format - includes pie, line, bar and column.
• Full copy of FusionCharts developer license included with each license of Apex SQL Report a $99 value. Includes help file, implementation guide and .fla file to customize look and feel of graphs.
• Administrative console for creating users, grouping reports, managing procedures, reports, passwords and more.
• Now users can be assigned to groups and only allowed access to certain reports.
• Reports can be added to groups and only be shown to certain users
• More user defined options added for graphing.
• Reports that are created are automatically displayed in a powerful treeview control grouped by report category.
• Reports point directly to SQL stored procedures and analyze the procedure meta data to create filters to select user criteria and automatically create report tables.
• HTML reports allow pagination and column sorting.
• User's can create client side report filters to show only a subset of reports and set other options like max rows returned and rows per page.
• Reports can be created, edited and deleted all through an online administration console.
• Report authors can edit reports down to report parameters to make them required and even point an individual parameter to a stored procedure to populate a pick list for user input.

Concept

(by Brian Lockwood, founder of Apex SQL)

The idea is simple and I have seen this at several client sites where I implemented earlier versions of Apex SQL Report. You have a database and a client application built and deployed. You have a few weeks worth of application usage and DATA is accumulating ... now you need reports to extract INFORMATION. The boss wants sale stats, biz ratios, how many failed orders, calls taken by reps etc. You go into a meeting and listen to him list off the basic ideas of 20 or more reports. You scratch them down on paper. you get back to your desk and there is an email with 5 more that he just thought of. Another meeting is called with more "players" and you get another 20 reports.

At end of the day you have a request for more than 50 reports. Some hard some easy. Some with criteria (input params) and some without.

The kicker is the reports are needed "yesterday".

I've been in this situation several times. Some developers would just implement Crystal or custom web pages in ASP/Java etc and start laboriously creating each hard coded report one by one. But I've always been averse to such needless drudgery as a developer and refuse to pay for excessive labor myself when it can be avoided.

My solution was to make an ASP "engine" that would "process" the underlying stored procedures that would provide the data for these reports. In it's early version it would present the procedures selected for reporting in a rudimentary menu, when the report was called the engine would check for existence of input parameters and present them to the user as HTML input boxes to collect user data. It would then fire off the proc and present the recordset in an html table. The rest is Apex SQL Report ....