![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
All, I'd appreciate a few words of advice if anyone's trod this path before. We've got an Oracle 9i database which contains the data for our cube. There are many reasons for this and we'd rather not have to re-write various modules to populate a SQL Server instance. We can connect easily from Analysis Services (2000 SP4) into this mart and it works well. The problem we have is that if you want to point at a different Oracle schema (e.g. from dev to production) MSAS stores the schema name in the cube definition and getting this updated is a real struggle. We've got a couple of sub-optimal solutions for this (based around utilities written in C# using the DSO library) but they don't work particularly well. Another alternative that we've come up with is to define the various Oracle tables as views in a SQL Server database via a linked server (using MSDAORA). This way the cube is built with reference to the SQL Server views, but we can easily repoint the linked server to different Oracle schemas with one easy update. So the deployment problem is solved but we are suffering a serious performance hit - going through SQL Server on to Oracle is much, much slower than direct to Oracle. Has anyone any suggestions as to what we might like to consider to speed up this solution? thanks, - chris. |
![]() |
| Thread Tools | |
| Display Modes | |
| |