You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website/docs/reference/resource-configs/teradata-configs.md
+6-9Lines changed: 6 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ id: "teradata-configs"
5
5
6
6
## General
7
7
8
-
**Set `quote_columns`* - to prevent a warning, make sure to explicitly set a value for `quote_columns` in your `dbt_project.yml`. See the [doc on quote_columns](https://docs.getdbt.com/reference/resource-configs/quote_columns) for more information.
8
+
**Set `quote_columns`* - to prevent a warning, make sure to explicitly set a value for `quote_columns` in your `dbt_project.yml`. See the [doc on quote_columns](/reference/resource-configs/quote_columns) for more information.
9
9
10
10
```yaml
11
11
seeds:
@@ -123,7 +123,7 @@ id: "teradata-configs"
123
123
124
124
For details, see [CREATE TABLE documentation](https://docs.teradata.com/r/76g1CuvvQlYBjb2WPIuk3g/B6Js16DRQVwPDjgJ8rz7hg).
125
125
126
-
* `with_statistics` - should statistics be copied from the base table, e.g.:
126
+
* `with_statistics` - should statistics be copied from the base table. For example:
127
127
```yaml
128
128
{{
129
129
config(
@@ -270,7 +270,7 @@ For example, in the `snapshots/snapshot_example.sql` file:
270
270
271
271
Grants are supported in dbt-teradata adapter with release version 1.2.0 and above. You can use grants to manage access to the datasets you're producing with dbt. To implement these permissions, define grants as resource configs on each model, seed, or snapshot. Define the default grants that apply to the entire project in your `dbt_project.yml`, and define model-specific grants within each model's SQL or YAML file.
272
272
273
-
for e.g. :
273
+
For example:
274
274
models/schema.yml
275
275
```yaml
276
276
models:
@@ -280,7 +280,7 @@ for e.g. :
280
280
select: ['user_a', 'user_b']
281
281
```
282
282
283
-
Another e.g. for adding multiple grants:
283
+
Another example for adding multiple grants:
284
284
285
285
```yaml
286
286
models:
@@ -295,8 +295,8 @@ Another e.g. for adding multiple grants:
295
295
296
296
Refer to [grants](/reference/resource-configs/grants) for more information on Grants.
297
297
298
-
## Query Band
299
-
Query Band in dbt-teradata can be set on three levels:
298
+
## Query band
299
+
Query band in dbt-teradata can be set on three levels:
300
300
1. Profiles level: In the `profiles.yml` file, the user can provide `query_band` using the following example:
301
301
302
302
```yaml
@@ -401,9 +401,6 @@ These steps collectively ensure that the valid_history strategy effectively mana
401
401
2 | PERIOD(TIMESTAMP)[2024-03-01 00:00:00.0, 2024-03-12 00:00:00.0] | A | x1
402
402
2 | PERIOD(TIMESTAMP)[2024-03-12 00:00:00.0, 9999-12-31 23:59:59.9999] | C | x1
403
403
```
404
-
405
-
406
-
407
404
408
405
## Common Teradata-specific tasks
409
406
* *collect statistics* - when a table is created or modified significantly, there might be a need to tell Teradata to collect statistics for the optimizer. It can be done using `COLLECT STATISTICS` command. You can perform this step using dbt's `post-hooks`, e.g.:
0 commit comments