OLAP Cubes: Compatibility Between Analysis Services 2005 and 2008

I am working with Analysis Services and I am facing a compatibility issue. Here is my situation. I have 3 cars:

  • Server2005: This machine has SQL Server, Analysis Services and Visual Studio, all 2005 versions.
  • Client2008: This machine has Visual Studio 2008.
  • Client 2005: This machine has Visual Studio 2005

What I would like to do:

  • Developing cubes running on Client2008 and deploying on Server2005.

Problem:

  • I can read data and deploy cubes. However, when I try to "process" the cube, I get the error: Errors in the high-level relational engine. Failed to connect to data source using DataSourceID "xxxxx", "Name xxxxx". The impersonation information is set to "Use service account". I don't know why I can use the connection to read the data, I can deploy the cube (new AnalysisServices created in Server2005) but I cannot process the data.

Well-developed tests:

  • I can deploy and process cubes locally on Client2008 with SQL Server 2008.
  • I can deploy and process cubes locally on Server2005.
  • I can deploy and process cubes on Server2005 with Client2005.
  • Here's the weirdest of all: I am developing a cube using Client2005. I copy the visual project to Client2008 and update the project to use it with VS2008 and ... it works! However, if I designed the exact same cube with VS2008 from the beginning, I get the previous error. I compared the .ds files created with VS2005 and VS2008 and found no significant differences.

I dont know. Any help is appreciated, thanks!

+1


source to share


5 answers


The impersonation settings have changed slightly. The best solution is to ensure that your SQL Server database grants validate permissions to the Analysis Services service account.

You may also need to change the issue information of the data source connection:



Data Source> Impersonation Information tab

+1


source


When I talk about granting read permissions to a service account, I mean that Analysis Services is running under a different credential, so you can read data that the service cannot.

It's either SYSTEM, NETWORK SERVICE, or a special user account - type services.msc at the startup prompt to get a list of services ...



You need to grant this account the appropriate read permissions on your SQL database.

+1


source


Same problem here ... it looks like projects built in benn build VS2008 cannot be deployed in SQL Server Analysis Services 2005 ...

0


source


We had the same problem and just replaced a SQL Native 10.0 datasource with a SQL Server OLEDB datasource.

Pedro Gomez.

Luck

0


source


Which provider is your data source using?

If you are going to deploy to SQL Server 2005, you need to make sure the provider is "SQLNCLI.1" instead of "SQLNCLI10.1".

In your analysis project, double-click the data source and click Edit below the connection string. At the top there is a drop-down list where you can select the supplier you want. You need to have SQL Server Native Client 9.0 installed on your Client2008 (download here , search for "Microsoft SQL Server Native Client").

Alternatively, it should work if you are installing SQL Server Native Client 10.0 on your 2005 server (download here , search for "Microsoft® SQL Server® 2008 R2").

0


source







All Articles