Our software comes with the free developer license included after the installation. Under the free developer license, you may develop SSIS packages, and execute them interactively within Visual Studio (SSDT or BIDS) without requiring a commercial license. The free developer license should serve most (if not all) development purposes sufficiently, including the evaluation of our software capabilities.

In case that you need to test the unattended execution of SSIS packages that contain our components, you would need a commercial license. If you want to try out the scheduling capabilities before acquiring a commercial license from us, you may request a free trial license by using the instructions below.

  • If you are running our software on an on-premise server or a virtual machine (VM) on the cloud, you would login to the server and launch the License Manager program, from there you would select the “Change License Key” button on the right side of the License Manager program UI. In the Change License Key window, you would leave the license key field empty, and fill out all the other fields in the form. Once everything is completed in the window, the “Request a Trial License” button will become available which you can click to request a trial license, which will last for 14 days.
  • If you are running our software on the cloud by utilizing the Azure SSIS Integration Runtime (SSIS-IR), our software would automatically request a new trial if no license has been detected in the system.

It is important to note that our license manager will not automatically offer trial extension, it is generally limited to one trial per server instance. For this reason, we recommend you complete the necessary evaluation of scheduling capabilities within the provided trial period (14-day) to maximize the values of having a trial license.

You would need a commercial license in any one of the following two scenarios.

  • When you plan to run unattended SSIS jobs such as using SQL Server agent job for scheduling, running from Windows command line, a third-party scheduling/automation software, or running it from within Azure Data Factory (ADF) using SSIS Integration Runtime (SSIS-IR).
  • When you use our software for production purpose. We don't generally put limitations in our free developer license to prohibit you from loading data into a production system, but there is a legal term in our license agreement that advises against this practice, in other words, it is a situation that you should acquire a commercial license when you load data into your production even you may be running the software interactively.

We have two types of licenses for our commercial products:

  1. Perpetual License (On-premise integration server or VM only)
  2. Subscription License

The two licenses work exactly the same by enabling you to run unattended jobs. However the subscription license would expire once the subscription term has matured and will cease functioning for unattended job executions if not renewed. Perpetual license runs infinitely on the version of the software that you are licensed for, and it will never expire. Our perpetual license comes with an initial one-year Maintenance and Upgrade (M&U) included, which means you are eligible for the version that you are licensed at the time when the license was acquired. In addition you also have access to any versions released by us for the same software within the maintenance term included (typically a year) from the date when the license was acquired. We recommend our clients always keep their software maintenance up-to-date in order to maintain access to our latest software releases and also our technical support resources, including any client services that you may require while using our software in a commercial environment. 

It is important to note that Perpetual License is NOT available for Azure SSIS-IR, in which case it would have to be a Subscription License. In addition, our Single Server license cannot be used for Azure SSIS-IR, neither can you use an Azure SSIS-IR license for an on-premise server or VM, in which case the Single Server license will be the option to go for.

Our software is licensed per integration server (if using an on-premise server or a VM either on-premise or on the cloud), or per IR instance (when working with Azure SSIS-IR). Each SSIS server or IR instance that you want to run SSIS packages for unattended job execution would require a separate license. Unattended job execution includes any execution outside of the development tools (e.g. Visual Studio, BIDS or SSDT), also the scenario that you run SSIS packages using a scheduling tool such as SQL Server agent job, ADF activity or other scheduling solution. In any of such cases, the server or IR instance will have to be licensed in order to work with job executions.

We don't differentiate between different server purposes in terms of how they should be licensed. Given an example, if you have one DEV server and one Production server for unattended job execution, you will need to acquire two licenses. To make it more specific, there isn't a DEV, or non-Production server licensing option available that would be priced at a different rate.

Software maintenance is an important component of the license that you have acquired. It provides you the access to our software upgrade along with technical support that you may require. Software maintenance is always included for the entire subscription period when working with a subscription license. So the maintenance mainly applies to the perpetual license that you have acquired.

When working with a perpetual license, it generally comes with the first year of maintenance and upgrade included, which means that you have access to our maintenance and upgrade program for the entire year starting from the date when the license is purchased. This also means that you would have access to the software versions released before your license maintenance expiry date. Let's say you have acquired a perpetual license on January 1, 2020, you will have access to all versions released before January 1, 2021 for the entitled software.

In addition, maintenance is required in order to received any services for the software you have licensed.

