Netezza

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.

Connection Details

Connect using

DSN
‍Select this option if you have a pre-configured DSN for Databricks. DSNs are a convenient way to store connection information in a named location and can be easily managed within your operating system.
Connection string
‍Choose this if you prefer to directly enter a full connection string. This string includes all necessary details such as host, port, and credentials.

Username

Enter the username that has access rights to the Netezza database.

Password

Enter the password corresponding to the username provided.

Include views as tables

If you want to include views in the migration and treat them as tables, check this option. This can be useful for migrations where the view's data needs to be replicated along with the tables.

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.