Alexey Semchenko

prefect config output: ``` { "debug":false, "home_dir":"/home/admin/.prefect", "backend":"server", "server":{ "host":"http://myhost", "port":4200, "host_port":4200, "endpoint":"http://myhost:4200", "database":{ "host":"localhost", "port":5432, "host_port":5432, "name":"prefect_server", "username":"prefect", "password":"test-password", "connection_url":"postgresql://prefect:pwd@localhost:5432/prefect_server", "volume_path":"/home/admin/.prefect/pg_data" }, "graphql":{ "host":"0.0.0.0", "port":4201, "host_port":4201, "debug":false, "path":"/graphql/" },...

Hi @swanderz! It takes 4-5 days to test, but I'm ready to accept suggestions/edits 🚀

@NicolasPA Yep, of course: ``` indexes=[ {'type': 'nonclustered', 'columns': ['customer_id'], 'unique': True} ] ```

@mahazza Thank you for sharing that code!

Looks intresting : ) But SQL Server have: - clustered/non-clustered indexes - limit to clustered index (one per table) - row-store (b-tree)/columnstore indexes - non-clustered row-store index may have included...

Hi @swanderz! Do I understand correctly that we need to implement this macro for SQL Server and name it `sqlserver__get_create_index_sql`? https://github.com/dbt-labs/dbt-core/pull/3106/files#diff-49fbdf0ee41b3d9ec139a881dfed1e9196c47ba014f946421f636bbf57703a6c

Working on that issue here: https://github.com/semcha/dbt-sqlserver/commits/new-indexes

@sdebruyn How else I can help?