I’m working on a new universe at the same time our DBA is creating the underlying databases (Such a joy )
Because there are no views as of yet in the database, I’m making LOTS of derived tables in the Universe, with the understanding that most if not all will eventually become indexed views and/or tables once we begin performance testing…
I do not know if those views/tables will be made before or after our initial pilot rollout so I have to design the universe to actually work even if I have to use derived tables…
I just started a new set of tables to include and realized that I need to duplicate some of the derived tables… If they were true views/tables I’d simply alias them…
The question is from a performance standpoint… is there any difference If I were to Alias a Derived Table vs creating a 2nd Derived table with the same SQL Syntax?
I’m leaning toward aliasing so that when I eventually replace some of them with views, it’ll be easy to see which ones need to be replaced.
I thought as much… it just seems kind of silly from a logical standpoint…
And yes retesting will need to happen, but I do not have a choice… someone higher up already commited us to various clients as having our BOBJ system up and running in Jan, yet they don’t even have the database complete yet, nor even installed the ‘real’ version of BOBJ yet (I’m working off Trial licensing atm ).
Yet another fine example of Senior management dictating deadlines without really talking to the technology people to see what can and cannot be done.
I’m cutting so many corners that it makes my own head spin sometimes.
)
(BOB member since 2005-01-06)