- Release notes
- Getting started
- Installation
- Configuration
- Integrations
- Authentication
- Working with Apps and Discovery Accelerators
- AppOne menus and dashboards
- AppOne setup
- TemplateOne 1.0.0 menus and dashboards
- TemplateOne 1.0.0 setup
- TemplateOne menus and fashboards
- TemplateOne 2021.4.0 setup
- Purchase to Pay Discovery Accelerator menus and dashboards
- Purchase to Pay Discovery Accelerator Setup
- Order to Cash Discovery Accelerator menus and dashboards
- Order to Cash Discovery Accelerator Setup
- Basic Connector for AppOne
- SAP Connectors
- Introduction to SAP Connector
- SAP input
- Checking the data in the SAP Connector
- Adding process specific tags to the SAP Connector for AppOne
- Adding process specific Due dates to the SAP Connector for AppOne
- Adding automation estimates to the SAP Connector for AppOne
- Adding attributes to the SAP Connector for AppOne
- Adding activities to the SAP Connector for AppOne
- Adding entities to the SAP Connector for AppOne
- SAP Order to Cash Connector for AppOne
- SAP Purchase to Pay Connector for AppOne
- SAP Connector for Purchase to Pay Discovery Accelerator
- SAP Connector for Order-to-Cash Discovery Accelerator
- Superadmin
- Dashboards and charts
- Tables and table items
- Application integrity
- How to ....
- Working with SQL connectors
- Introduction to SQL connectors
- Setting up a SQL connector
- CData Sync extractions
- Running a SQL connector
- Editing transformations
- Releasing a SQL Connector
- Scheduling data extraction
- Structure of transformations
- Using SQL connectors for released apps
- Generating a cache with scripts
- Setting up a local test environment
- Separate development and production environments
- Useful resources
Separate development and production environments
This page describes a suggested setup for separate production and development environments. This enables you to work together with multiple developers on a SQL connector. After all changes are done, a finished SQL connector can be released to a production environment.
See the illustration below for an overview of the suggested setup.
This is a suggested setup.
There are two instances of the SQL Server database, one for development and one for production.
SQL Server database instance |
Description |
---|---|
Development database |
• All developers should have access to the development database to inspect the data and validate transformations. • A schema per developer (per connector) should be created to ensure that developers do not interfere with each others work while running transformations during development. |
Production database |
• Access to the production database can be granted on a need-to-have basis or based on a certain role. • Only one schema is required that contains the production data. |
Instead of two separate SQL Server database instances you can choose to store the development and the production schemas in one SQL Server database.
There are two instances of CData Sync, one for development and one for production. For both instances, the basic installation instructions should be followed. However, there are some differences in configuration.
CData Sync instance |
Description |
---|---|
Development environment |
• A CData Sync user account per developer should be created such that each developer can create connections and jobs for development and testing purposes. |
Production environment |
• Only user accounts needed to configure production runs are needed. • Only jobs and connections necessary to extract production data and store it in the production SQL database are required. |
Instead of two separate CData Sync instances you can choose to store the development and the production jobs in one CData Sync instance.
Dbt needs to be installed on the local development workstations and on the production server. Local developers only use the development database, whereas the production instance of dbt will connect to the production database.
dbt-core
and some adapters like dbt-sqlserver
. Make sure the version of each of the components is the same on all environments to prevent problems. Refer to the dbt documenation for a list of available adapters.
See Setting up a SQL connector for a description on how to make a connector checkout for a new SQL connector.