You are welcome! Yes, I forgot about that, being read only limits its use in a Datawarehouse / ETL environment in our case. Thanks for the link, I will be sure to check it out.
We just started deploying filtered indexes in some of our ETL tables to help speed up our nightly loads since we are still using 2008 R2. We've seen dramatic improvements and I wanted to compare the filtered indexes against the clustered columnstore indexes and see which is faster overall. Thanks for your prompt and courteous response!
If you have a datawarehouse that uses table partitioning, then the read-only limitation becomes far less annoying, because you can use partiition switching to add new data without having to rebuild the entire columnstore index. This, too, will be covered in a later level.
And yes, depending on data and workload, filtered tables can also help. There are often multiple solution available in SQL Server.