Add support for Enterprise SQL Server features (i.e. Indexes ONLINE=ON)

[kramer1007]

When building a SQL Server Database project, if SQL files include enterprise features such as Online Index building, these statements are ignored when outputting the SQL code or applying to target databases.

How to reproduce: add an index to a database project that would get deployed. test it with "WITH (ONLINE = ON)" and without. You'll see that when looking at the output, you'll see that the "WITH (ONLINE = ON)" is ignored.

[kramer1007]

Drew Skwiers-Koballa (@dzsquared) any update on this? i see it's on the backlog.

[kramer1007]

[tony-donley]

Persisted options are honored or ignored according to publish profile flags, but non-persisted options are always ignored. I would like to see SOME non-persisted options honored, such as ONLINE and SORT_IN_TEMPDB. DROP_EXISTING would need to be applied intelligently because it would fail if the index doesn't exist.

[kramer1007]

[kramer1007]

[tony-donley]

Drew Skwiers-Koballa (@dzsquared) Thanks for the great information you provided at PASS last week. I appreciated the session.

Is there any interest in this issue? I don't think this is limited to just Enterprise features, it's other non-persisted options also, like SORT_IN_TEMPDB and MAXDOP, which when applied intelligently can reduce the outage window during a deployment.

[kramer1007]

Great points Tony! I would have to agree with those options as well.

[asrichesson]

It would be nice to have an option in the publish profile to create all indexes with ONLINE = ON regardless if the option is not set in the Create Index DDL statement. Right now, I am using this contributor to set ONLINE = ON for all create index statements.

[llali]

this feature is implemented in dacFx and available in the preview version 162.2.91-preview