This case aims to identify the requirement to maintain the "Windows Service - Scheduler" in LinkSOFT.

Since the Web Service Scheduler is more configurable than the Windows Service Scheduler, we are considering the option to deprecate the Windows Service Scheduler.

The Windows Service  (Link Technologies - Windows Service) is an alternative scheduler to the WEB.CONFIG scheduler.

1. Can you please provide your feedback on the need to keep the LinkSOFT Windows Service?
2. If you choose to keep, please list the clients using the Windows Service

Hi Sanjay

Find below reasons for keeping Windows service:

1. With the recent upgrade of a few customers, I have noticed that the Windows scheduler is much faster with API data transmission, especially for replication cases. 
2. I have a few customers using POS and Payroll with the Express version of SQL hence the need for Windows Scheduler to run the processes

Link Clients Using Windows Scheduler:

1. OTGL 22 Sites Windows Scheduler for replication. When they were using IIS Scheduler, replication was used to queue up. With the Windows scheduler, we have not seen this happening.
2. DATELINE HOTEL (Express SQL)
3. Delta Timber Supplies Pte Limited (Express SQL)
4. DR Suresh Chandra Dental Surgeon (Express SQL)
5. Haniff Tuitoga Lawyers (Express SQL)
6. I-DESIGN PROPERTY SOLUTIONS PTE LTD T/A Rhubarb Cafe (Express SQL)
7. Multiline Traders (Express SQL)
8. P S Nagra & Son (Express SQL)
9. Protech Electrical & Safety Supplies Ltd  (Express SQL)
10. Rajen Builders Ltd (Express SQL)

Thanks
Vineet Ram

Hi Vineet, thanks for the feedback.

The WEB service can be used to run the SQL scheduler similar to what the Windows Scheduler does.

I will configure QA7 with SQL Express and set this up to show you how this can work later next week.

Hi Vineet, I have configured QA7 with SQL Express 2017 and set up LinkSOFT 15.00 with the Web Scheduler turned on for SQL Jobs.

Here are some details in response to the concerns raised:

1. For clients using SQL Express, the SQL Jobs will be picked up by the IIS Worker Process (See Figure 1)
2. The worker process is multi-threaded, therefore the agent jobs should not slow down the web application
3. For customers requiring heavy data processing
   1. Set up separate "site files" and use this to run the scheduler.
   2. This is the method used in one of our "high volume data processing clients" that have a very large database and use this method to run complex and "long-running" scheduled reports, as well as "Company ~> Processes"
   3. This method allows you to use multiple servers to distribute workloads as well
4. Since IIS is a lot more configurable, you can manage load balancing better using the IIS scheduler

Next steps:

1. Review the setup in QA7 and let me know if there are any concerns that we should consider further

Figure 1 - Process scheduler will pick up the IIS Worker process if the Windows Service is not available

No response to this case. We are proceeding with the removal of the Windows Service.

For customers requiring Windows Service, please keep them on Version 14 until we have a use case to bring this functionality back.