Skip to content

Commit 32c674a

Browse files
committed
Updated readme and version to 0.15.1
1 parent 2a9a00f commit 32c674a

2 files changed

Lines changed: 35 additions & 1 deletion

File tree

README.md

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -55,6 +55,7 @@ Configure your dbt profile for using SQL Server authentication or Integrated Sec
5555

5656
### Sources
5757

58+
5859
### Testing & documentation
5960
- Schema test supported
6061
- Data tests supported from dbt 0.14.1
@@ -66,8 +67,41 @@ Configure your dbt profile for using SQL Server authentication or Integrated Sec
6667

6768
But, columns in source table can not have any constraints. If for example any column has a NOT NULL constraint, an error will be thrown.
6869

70+
### Indexes
71+
There is now possible to define a regular sql server index on a table.
72+
This is best used when the default clustered columnstore index materialisation is not suitable.
73+
One reason would be that you need a large table that usually is queried one row at a time.
74+
75+
Clusterad and non-clustered index are supported:
76+
- create_clustered_index(columns, unique=False)
77+
- create_nonclustered_index(columns, includes=False)
78+
- drop_all_indexes_on_table(): Drops current indexex on a table. Only meaningfull if model is incremental.
79+
80+
81+
Example of applying Unique clustered index on two columns, Ordinary index on one column, Ordinary index on one column with another column included
82+
83+
{{
84+
config({
85+
"as_columnstore": false,
86+
"materialized": 'table',
87+
"post-hook": [
88+
"{{ create_clustered_index(columns = ['row_id', 'row_id_complement'], unique=True) }}",
89+
"{{ create_nonclustered_index(columns = ['modified_date']) }}",
90+
"{{ create_nonclustered_index(columns = ['row_id'], includes = ['modified_date']) }}",
91+
]
92+
})
93+
}}
94+
95+
6996
## Changelog
7097

98+
### v0.15.1
99+
#### New Features:
100+
- Ability to define an index in a poosthook
101+
102+
#### Fixes:
103+
- Previously when a model run was interupted unfinished models prevented the next run and you had to manually delete them. This is now fixed so that unfinished models will be deleted on next run.
104+
71105
### v0.15.0.1
72106
Fix release for v0.15.0
73107
#### Fixes:

setup.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
from distutils.core import setup
44

55
package_name = "dbt-sqlserver"
6-
package_version = "0.15.0.1"
6+
package_version = "0.15.1"
77
description = """A sqlserver adpter plugin for dbt (data build tool)"""
88

99
setup(

0 commit comments

Comments
 (0)