![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
#4
| |||
| |||
|
#5
| |||
| |||
|
|
Further to my previous post; what I really want to do is have two data sources, one for the test database server and one for the live, and be able to process some cubes on live and some on test - seems reasonable I think, but from what I read it seems it can't be done once the cubes are created, because they will include dimensions with a specific data source and so the only way of pointing them at a different server is to amend the Sybase data source - which will then affect any cubes using that data source, so it is all or nothing! Surely this can't be the way Analysis Services is designed to work? I would really appreciate comments from any Microsoft people... |
#6
| |||
| |||
|
#7
| |||
| |||
|
#8
| |||
| |||
|
|
I have now tested a cube which was created using the test database server data source for both the cube and the dimensions; I changed the datasource to point at the live database server and successfully processed it on the live server. Therefore, I think the problem may be to do with the fact that some of the other cubes have been copied & pasted from the live AS server and somewhere the connection has been cached. Could this be so? Rachel |
#9
| |||
| |||
|
#10
| |||
| |||
|
|
If I change the data source to point at the test server and restart the service, I find that the only cubes which still look OK are the two which I have been unable to process (as they keep giving me a "socket closed" error which I have been unable to resolve) - all the others now say they cannot find the fact tables and have consequently lost all their joins in the cube schema - but all these tables DO exist on the test server. When I test the connection in the Sybase OLEDB Configuration manager it succeeds. Rachel Jones IT Developer Talbot Underwriting Ltd *** Sent via Developersdex http://www.developersdex.com *** |
![]() |
| Thread Tools | |
| Display Modes | |
| |