Click or drag to resize
SSIS packages

[This is preliminary documentation and is subject to change.]

SSIS (SQL Server Integration Services) is a standard component of SQL Server - it is Microsoft's ETL ("Extract, Transform, Load") tool. It is possible to build SSIS "packages" either in Visual Studio (workflow and dataflow editors etc.) or in SQL Server Management Studio (by using the import/export wizard and selecting "save as SSIS package").

SSIS is a very powerful tool. If you need functionality, that is not directly supported by SSIS, you might find (commercial or free) componentes, that may add this functionality to SSIS. Programmers may build custom components, too. There is a steep learning curve, though.

It is recommend that you consider using SSIS to solve import/export demands and implement interfaces to 3rd party systems before you start developing you own code (using Custom WebForms, Plugins, etc. )

SSIS packages may be deployed and run in various ways - each option has its pros and cons.

Deploy and run on database server

SSIS packages may be deployed to a database server.

See Running on database server for details.

Deploy and run on web server

Sometimes is is desirable to execute SSIS packages from within the TOPICA user interface. This is the case, when an end user must initiate an action that is implemented as an SSIS package, and this package generates output, that must be displayed to the end user.

See Ruinng on web server for details.

Deploy and run on remote server

In typical production scenarios, the database is not installed on the web server - but on a dedicated database server. In this case there is no need for an SQL server license on the web server.

Running an SSIS package on a server requires an SQL Server license on that server. So running SSIS packages on the web server will require an additional SQL Server license.

If the production environment contains a server with the right connectivity, and where an SQL Server license is already installed, it would be desirable to execute the SSIS packes on this server (the "remote server").

See Running on remote server for details.

Run packages from scheduled tasks

See Running as scheduled task for details.