Hello fellow TimeXtender users,
We were wondering: is it worth upgrading from SQL 2014 to 2016 in the scenario where we use TX traditionally: stage - dw - cubes.
Has anyone done it and have you seen performance improvements?
Thanks!
Wim
CALM - Co
Hello fellow TimeXtender users,
We were wondering: is it worth upgrading from SQL 2014 to 2016 in the scenario where we use TX traditionally: stage - dw - cubes.
Has anyone done it and have you seen performance improvements?
Thanks!
Wim
CALM - Co
I personally have not seen any difference using TX DWA with 2014 vs 2016. Anyone else?
I've not seen any difference in the typical scenarios we've upgraded for. One reason to upgrade is to be able to use Power BI on the cubes.
If you're running Enterprise edition you could benefit from better column store indexes on fact tables.
Thanks for the feedback everybody.
From Justin's feedback I gather that in theory cleansing rules should run faster. We are going to do some tests on our most complex ETLs and see if we see any performance difference.
I would say that with yesterday's announcement that SQL2016 SP moves support for compression, partitioning, columnstore from Enterprise Edition to Standard Edition, that would be a big reason for current 2014 Standard Edition upgrades to 2016:
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.