Teradata

What’s a Rich Text element?

The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.

Static and dynamic content editing

A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!

How to customize formatting for each rich text

Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.

Omni Loader supports the following authentication schemes:

SQL Server
This is the standard username/password combination stored in and verified by the SQL Server.
AAD password
This is Azure Active Directory password authentication.
AAD multi-factor
Azure Active Directory multi-factor authentication will show a pop-up authenticating you as a separate step.
AAD integrated
Azure Active Directory integrated authentication is an equivalent of what was used to be called Windows authentication for SQL Server.

Data handling defines the way Omni Loader will generate the files and clean up:

Clear before run
Everything in the container folder will be deleted before the data copying starts.
Clear after run
Everything in the container folder will be deleted after the data copying completes.
Timestamped
Nothing is deleted. On each run, Omni Loader creates a new folder named as the current time, then place the files inside the folder. This allows for a complete history, but may generate a large amount of data after many runs.

We support three modes of storage authentication:

Connection string
This is the least secure mode which should not be used in production. It requires account key and grants full access to the whole storage account.
Managed identity
A secure authentication mode, leveraging AAD to grant access to the resource.
Shared access signature
A good middle-ground where one can easily grant access to either a whole account or a specific container only.

Connection Details

Server

The IP address or hostname of your Teradata server. In the given example, it’s set to 127.0.0.1, which is typically used for local testing. Ensure to replace it with your actual server's IP address or hostname.

Port

The port number where your Teradata database is listening. The default Teradata port is 1025, but this should be confirmed with your database administrator or network team.

Username

Enter the username that will be used to log in to the Teradata database. The example shows the default Teradata username dbc, but you should use a specific username provided for your connection.

Password

The password associated with your Snowflake username.

Database

Specify the name of the database to which you are connecting. In many cases with Teradata, the default dbc database is used as a starting point.

Not encrypted/Encrypted

This indicates that the connection to the Teradata database will be encrypted. Ensure that your Teradata server is configured to accept encrypted connections.