can we create single universe with multi sources(oracle&my sql) in universe design tool? if yes then how?

Cons for Single Universe - You would probably have to use contexts to keep users from building queries that mix data from different departments. This can be confusing for users. It's also more difficult to maintain because you have to manually make sure that the joins between tables are in the correct context. - There would be more tables, which can make the visual view of the tables and links in the universe more difficult to see - it probably won't fit on a single screen view unless you zoom out to where you can't read the table names. This makes it harder to see how things are put together. read less

Pros for Single Universe - There is a single place to make edits when something changes. Although from what you've described, you'd still have to make changes in multiple places in that universe. Cons for Single Universe - You would probably have to use contexts to keep users from building queries that mix data from different departments. This can be confusing for users. It's also more difficult to maintain because you have to manually make sure that the joins between tables are in the correct context. - There would be more tables, which can make the visual view of the tables and links in the universe more difficult to see - it probably won't fit on a single screen view unless you zoom out to where you can't read the table names. This makes it harder to see how things are put together. I can think of a couple of options that might make things easier, though. 1. If departments have tables that are essentially the same structure and "subject" for their data but with different names, create a view in the database that will "union" together the data for each set of similar tables. Include a static text field that will identify which department the data comes from. This way you could create a single universe on the views that would not be as complex as one on all of the tables. The down side of this would be that queries for data for one department will probably be slower using the view than just querying the tables for that department. 2. You might be able something like the following: - Create a separate "reporting" user ID for each department that is limited to seeing the tables for that department. - In the database, alias the tables and assign security in such a way that each department's tables have the exact same name as far the user ID created above can see. - Create a connection for each of the department users created above. - Create a "master" universe using one the user/department/connection combinations. - Use the master universe to create "linked" universes which have a different department connection but see the same table aliases which actually point to the different tables for that universe. Unfortunately, linked universes are only available for .unv universes created in XI 3.1 or earlier or in the legacy Universe Design Tool in 4.0. They're not available in the new .unx universes created with the Information Design Tool (IDT). read less