SQL-RD is an application for Windows that saves time and money by making it easy to define single or packages of SQL Server Reporting Services reports, schedule and run them automatically, and send the reports to print, fax, disk, or email in a number of standard formats.

Simply set up a schedule stating how often you would like each report to run, whether you'd like the output in Word, Excel, HTML, RTF, Acrobat, RPT, text format, and more and who it should be sent to.

SQL-RD is a software that define single or packages of SQL Server Reporting Services reports.

It's easy to schedule reports to run at a specific date and time, or to run them hourly, daily, weekly, or monthly - or when spcified events occur

The same report can be scheduled to be run multiple times with different parameters, formats, frequencies, and destinations.

By automating repetitive reporting tasks, SQL-RD ensures that reports are created and distributed when needed, without error, and without costly support time.

SQL-RD's familiar Explorer-like interface makes it easy to define and schedule report packages. The context (right-click) menus and full copy-and-paste support make it easy to create complex distribution schedules.

Features include the ability of Windows users to run SQL-RD as a service, an improved intuitive user interface, a comprehensive scheduler that lets you create reports at any frequency, and send them to print, fax, disk, or email (using SMTP, MAPI, and SQL-RDMail), a wide range of export formats, dynamic database functionality, custom frequency calendars, a built in address book, bulk printing, ftp folder output, single and ranges of parameters, conditional scheduling, group bursting, multi-threading, clustering and lots more.

Whether you're spending too much time running and distributing SQL Server Reporting Services reports output to line managers, or you need to provide corporate management with tailored reports on a regular schedule, SQL-RD gives you the tools that you need. 

Here are some key features of "SQL-RD":

Single Report Schedules:
· A single report is set to generate at specified intervals (Daily, Hourly, Weekly etc). It is exported to a specified format (PDF, Excel, XML etc). The exported file is delivered to one or more destinations (email, FTP, printer, etc). For example, email the daily sales report to the sales manager at 8am every week day except on public holidays.

Package Report Schedules:
· Set up a package of reports to be generated at defined intervals and delivered to one or more defined destinations - together. For example, a monthly report pack (consisting of a number of reports) can be sent to a client with all reports attached to the single email or compressed into a single zip file, or merged into a single Excel workbook, or PDF file before delivery.

Automation Schedules:
· Write and execute simple or complex business process automation scripts or macros using SQL-RD's Custom Tasks. Use this schedule on its own, or as part of a more complete automation solution. Examples include Send an email, Update a database record, Upload to FTP, Update a file, Print files and lots more.

Dynamic Schedules:
· Multiple instances of the same report are exported. For each instance SQL-RD will automatically enter the required parameter values, export the report and deliver the results to the corresponding email, folder, ftp, printer or fax. The parameters and destination are read from your own database. For example, run the same report for dozens of clients without writing a schedule for each client.

Dynamic Package Schedules:
· Dynamically generate and deliver individualized export packages for multiple recipients using the same set of reports. Dynamic Schedules for Packages! For example, you can use the same set of reports to generate individual monthly report packages for all your clients.

Event-Based Schedules:
· Instantly respond to business and client needs. Fire off reports or automation scripts when a defined system event occurs. For example, trigger a report or automation script when a value in a database has changed, or when a new email arrives You can even use values in the email body text to populate parameters, email addresses, database tables and more.

Event-Based Packages:
· String a number of Event-Based schedules together as a batch to run in a specified order and/or at specified scheduled times. Use to ensure that required conditions are fulfilled before a report is exported. For example, run the report once a month, but only if the monthly total figure in the sales database matches that in the invoices database.

Data-Driven Schedules:
· Expand Reporting Services functionality! Drive all variables of your reporting requirements (parameters, destinations, output format, etc) from database tables and queries.

Database Record Exists:
· Apply to new database records only, or to any matching database records.

Database Record Has Been Modified:
· Choose to include New (Inserted) records and Deleted records. Use this for follow-ups by selecting to only match the condition if the record has been (or not been modified) in x minutes. Repeat the action every x minutes until the condition is no longer true, or run just once.

Unread Mail Is Present:
· Monitor a POP or IMAP mailbox for new emails. Forward or Redirect. Delete mail after processing. Read the body text and other mail sections (sender email, subject, etc) and use the values to populate report parameters, email addresses etc. For example, send the report to the sender of the email.

File Exists:
· Use this trigger to respond to the existence of a new file in a local or network folder.

File Has Been Modified:
· Great for monitoring log files, but works equally well for all other types of local or network files.

Printer:
· Output to a single printer.
· Multiple copies to a single printer.
· Output to multiple printers (bulk printing).
· Multiple copies to multiple printers.

Email:
· Set up & use one or multiple SMTP servers.
· Use different SMTP servers/accounts for different schedules.
· Nominate one or more SMTP servers as backup or fail over servers.
· Connect to Secure SMTP servers.
· Connect and send via GroupWise.
· Connect & send via MAPI.
· Silent integration with MS Outlook & MS Exchange.
· Use Outlook/Exchange address book.
· Use SQL-RD's built in address book.
· CC & BCC
· Insert additional files as attachments.
· Read email addresses from a database.
· Read email address from a mailing list (text file).
· Insert personalized tags in email body. For example, Dear {tablename.firstname}.
· Send emails in plain text or HTML.
· Use raw HTML code to construct better looking emails
· Embed report into email body.
· Read Receipt Processing.

Disk:
· Output to local drives. For example C:MyReportsToday.
· Output to network shares and UNC paths. For example \MyServerCMyReportsToday.
· Output to a remote system by Dial-Up Networking or VPN.
· Choose to append to an existing file instead of overwriting it.

FTP:
· Upload reports to FTP server.
· Supports Secure FTP - SSL 3 & SSL 3.1 (TLS).
· Upload non-report files.
· Download files from FTP server.


FAX:
· Manual or automated output to fax driver.
· Choose to include a cover sheet.
· Single or multiple recipients per schedule.

ODBC:
· Export the report data directly to a database table via and ODBC DSN.
· Choose to overwrite if target table already exists.

SMS (Cell phone Text):
· Send a text alert or simply embed a text report body into an SMS message.
· Use a local GSM Phone or device.
· Use a service provider (SMSC) via standard modem.

Other Destination Options:
· Compress (ZIP) file before delivery.
· Password protect ZIP file using zip encryption level 128, 192 or 256.
· Customize the output file name
· Customize the output file extension. For example, a CSV file normally named myfile.csv can be exported as myfile.abc.
· Append a date/time stamp to the output file.
· Deferred delivery allows you to take environmental issues into account. For example, export the reports at 1am, but do not email them until 7am as the email server is unavailable during those hours.
· Use PGP Encryption to secure file before delivery.
· Select multiple destinations

Requirements:

· P4 750MHz
· 500 MB disk space
· 1 GB memory
· Latest .NET Framework
· MDAC 2.7 or above
· Latest MS Jet Engine

Limitations:

· 30 days trial