SSAS: Overview of models and models for the SSAS Analysis service under SQL Server 2012

There was an error deploying an SSAS project to the local server in SSDT

You cannot deploy the model because the localhost deployment server isn't running in multidimensional mode.

The reason for the error is that I only chose to install tabular mode when I installed SQL Server 2012 locally, and this demo project is a cube project, which is called multidimensional mode in SQL Server 2012.

Sometimes the projects we deploy are not necessarily on the local server sample, it is possible to deploy them in the remote server sample, so how do you know which mode the SSAS service on the remote server has installed?

A very simple approach is to connect to the remote server profiling service and then refer to this figure-showing instances of different SSAS models

The first is the multidimensional mode multi-dimensional data mining pattern, which is a simple understanding of the SSAS model we use on the SQL Server 2008/2008 R2 to support MOLAP, HOLAP, and ROLAP storage, as well as A multidimensional database of data mining models.

The second shows tabular Mode, a new SSAS solution in SQL Server 2012, a complete new product, a tabular model based on memory storage or directoryquery storage

The third shows that the SSAS instance is installed as part of a PowerPivot for SharePoint deployment.

Each pattern is mutually exclusive, and you cannot run the SSAS database of the multidimensional database model under the table model, as I mentioned at the beginning, in tabular mode I was unable to deploy a multidimensional mode project successfully.

It is also recommended that you do not attempt to install several different models into the same server instance, because my attempt did not succeed!

In the subsequent attempt, I also tried to install these different models to different server instances on the same server, and found that they could not be successful or character problem!

Error message-rule "Same Architecture installation" failed.

One important reason is that after the first installation of SQL Server 2012, a portion of Microsoft SQL Server 2008 appears in the system directory, and when you install SQL Server 2012 again, it sees a conflict between the two, so Validation failed!

Luckily I have different virtual machines on my computer, so I'm not going to waste time trying. And there is a very important premise is that unless your computer configuration is very high, do not install multiple SSAS services in the same system, the overhead will be very large.