MS SQL Server OLAP - connection string differences 2005 to 2000?

Author

connection string differences 2005 to 2000?

Simmo

2005-11-22, 7:23 am

Hi all,

Just wondered if anyone knew of any key differences in connection strings
when connecting to 2005 rather than 2000 Analysis Services? Also are there
any enhancements or funky new options available?

thanks
--
Simmo

Raman Iyer [MS]

2005-11-22, 8:24 pm

AS2005 connection strings are fully compatible with AS2000 - however, there
are some properties whose values will be ignored since they no longer make
sense for AS2005 (which doesn't have a thick client architecture like AS2000
PivotTableServices).
There are several new properties for AS2005 (see Books Online for details):
SQLQueryMode
Protocol Format
Transport Compression
Compression Level
Character Encoding
Encryption Password
Real Time Olap
ConnectTo (allows to to specify whether you're connecting to an 8.0 or 9.0
server so the provider does not attempt connecting to both versions)
EffectiveUserName
MDX Missing Member Mode

Also, all XMLA properties can be passed through to the server from the
connection string.

--
-Raman Iyer
SQL Server Data Mining
[This posting is provided "AS IS" with no warranties, and confers no
rights.]

"Simmo" <Simmo@discussions.microsoft.com> wrote in message
news:0A5835D3-CA05-4C84-A627- 391F3D01D0E1@microso
ft.com...
> Hi all,
>
> Just wondered if anyone knew of any key differences in connection strings
> when connecting to 2005 rather than 2000 Analysis Services? Also are there
> any enhancements or funky new options available?
>
> thanks
> --
> Simmo

Simmo

2005-11-24, 7:23 am

Hi thanks for that, however I cant find any information on some of the
parameters you put:

SQLQueryMode:
Real Time Olap:
EffectiveUserName:
MDX Missing Member Mode:

"Raman Iyer [MS]" wrote:

> AS2005 connection strings are fully compatible with AS2000 - however, there
> are some properties whose values will be ignored since they no longer make
> sense for AS2005 (which doesn't have a thick client architecture like AS2000
> PivotTableServices).
> There are several new properties for AS2005 (see Books Online for details):
> SQLQueryMode
> Protocol Format
> Transport Compression
> Compression Level
> Character Encoding
> Encryption Password
> Real Time Olap
> ConnectTo (allows to to specify whether you're connecting to an 8.0 or 9.0
> server so the provider does not attempt connecting to both versions)
> EffectiveUserName
> MDX Missing Member Mode
>
> Also, all XMLA properties can be passed through to the server from the
> connection string.
>
> --
> -Raman Iyer
> SQL Server Data Mining
> [This posting is provided "AS IS" with no warranties, and confers no
> rights.]
>
> "Simmo" <Simmo@discussions.microsoft.com> wrote in message
> news:0A5835D3-CA05-4C84-A627- 391F3D01D0E1@microso
ft.com...
>
>
>

Simmo

2005-11-24, 7:23 am

Cant find anything on the below in BOL, any further info much appreciated?

SQLQueryMode:
Real Time Olap:
EffectiveUserName:
MDX Missing Member Mode:

--
Simmo

"Raman Iyer [MS]" wrote:

> AS2005 connection strings are fully compatible with AS2000 - however, there
> are some properties whose values will be ignored since they no longer make
> sense for AS2005 (which doesn't have a thick client architecture like AS2000
> PivotTableServices).
> There are several new properties for AS2005 (see Books Online for details):
> SQLQueryMode
> Protocol Format
> Transport Compression
> Compression Level
> Character Encoding
> Encryption Password
> Real Time Olap
> ConnectTo (allows to to specify whether you're connecting to an 8.0 or 9.0
> server so the provider does not attempt connecting to both versions)
> EffectiveUserName
> MDX Missing Member Mode
>
> Also, all XMLA properties can be passed through to the server from the
> connection string.
>
> --
> -Raman Iyer
> SQL Server Data Mining
> [This posting is provided "AS IS" with no warranties, and confers no
> rights.]
>
> "Simmo" <Simmo@discussions.microsoft.com> wrote in message
> news:0A5835D3-CA05-4C84-A627- 391F3D01D0E1@microso
ft.com...
>
>
>

Akshai Mirchandani [MS]

2005-11-29, 8:24 pm

Brief descriptions below but if they're not documented they're not supported
:)

SQLQueryMode -- Calculated/Data. SQL queries return either calculated
results or lowest pass results. The lowest pass mode is used by local cubes
to process the local cube from server cube's lowest pass data. You need
extra permission to fetch lowest pass data

Real Time Olap: true/false. Default is false -- if you turn this on, then
the query will ignore the in-memory caches of storage engine data and go
directly to the source data for each partition (MOLAP will go to MOLAP data
and ROLAP will execute relational queries).

EffectiveUserName: Allows impersonating another user when privilege is
available. Requires S4U Windows support to be setup.

MDX Missing Member Mode: Default/Ignore/Error. If a name in the MDX query
cannot be resolved, the server can either ignore it or raise an error.

Thanks,
Akshai
--
This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Simmo" <Simmo@discussions.microsoft.com> wrote in message
news:D29ECBFA-D6F0-428F-840B- 7040A3480890@microso
ft.com...[color=darkred]
> Cant find anything on the below in BOL, any further info much appreciated?
>
> SQLQueryMode:
> Real Time Olap:
> EffectiveUserName:
> MDX Missing Member Mode:
>
> --
> Simmo
>
>
> "Raman Iyer [MS]" wrote:
>

Sponsored Links