Note: Technical Support does not support or troubleshoot issues around the set up of Collaboration as many steps required for collaboration to work correctly are modifications done outside of SQL-RD. Therefore it is highly recommended that you allow one of our internal consultants to perform the migration of the product. This will not only ensure a smoother transition, but minimal to no downtime and minimal resources/time spent.
Collaboration enables the ability to "assign" schedules to other SQL-RD machines. Though the management and editing of the schedules will occur on the primary SQL-RD machine, processing and running of the schedule will occur on the collaborator (the other SQL-RD installation).
With Collaboration, resource intensive schedules can be processed on more powerful servers. Also numerous schedules can be spread out across an array of SQL-RD machines to reduce the overall load, and run schedules more efficiently. Combined with Multi-threading, each SQL-RD Collaborator will have up to 8 threads. Therefore quadrupling the number of concurrent schedules you can run simultaneously with every collaborator added.
This Feature best fits organizations that desire enterprise-wide reporting that require thousands of reports to be distributed.
1) Collaboration is included with the Multi-threading module. Multi-Threading must be purchased in order for this feature to be available. (Not applicable to X Model Licenses)
2) More than one SQL-RD Installation is required. (Note: ensure each SQL-RD machine meets the SQL-RD Pre-requisites)
3) Each SQL-RD Machine must have SQL-RD installed, and is accessible through the internal network.
4) Each remote server must have the correct email, database, and system settings in order to ensure proper processing and delivery of the reports/schedules. Each collaborator's settings should match the main scheduler.
5) The Primary Machine's database must be migrated to your own SQL Server instance (See Migrate to SQL Server / ODBC). Additionally, each collaborator should be connected to primary scheduler's database (See Switch - To ODBC / Local SQL)
Setting up Collaboration:
Go to the "System" tab on the SQL-RD ribbon.
Select "Collaboration" from the ribbon menu.
Switch "enable server Collaboration" to "ON"
Now it is time to add the SQL-RD machine as a collaborator. Clicking on "Add" you will be prompted to select the SQL-RD configuration file on the remote machine. Browse through the network and select the SQL-RD machine.
SQL-RD will automatically display two folders for SQL-RD. Select "crdconfigshare."
Then select the "sqlrdlive.config" file.
Please understand that the new Collaborator will no longer process its own local schedules. Select "OK" to continue.
Authenticate to the windows machine. Ensure that the user is a local administrator with read/write access to the collaborator.
Once you have authenticated, you may receive a message stating that SQL-RD cannot access the process list on the remote machine. If this is the case, ensure that remote machine's SQL-RD and scheduler are closed. Then Select "OK."
Once Finished, the new Collaborator is added to the list. Select "Add" to include more servers.
For the next step, go to the collaborator machine. Switch the Collaborator to NT Service Scheduler. All collaborators must run using the NT Service Scheduler. (See NT (Windows) Service Scheduler)
Assigning Schedules to other Collaborators:
Open a schedules Properties then go to the "Schedule" section.
At the bottom, a new option "Enable this schedule and execute it on" will appear. Check the box to the left to enable the schedule and then select from the dropdown list which collaborator will process the schedule.
Removing A Collaborator:
To remove a Collaborator from the system, go to the collaborator and switch the scheduling system to "no scheduling required." (see No Scheduling Required)
Return to the Collaboration Menu. Select the desired server and then click "delete." Click "OK" on the confirmation message to initiate the removal.
Authenticate to the remote machine to finish the process.
The Collaborator is then removed from the list, and can now be operated independently of the primary SQL-RD installation.