In SQL Server 2019:
– Exciting stuff: In memory tempdb!
– Exciting stuff: sp_estimate_data_compression_savings can evaluate columnstore compression!
– Disappointing stuff: If you use in memory tempdb, you can’t have any columnstore anything in tempdb
That means if you’re using sneaky tricks like clustered columnstore indexes on temp tables to induce batch mode, you’re gonna get a lot of errors.
Likewise, you won’t be able to evaluate if columnstore will help your tables.
Click through to understand the extent of this limitation. Hopefully this is something we see addressed in vNext and a CU for 2019.