Hi all
Firstly, apologies for the Sherlock Holmes-type reference. It is, however, accurate.
We've built a tabular cube using SSDT 2017 and deployed it on a SQL2016 Developers instance.
We can refresh it without any issues.
Firstly, apologies for the Sherlock Holmes-type reference. It is, however, accurate.
We've built a tabular cube using SSDT 2017 and deployed it on a SQL2016 Developers instance.
We can refresh it without any issues.