![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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 |
#3
| |||
| |||
|
|
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 |
#4
| |||
| |||
|
|
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 |
#5
| |||
| |||
|
|
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. |
#6
| |||
| |||
|
|
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 |
#7
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |