Page Comparison

About Collectors

Collectors are extractors that are developed and managed by you (A customer of K).

...

There are several reasons why you may use a collector vs the direct connect extractor:

1. You are using the KADA SaaS offering and it cannot connect to your sources due to firewall restrictions

2. You want to push metadata to KADA rather than allow it pull data for Security reasons

3. You want to inspect the metadata before pushing it to K

Using a collector requires you to manage

1. Deploying and orchestrating the extract code

2. Managing a high water mark so the extract only pull the latest metadata

3. Storing and pushing the extracts to your K instance.

...

Pre-requisites

• Python 3.6 - 3.10

• Support SQL SSRS 2016+ where the database is called ReportServer$RS

  • if your SSRS databases differs from this, please Advise KADA of the SSRS version and what the database is called.

  • The collector will need access to the underlying SQLServer Database with permissions to read the following tables:

    • ReportServer$RS.DBO.CATALOG

    • ReportServer$RS.DBO.EXECUTIONLOG3

    • ReportServer$RS.DBO.USERS

• Access to K landing directory

• Access to the KADA Collector repository that contains the SSRS whl

  • The repository is currently hosted in KADA’s Azure Blob Storage. You will be given a SAS token to access the repository. Reach out to KADA Support (support@kada.ai) if you do not have access.

  • Download the SSRS whl (e.g. kada_collectors_extractors_ssrs-#.#.#-py3-none-any.whl)

...

The following connection types are NOT currently supported:

1. Teradata IP Reference Only Data Source

2. SAP NetWeaver Data Source

3. XML Data Source

4. Web Service Data Source

5. XML Document Data Source

6. Sharepoint Data Source

The following catalog item types are currently NOT supported:

1. Linked Reports

2. Files

3. Power BI Desktop Files

4. Report Models

Parameter resolution is not supported.

...

Some TSQL syntax is not support. These are mostly statements that contain not standard ANSI SQL constructs. Examples include:

1. Variables (DECLARE)

2. Flow control (IF BEGIN .. )

...

Step 1: Create the Source in K

...

If you are handling external arguments of the runner yourself, you’ll need to consider the following for the run method https://kadaai.atlassian.net/wiki/spaces/DATKSL/pages/18943181521902411777/Notes+v2.0.0#TheAdditional+Notes#Extractor-run-method

from kada_collectors.extractors.ssrs import Extractor

kwargs = {my args} # However you choose to construct your args
hwm_kwrgs = {"start_hwm": "end_hwm": } # The hwm values

ext = Extractor(**kwargs)
ext.run(**hwm_kwrgs)

...

A high water mark file is created in the same directory as the execution called ssrs_hwm.txt and produce files according to the configuration JSON. This file is only produced if you call the publish_hwm method. https://kadaai.atlassian.net/wiki/spaces/KSL/pages/1902411777/Additional+Notes#Storing-the-HWM-using-the-K-Landing-Area

...

Step 7: Push the Extracts to K

...