dbTalk Databases Forums  

XMLA and data source config

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


Discuss XMLA and data source config in the microsoft.public.sqlserver.olap forum.



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

Default XMLA and data source config - 11-12-2004 , 02:01 PM






I am running XMLA 1.1 with Analysis Services 2000. In my
datasources.xml, I have the data source configured with:

<DataSourceInfo>Provider=MSOLAP.2;Data Source=local</DataSourceInfo>

When I try to run an XMLA request, I find that regardless of what
database I specify in the restrictions (e.g.,
<CATALOG_NAME>sales_dev</CATALOG_NAME>), the request always runs
against the *first* database on the server. If I add Initial
Catalog=sales_dev to the DataSourceInfo in datasources.xml, the XMLA
requests will run against that database, but, of course, only that
database.

So must I create a separate data source for each database on the
server? Is there no way to allow a single data source to access
multiple databases with XMLA? The XMLA SDK that MS provides doesn't
say a word about this, and the schema rowset definitions imply that
you can specify a different database. I mean, what would be the point
of having a CATALOG_NAME restriction if the datasource is
automatically restricted to a single database anyway?

Thanks,
Rick

Reply With Quote
  #2  
Old   
Dave Wickert [MSFT]
 
Posts: n/a

Default Re: XMLA and data source config - 11-12-2004 , 06:23 PM






There is a newsgroup dedicated to XMLA.
I would suggest that you repost this question on
microsoft.public.data.xmlanalysis
Several of the developers hang out there.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Rick Razzano" <rick.razzano (AT) gmail (DOT) com> wrote

Quote:
I am running XMLA 1.1 with Analysis Services 2000. In my
datasources.xml, I have the data source configured with:

DataSourceInfo>Provider=MSOLAP.2;Data Source=local</DataSourceInfo

When I try to run an XMLA request, I find that regardless of what
database I specify in the restrictions (e.g.,
CATALOG_NAME>sales_dev</CATALOG_NAME>), the request always runs
against the *first* database on the server. If I add Initial
Catalog=sales_dev to the DataSourceInfo in datasources.xml, the XMLA
requests will run against that database, but, of course, only that
database.

So must I create a separate data source for each database on the
server? Is there no way to allow a single data source to access
multiple databases with XMLA? The XMLA SDK that MS provides doesn't
say a word about this, and the schema rowset definitions imply that
you can specify a different database. I mean, what would be the point
of having a CATALOG_NAME restriction if the datasource is
automatically restricted to a single database anyway?

Thanks,
Rick



Reply With Quote
  #3  
Old   
Mosha Pasumansky [MS]
 
Posts: n/a

Default Re: XMLA and data source config - 11-12-2004 , 06:59 PM



XMLA model is the same as OLEDB - session is tied to single
catalog/database. You can certainly change you current catalog, by either
changing <Catalog> XMLA property, or using "USE <database>" MDX command, but
you cannot work with 2 or more databases at the same time.

--
==================================================
Mosha Pasumansky - http://www.mosha.com/msolap
Analysis Services blog at http://www.sqljunkies.com/WebLog/mosha
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================

"Rick Razzano" <rick.razzano (AT) gmail (DOT) com> wrote

Quote:
I am running XMLA 1.1 with Analysis Services 2000. In my
datasources.xml, I have the data source configured with:

DataSourceInfo>Provider=MSOLAP.2;Data Source=local</DataSourceInfo

When I try to run an XMLA request, I find that regardless of what
database I specify in the restrictions (e.g.,
CATALOG_NAME>sales_dev</CATALOG_NAME>), the request always runs
against the *first* database on the server. If I add Initial
Catalog=sales_dev to the DataSourceInfo in datasources.xml, the XMLA
requests will run against that database, but, of course, only that
database.

So must I create a separate data source for each database on the
server? Is there no way to allow a single data source to access
multiple databases with XMLA? The XMLA SDK that MS provides doesn't
say a word about this, and the schema rowset definitions imply that
you can specify a different database. I mean, what would be the point
of having a CATALOG_NAME restriction if the datasource is
automatically restricted to a single database anyway?

Thanks,
Rick



Reply With Quote
  #4  
Old   
Marco Groeneveld
 
Posts: n/a

Default Re: XMLA and data source config - 11-13-2004 , 02:43 PM



You can visit www.reportportal.com and see the settings in the
tutorial or the download of ReportPortal.

Regards, Marco
www.gmsbv.nl


"Mosha Pasumansky [MS]" <moshap (AT) online (DOT) microsoft.com> wrote

Quote:
XMLA model is the same as OLEDB - session is tied to single
catalog/database. You can certainly change you current catalog, by either
changing <Catalog> XMLA property, or using "USE <database>" MDX command, but
you cannot work with 2 or more databases at the same time.

--
==================================================
Mosha Pasumansky - http://www.mosha.com/msolap
Analysis Services blog at http://www.sqljunkies.com/WebLog/mosha
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================

"Rick Razzano" <rick.razzano (AT) gmail (DOT) com> wrote in message
news:bed48cb5.0411121201.1af6d917 (AT) posting (DOT) google.com...
I am running XMLA 1.1 with Analysis Services 2000. In my
datasources.xml, I have the data source configured with:

DataSourceInfo>Provider=MSOLAP.2;Data Source=local</DataSourceInfo

When I try to run an XMLA request, I find that regardless of what
database I specify in the restrictions (e.g.,
CATALOG_NAME>sales_dev</CATALOG_NAME>), the request always runs
against the *first* database on the server. If I add Initial
Catalog=sales_dev to the DataSourceInfo in datasources.xml, the XMLA
requests will run against that database, but, of course, only that
database.

So must I create a separate data source for each database on the
server? Is there no way to allow a single data source to access
multiple databases with XMLA? The XMLA SDK that MS provides doesn't
say a word about this, and the schema rowset definitions imply that
you can specify a different database. I mean, what would be the point
of having a CATALOG_NAME restriction if the datasource is
automatically restricted to a single database anyway?

Thanks,
Rick

Reply With Quote
  #5  
Old   
Rick Razzano
 
Posts: n/a

Default Re: XMLA and data source config - 11-13-2004 , 10:26 PM



Mosha -

Thanks, the <Catalog> property was what I was looking for. I'm not
trying to use more than one db in a request, just to have one
datasource provide the means to connect to any of the dbs on the
server.

Rick

"Mosha Pasumansky [MS]" <moshap (AT) online (DOT) microsoft.com> wrote

Quote:
XMLA model is the same as OLEDB - session is tied to single
catalog/database. You can certainly change you current catalog, by either
changing <Catalog> XMLA property, or using "USE <database>" MDX command, but
you cannot work with 2 or more databases at the same time.


Reply With Quote
  #6  
Old   
Les Russell
 
Posts: n/a

Default Re: XMLA and data source config - 11-15-2004 , 10:08 PM



Does anyone know how to get the below-mentioned newsgroup? I can't seem to
find it in the MSDN newsgroups menu.

"Dave Wickert [MSFT]" wrote:

Quote:
There is a newsgroup dedicated to XMLA.
I would suggest that you repost this question on
microsoft.public.data.xmlanalysis
Several of the developers hang out there.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Rick Razzano" <rick.razzano (AT) gmail (DOT) com> wrote in message
news:bed48cb5.0411121201.1af6d917 (AT) posting (DOT) google.com...
I am running XMLA 1.1 with Analysis Services 2000. In my
datasources.xml, I have the data source configured with:

DataSourceInfo>Provider=MSOLAP.2;Data Source=local</DataSourceInfo

When I try to run an XMLA request, I find that regardless of what
database I specify in the restrictions (e.g.,
CATALOG_NAME>sales_dev</CATALOG_NAME>), the request always runs
against the *first* database on the server. If I add Initial
Catalog=sales_dev to the DataSourceInfo in datasources.xml, the XMLA
requests will run against that database, but, of course, only that
database.

So must I create a separate data source for each database on the
server? Is there no way to allow a single data source to access
multiple databases with XMLA? The XMLA SDK that MS provides doesn't
say a word about this, and the schema rowset definitions imply that
you can specify a different database. I mean, what would be the point
of having a CATALOG_NAME restriction if the datasource is
automatically restricted to a single database anyway?

Thanks,
Rick




Reply With Quote
  #7  
Old   
Deepak Puri
 
Posts: n/a

Default Re: XMLA and data source config - 11-16-2004 , 12:11 AM



You can access it via Google groups - even the Microsoft web-site lists
this link for the xmlanalysis newsgroup:

http://groups.google.com/groups?hl=e...icrosoft.publi
c.data.xmlanalysis


- Deepak

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

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.