GilaMonster (10/5/2015)
yb751 (10/5/2015)
The upcoming 'Stretch Database' feature in SQL 2016 may be exactly what you are looking for.With poor queries, that'll just make matters worse. If the queries can't eliminate the data in Azure (which with the function on the date column they won't be able to), SQL still has to read all the table, only now it'd have to fetch part of it down from Azure first, instead of off disk.
Stretch is mostly for alleviating storage problems, not a fix for badly performing queries.
Good point...however just solely on his original post it does appear to be the strategy he aiming for, I wasn't accounting for any shortcomings in the original design. Maybe I'll just walk away in virtual shame now... :pinch: