dbTalk Databases Forums  

connection string differences 2005 to 2000?

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap


Discuss connection string differences 2005 to 2000? in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Simmo
 
Posts: n/a

Default connection string differences 2005 to 2000? - 11-22-2005 , 05:31 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

Reply With Quote
  #2  
Old   
Raman Iyer [MS]
 
Posts: n/a

Default Re: connection string differences 2005 to 2000? - 11-22-2005 , 02:01 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 (AT) discussions (DOT) microsoft.com> wrote

Quote:
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



Reply With Quote
  #3  
Old   
Simmo
 
Posts: n/a

Default Re: connection string differences 2005 to 2000? - 11-24-2005 , 05:26 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:

Quote:
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 (AT) discussions (DOT) microsoft.com> wrote in message
news:0A5835D3-CA05-4C84-A627-391F3D01D0E1 (AT) microsoft (DOT) 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




Reply With Quote
  #4  
Old   
Simmo
 
Posts: n/a

Default Re: connection string differences 2005 to 2000? - 11-24-2005 , 05:27 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:

Quote:
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 (AT) discussions (DOT) microsoft.com> wrote in message
news:0A5835D3-CA05-4C84-A627-391F3D01D0E1 (AT) microsoft (DOT) 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




Reply With Quote
  #5  
Old   
Akshai Mirchandani [MS]
 
Posts: n/a

Default Re: connection string differences 2005 to 2000? - 11-29-2005 , 03:56 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 (AT) discussions (DOT) microsoft.com> wrote

Quote:
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 (AT) discussions (DOT) microsoft.com> wrote in message
news:0A5835D3-CA05-4C84-A627-391F3D01D0E1 (AT) microsoft (DOT) 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






Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.