esProc boasts outstanding computing capability and high performance in solving complex problems involving report data source preparation based on its excellent support for multiple data sources and non-database computing. It offers a user-friendly IDE, enabling reporting tools to reference the computed result conveniently through JDBC interface. It is really an ideal development tool tailored for the report developers.
Now let’s take a look on SQL/SP. Due to their native drawbacks, the development efficiency could be affected now and then when handling the complex report data source. For those SQL/SP drawbacks, esProc provides many remedies with its support of set-type data, discrete records, ordered sets, object reference, and set-style grouping to develop database scripts efficiently.The data source preparation usually involves handling heterogeneous databases, like providing a single data set for Jasper/BIRT/Crystal. Since esProc is independent of any specific database, this kind of computation can be carried out easily and smoothly without using the costly data warehouse and the low-efficiency customized data set. Compared with the semantic layer table join bound with specific reporting tools, esProc is more powerful in computing.
The data source preparation also covers the hybrid computing over the database and non-database source, for example, the interactive computing on the structured data from Excel/Txt files and the relational databases. This would usually involve the ETL tools and be implemented through Perl/VBScript plus multi-level scheduling. Owing to this, development and maintenance costs are always high. esProc, however, supports such hybrid computing by easily consolidating the heterogeneous data sources.
esProc provides the professional and easy-to-use IDE. An esProc script is written in a grid. When composing the judgment statement, loop statement, and other long statements, users benefit from the natural grid indentation that gives a clear view of the computing work scope. Each grid cell represents one computing unit/step. A cell can reference another cell by its natural cell name, without the need to define a variable. By clicking cells, users can monitor the computed results intuitively, instead of searching for them in a list of variables. esProc IDE boasts a complete set of debugging functions than that of SQL/SP. Users can thus bid farewell to the intermediate table specifically created to a debugging process, and there will be no code modification before they set up a break point.
esProc supports JDBC interface for reporting tools to retrieve computed result. The report developers don’t need to learn API or write code. The integration and deployment thus become easier.
esProc offers the powerful capability for cross-database computing and complex data computing, simple and easy-to-use IDE, and integrated JDBC interface. So, it is an ideal development tool for preparing the report data source.