Migrating data from Claude Compliance to Snowflake using CData SSIS Components.

Cameron Leblanc
Cameron Leblanc
Senior Technology Evangelist
Easily push Claude Compliance data to Snowflake using the CData SSIS Tasks for Claude Compliance and Snowflake.

Snowflake is a leading cloud data warehouse and a popular backbone for enterprise BI, analytics, data management, and governance initiatives. Snowflake offers features such as data sharing, real-time data processing, and secure data storage which makes it a common choice for cloud data consolidation.

The CData SSIS Components enhance SQL Server Integration Services by enabling users to easily import and export data from various sources and destinations.

In this article, we explore the data type mapping considerations when exporting to Snowflake and walk through how to migrate Claude Compliance data to Snowflake using the CData SSIS Components for Claude Compliance and Snowflake.

Data Type Mapping

Snowflake Schema CData Schema

NUMBER, DECIMAL, NUMERIC, INT, INTEGER, BIGINT, SMALLINT, TINYINT, BYTEINT

decimal

DOUBLE, FLOAT, FLOAT4, FLOAT8, DOUBLEPRECISION, REAL

real

VARCHAR, CHAR, STRING, TEXT, VARIANT, OBJECT, ARRAY, GEOGRAPHY

varchar

BINARY, VARBINARY

binary

BOOLEAN

bool

DATE

date

DATETIME, TIMESTAMP, TIMESTAMP_LTZ, TIMESTAMP_NTZ, TIMESTAMP_TZ

datetime

TIME

time

Special Considerations

  • Casing: Snowflake enforces an exact case match by default for identifiers, so it is common to run into issues that can be attributed to mismatched casing. Set the IgnoreCase property to True in your CData SSIS Components for Snowflake connection to resolve these issues. This property directly maps to the QUOTED_IDENTIFIERS_IGNORE_CASE property in Snowflake and specifies whether Snowflake will treat identifiers as case-sensitive.
  • Timestamps: Snowflake supports three timestamp types:

    • TIMESTAMP_NTZ: This timestamp stores UTC time with a specified precision. However, all operations are performed in the current session's time zone, controlled by the TIMEZONE session parameter.
    • TIMESTAMP_LTZ: This timestamp stores "wallclock" time with a specified precision. All operations are performed without taking any time zone into account.
    • TIMESTAMP_TZ: This timestamp stores UTC time together with an associated time zone offset. When a time zone isn't provided, the session time zone offset is used.

    By default the CData SSIS Components write timestamps to Snowflake as TIMESTAMP_NTZ unless manually configured.

Prerequisites

Create the project and add components

  1. Open Visual Studio and create a new Integration Services Project. Create the SSIS project
  2. Add a new Data Flow Task to the Control Flow screen and open the Data Flow Task.
  3. Add a CData Claude Compliance Source control and a CData Snowflake Destination control to the data flow task. Add the source and destination controls (Salesforce is shown)

Configure the Claude Compliance source

Follow the steps below to specify properties required to connect to Claude Compliance.

  1. Double-click the CData Claude Compliance Source to open the source component editor and add a new connection. Open the source component editor (Salesforce is shown)
  2. In the CData Claude Compliance Connection Manager, configure the connection properties, then test and save the connection.

    The driver connects to Claude Compliance using a Compliance Access Key, the only supported authentication method. Set the following connection property:

    • APIKey: The Compliance Access Key you created.

    Creating a Compliance Access Key

    1. Enable the Compliance API for your organization.
    2. Sign in to claude.ai as a primary owner or organization owner and open Organization settings > API > Keys.
    3. Select Create Key and assign only the scopes your integration needs:
      • read:compliance_activities for Activities and the typed activity views.
      • read:compliance_org_data for organizations, roles, groups, and settings.
      • read:compliance_user_data for users, chats, files, projects, and downloads.
      • delete:compliance_user_data for the explicit Delete stored procedures.
    4. Create the key and copy it when it appears. The key starts with sk-ant-api01- and is shown only once.

    Optionally, set OrganizationUUID to limit organization-scoped views (such as OrganizationUsers and ComplianceRoles) to a single linked organization. If it is left empty, those views default to the first available organization and do not include data from all linked organizations.

    Configure the source connection (Salesforce is shown)
  3. After saving the connection, select "Table or view" and select the table or view to export into Snowflake, then close the CData Claude Compliance Source Editor. Select the table to export (Salesforce is shown)

Configure the Snowflake destination

With the Claude Compliance Source configured, we can configure the Snowflake connection and map the columns.

  1. Double-click the CData Snowflake Destination to open the destination component editor and add a new connection. Open the destination component editor
  2. In the CData Snowflake Connection Manager, configure the connection properties, then test and save the connection.
    • The component supports Snowflake user authentication, federated authentication, and SSL client authentication. To authenticate, set User and Password, and select the authentication method in the AuthScheme property. Starting with accounts created using Snowflake’s bundle 2024_08 (October 2024), password-based authentication is no longer supported due to security concerns. Instead, use alternative authentication methods such as OAuth or Private Key authentication.

    Other helpful connection properties

    • QueryPassthrough: When this is set to True, queries are passed through directly to Snowflake.
    • ConvertDateTimetoGMT: When this is set to True, the components will convert date-time values to GMT, instead of the local time of the machine.
    • IgnoreCase: A session parameter that specifies whether Snowflake will treat identifiers as case sensitive. Default: false(case is sensitive).
    • BindingType: There are two kinds of binding types: DEFAULT and TEXT. DEFAULT uses the binding type DATE for the Date type, TIME for the Time type, and TIMESTAMP_* for the Timestamp_* type. TEST uses the binding type TEXT for Date, Time, and Timestamp_* types.
    Configure the destination connection
  3. After saving the connection, select a table in the Use a Table menu and in the Action menu, select Insert. Choose the destination table
  4. On the Column Mappings tab, configure the mappings from the input columns to the destination columns. Map the columns (Salesforce is shown)

Run the project

You can now run the project. After the SSIS Task has finished executing, data from your SQL table will be exported to the chosen table.

Ready to get started?

Download a free trial of the Claude Compliance SSIS Component to get started:

 Download Now

Learn more:

Claude Compliance Icon Claude Compliance SSIS Components

Powerful SSIS Source Components that allow you to easily connect SQL Server with Claude Compliance through SSIS Workflows.

Use the Claude Compliance Data Flow Components to synchronize with Claude Compliance Activities, Chats, ChatMessages, CodeArtifacts, ComplianceRoles, Organizations, OrganizationUsers, Projects, and more. Perfect for data synchronization, local back-ups, workflow automation, and more!