There are a few ways to get your software maintenance renewed on the subsequent years.
  • We generally send you an advanced notice when your software maintenance is about to expire. In our reminder email, you will find the Renew link available for each license item, which you can simply click to start the renewal process.
  • In earlier version of our software, you have the option to acquire a maintenance key from us and apply it to a perpetual license by launching the KingswaySoft License Manager program (when working with KingswaySoft Integration Gateway, it will be the License button that you should click).
  • When using a recent version of our software, there is a Renew button in the KingswaySoft License Manager shipped with the software, which you can click to start the renewal process. Once you have placed the order, you can refresh the license in the KingswaySoft License Manager or you can re-activate the same license key in the License Manager program.
  • If you are unsure how this works, you are more than welcome to reach out to our client services team, we will be happy to assist you through the entire process. 

If you are reinstalling products on the same computer (e.g. following installation of a new operating system), you can re-activate the products using the same product license key, provided that you are using the exact same computer name. This does not affect the number of distinct activations for the license key. To install products on a different server or computer system, you must first deactivate the products on the old system using the Deactivate License tool in the KingswaySoft License Manager program, and then re-activate them on the new server or computer system.

Yes, you can if it is an on-premise server. In order to move the license, you must send us an email to request a deactivation code indicating which license key you are trying to move. You can use the code (if provided) to deactivate the license from your current system in order to use the same license on your new server or computer system. In your request, please provide us the full license key.

Note that you need to have up-to-date maintenance with us, our licensing system cannot generate a deactivation code if your software maintenance has expired (or the deactivation request will be declined even if a deactivation code was made available to you). Also note that our licensing system has imposed a limit on how many transfers can happen to one license key. The maximum allowed transfers for a license key is two within a maintenance/subscription term (typically one year). When the limit is reached (for instance, the third transfer within a year), we will not be able to offer the license relocation service for the particular license key. In this case, you must acquire a new license.

There is no limit on the total number of transfers you can do with one particular license key, as long as your software maintenance is up to date, and you don't reach the annual limit.

It is important to note that license relocation is only possible with on-premise server or virtual machine, we don't have the same flexibility of moving an Azure SSIS-IR license from one IR instance to another due to many technical barriers that we have when the software is running in SSIS-IR.

The "distinct connection" concept refer to the number of unique connections made within the last 24 hours per connection type. Multiple connections to the same instance in the same package or different packages are usually treated as one (1) distinct connection (exceptions may apply depending on the nature of the service). This is implemented under the conditions of fair-use which is explained in our End User License Agreement document. It is mainly enforced against those purpose-built API-based connections, such as Microsoft Dynamics 365, Salesforce, SharePoint, etc. By default, our SSIS Integration Toolkit and SSIS Productivity Pack software allows up to 8 distinct connections for each connection type by default. For instance, when you work with CDS or Microsoft Dynamics 365/CRM Servers, you will be able to connect to 8 different Dynamics 365/CRM or CDS instances (or organizations) by default on each licensed integration server. As mentioned, the limit is restricted per connection type (or service). If you are connecting to two different services, let's say SharePoint and Salesforce, you can connect to up to 8 different SharePoint servers and 8 different Salesforce instances on the same integration server, and the limit does not interfere with each other between different connection types.

In order to understand how many distinct connections are currently in use, you would launch the KingswaySoft License Manager program shipped with our software. If your server is licensed, there should be a magnify icon button on the main UI, when clicked, it will launch the Runtime Connection Usage Summary window from where you can see the number of distinct connections currently in use for each connection type applicable to the software installation. If you don't see any connections there, it generally means that no connections have ever been logged in the system.

In should be noted that the limit is implemented over a span of 24 hours, it is a system wide restriction, and it applies to all SSIS packages executed during the 24-hour period of time, not just the current executing package. The system will automatically reset the count every 24 hours. The 24-hour period is a sliding duration, the reset does not always happen at the same time every day, it generally depends on the job executions.

It is important to note that this restriction does not apply to those general-purpose connections or components, such as general HTTP connections, ADO.NET connections, XML components, JSON components, etc. Neither does this apply to the components that require no connections.

In addition, the way how the connections are counted varies from service to service. For most services, it is about the unique number of instances that you are connecting to. For SharePoint connection, each SharePoint server (the host name) would consider a distinct connection. It is important to note that the feature does not provide any detailed debugging capability, the restriction is implemented in a philosophy that it should be fair to our clients or partners.