Should I expect any problems installing a SQL Server Analysis Services 2016 tabular instance next to a SQL Server 2014 database engine? (e.g. due to an update of some shared components)

I'm mostly worried about any issues related to the running database engine.


  • By "Next to" do you mean on the same server (or VM) or do you mean having SSAS 2016 pull data from SQL 2014? – Greg Jan 30 '18 at 21:42

It is best to keep a server dedicated to a single version of SQL Server and/or its components. You can run into connectivity issues or have components stop working as expected due to the mismatched version of the shared components. I recently had an instance where someone upgraded the SSIS components and prevented us from opening packages properly on that box any more.

Additionally, if you can avoid it, keep SSAS and the engine separated as both do not like to share resources properly. You could end up with performance issues if you do not configure things properly.


Unless you are out of options, it is not the best recommended practices to put these two services together in a single machine. if you have to do, follow some of recommended course of actions during and post deployment such min/max memory setting, using different data and log files...

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.