Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
One Universe connected to several Databases
- Thread starter abdess
- Start date
This will only be usefull if the other databases are EXACTLY alike in structure. Every table and field has to be exactly the same. Try changing the connection in the universe parameter setting.... T. Blom
Information analyst
tbl@shimano-eu.com
Information analyst
tbl@shimano-eu.com
You can change the connection string in the universe. You can also assign different connection strings to different users from within Supervisor. That way you can have 1 universe that points to different database instances based on the login id.
I have seen this done many times by Application Providers who have a common structure, but separate databases for each client. Steve Krandel
BASE Consulting Group
I have seen this done many times by Application Providers who have a common structure, but separate databases for each client. Steve Krandel
BASE Consulting Group
Steve,
To comment upon your reply about using login id to select connection:
When working with version 4 we experienced a very serious bug when working this way (hard to recall how we exactly did it) but reports with multiple dataproviders only refreshed the first dataprovider when connection was switched. We were working with ORACLE then with a test and a production environment and were forced to do all reports on production environment, cause running the report on the testdatabase just refreshed the first of the multiple queries. Does that ring a bell with you? T. Blom
Information analyst
tbl@shimano-eu.com
To comment upon your reply about using login id to select connection:
When working with version 4 we experienced a very serious bug when working this way (hard to recall how we exactly did it) but reports with multiple dataproviders only refreshed the first dataprovider when connection was switched. We were working with ORACLE then with a test and a production environment and were forced to do all reports on production environment, cause running the report on the testdatabase just refreshed the first of the multiple queries. Does that ring a bell with you? T. Blom
Information analyst
tbl@shimano-eu.com
It does ring a bell, but I'm pretty sure that was resolved long ago. I'll do some testing with V5 to make sure. Steve Krandel
BASE Consulting Group
BASE Consulting Group
- Status
Similar threads
- Locked
- Question
- Locked
- Question