When you say moving to DB2, what is the current DB datasource being used?
If its a totally different DB then you need to probably do modifications in the universe for any derived object containing functions specific to current datasource, apart from some tweakings and testing to be carried out while running DeskI reports
That said, there should be no changes on the report side unless the generated SQL in query panel has been overridden
.
Thanks for the suggestions.
The current data source is Sybase.
What type of testing should be carried out in Deski? Anything specific? We have lots of reports having Custom SQL, so I believe this SQL has to be modified and validated again… Any thing specific for custom SQLreports?
Thanks…
Reports don’t always re-point well, unfortunately. I have found Deski re-point better than Webi, even with the Webi new mapping feature, I have founf formulae break .
Also, you are shafted if you have multiple Dps from different universes - Webi re-points all queries
If the data structures are going to be the same, I would probably go with re-pointing the - existing - universe and making amendments to the existing objects, or replacing the universe, see here:-
Well, you have just hit the nail on the head with regards to, not ,running custom SQL in production .
This is going to be a major overhead, especially if many non-Ansi SQL functions are used, as Haider previously mentioned.
A question Strike now to my mind.
If we point to a Webi report (Which has Custom SQL) from a Sybase Universe to a DB2 Universe, will my Custom SQL be lost?