Using SQL Server Standard? Tired of seeing everyone else using SQL Server Enterprise scheduling while you languish in a lower edition? Indeed SQL Server Enterprise scheduling brings handy features such as data-driven SSRS report scheduling and business process management that aren’t available in SQL Server Standard. However, there is a way to keep up with these features without upgrading your SQL Server edition. With PBRS, you can schedule SSRS reports, SSIS packages, and tackle other business processes such as updating database records.
Data Driven and Event Based Schedule
Many Enterprise users enjoy data driven report subscriptions or even event driven task scheduling. PBRS accomplishes something similar via its Data Driven Schedule and Event Based Schedule. The Data Driven Schedule will reel through your database, populate report parameters based on specific records, and then deliver the report to a corresponding email address. Going beyond SSRS, PBRS can even dynamically populate report formats, and deliver the report to customized destinations such as a fax machine or printer.
The Event Based Schedule can trigger reports or tasks based on a number of conditions. Based on changes in a database, the Event Based Schedule can send a report reflecting the changes in the data source. Changes in one database, can be propagated to other databases as well. The system can even monitor a file directory (either on a machine or an FTP site) for changes, and as a result trigger a report or task.
Speaking of tasks, PBRS has a wide array of custom tasks that can be used to build workflows. These tasks range from simple file management tasks, to complex tasks such as modifying tables, FTP sites, or even registry keys. Additionally, there are several features PBRS supports that simply don’t exist in SSRS regardless of edition. Numerous report formats, report encryption methods, and destinations are all possible with PBRS.
Advantages of PBRS Over SQL Server Enterprise Scheduling
Why would anyone use PBRS to expand on SQL Server Standard’s functionality as opposed to upgrading to SQL Server Enterprise scheduling? SSRS administrators that are looking for a dedicated scheduling system will find that PBRS offers a wider array of scheduling options. Multiple reports can be batch-distributed to users, and SSRS reports from multiple reporting environments can be managed in a single interface. Reports can often be a small part of an overall business process, and PBRS’s combined BPM and reporting solution enable administrators to manage both from one platform. Features such as Collaboration and Multi-threading enable administrators to better scale and throttle their report publishing processes.
Additionally, PBRS is an out of system workflow software, meaning that it is a standalone system from SSRS. There is no need to “plug” PBRS into the SQL server; many firms disallow the ability for users to modify SQL Server software in any way. In many cases, SQL Server Standard is packaged with a company’s ERP system, so they think they have to acquire a SQL Server license in order to expand on their ERP system’s features. However, in reality all a firm must do is use PBRS to augment their reporting and process infrastructure!
Who is PBRS Right For?
PBRS isn’t meant to replace SQL Server Enterprise entirely, however. Users that are looking for features such as advanced analytics, data warehousing functions, and enterprise data management will most likely look towards SQL Enterprise. On the other hand, PBRS’s powerful report scheduling and process automation tools will attract administrators that are looking to automate reports and tasks. Not to mention, there are plenty of SQL Enterprise users that also utilize PBRS scheduling features that do not exist in SQL Server. As always, the right solution is completely dependent on the organization’s needs.
You don't need to make the expensive upgrade to SQL Server Enterprise scheduling to keep up with your competitors. With PBRS, you can achieve similar report managing and scheduling success.
PBRS for SSRS & Power BI: