Skip to main content

Preparing to run the SQL Server Integration Services collector

Warning

This collector is in public preview. It has passed our standard testing, but it is not yet widely adopted. You might encounter unforeseen edge cases in your environment. data.world is committed to promptly addressing any issues with public preview collectors. If you face any problems, please report them through your Customer Success Director, implementation team, or support team for assistance.

Setting up pre-requisites for running the collector

Make sure that the machine from where you are running the collector meets the following hardware and software requirements.

Table 1.

Item

Requirement

Hardware (for on-premise runs only)

Note: The following specs are based upon running one collector process at a time. Please adjust the hardware if you are running multiple collectors at the same time.

RAM

8 GB

CPU

2 Ghz processor

Software (for on-premise runs only)

Docker

Click here to get Docker.

data.world specific objects (for both cloud and on-premise runs)

Dataset

You must have a ddw-catalogs dataset set up to hold your catalog files when you are done running the collector.

If you are using Catalog Toolkit , follow these instructions to prepare the datasets for collectors.

Network connection

Allowlist IPs and domains



Preparing SQL Server Integration Services (SSIS)

Creating a user and assigning permissions

  1. Follow the Microsoft documentation to create a user login with SQL Server Authentication or set up a domain service account for NTLM authentication.

  2. To assign a user with the necessary permissions for the Package Deployment Model, grant one of the following:

    • Membership in the db_ssisoperator role

    • All of the following privileges:

      • SELECT on msdb.dbo.sysssispackages

      • SELECT on msdb.dbo.sysssispackagefolders

  3. For the Project Deployment Model, grant the user one of the following permissions:

    • Membership in the ssis_admin database role.

      OR

    • Membership in the sysadmin server role.

      OR

    • All of the following privellages:

      • EXECUTE privelage on SSISDB.internal.get_project_internal

        AND

      • READ on every extracted project

        AND

      • SELECT on the following tables and views:

        • SSISDB.catalog.projects

        • SSISDB.catalog.folders

        • SSISDB.catalog.packages

        • SSISDB.catalog.environments

        • SSISDB.catalog.environment_variables

        • SSISDB.catalog.environment_references

        • SSISDB.catalog.object_parameters

        • SSISDB.catalog.executions

        • SSISDB.catalog.operations

In this section: