universes versus database views

[#1]

why would we use universes versus database views to store sql/formulas/calculations (other than the fact WEBI has to use it)? this is assuming crystal reports only

[Former Member · Accepted solution]

Hello,

just to add the some more thoughts.

Universes have a full user and security management.

Universes can be managed offline apart from the application.

Universes can handle even very complex SQL structures in an easy -to -learn GUI.

I recommend to use universes with this in mind.

Nevertheless Crystal Reports has a strong database engine and only in really complex scenarios one should use universes as database layer for CR.

It can be very complex to troubleshoot problems in thoses scenarios.

Just my thoughts

[Former Member]

Kevin,

I am a big supporter of using Crystal Reports. I've been using Crystal for a while.

However, there is a difference between using universes and database views. I tend to use stored procedures more than I would a database view just because it is using the compiled code. However, if you use a database view and need to add a command, you will get a plain dialog box asking for SQL and parameters.

If you are using a universe and add a command, you are going to get the Business Objects query panel. With this query panel, you can add a combined query, add a sub query, look at the SQL, add fields, set whether you want to see unique values and designate how many rows are returned.

All this can be done using SQL. However, the difference is for those that can't access the database when they want. They would have to have permissions (and the know how) to modify the database view as they want or create a new one. If a universe has been set up for them, they can manipulate the universe as they want.

If order to use a database view and add a command, you would have to know the SQL pretty well to do the same things. Not a pretty GUI to use.

Hope that helps.

Glenn