Creating a custom view to be used in Discoverer

Question

Hi Everyone,
I would like to create a view, that can be used in Discoverer.
I am new to Oracle and was wondering if
1) the hardcoded values in the WHERE clause can be made into variables
2) if (1) is true, can the Discoverer parms drive/be the values of the variables for the sql?
SQL statement is below,
tx for any assistance, Sandra
SELECT
S1.ID
, S1.NAME
, SA1.ACADEMIC_PERIOD
, SA1.STUDENT_ATTRIBUTE
, IJ.STUDENT_ATTRIBUTE
FROM STUDENT_ATTRIBUTE SA1
INNER JOIN STUDENT S1
     ON SA1.PERSON_UID = S1.PERSON_UID     
INNER JOIN
                         SELECT
                         SA2.ACADEMIC_PERIOD
                         , SA2.PERSON_UID
                         , SA2.STUDENT_ATTRIBUTE
                         FROM STUDENT_ATTRIBUTE SA2                              
                         WHERE SA2.ACADEMIC_PERIOD = '200920' AND
                         SA2.STUDENT_ATTRIBUTE = 'M4'
                         ) IJ
ON SA1.PERSON_UID = IJ.PERSON_UID                         
WHERE SA1.ACADEMIC_PERIOD = '200920' AND
     S1.ACADEMIC_PERIOD = '200920' AND
     SA1.STUDENT_ATTRIBUTE = 'SD'
ORDER BY S1.NAME

Answer 1

Hi Sandra
I'm glad you got it.
With regards to custom folders, I have to humbly disagree with the opinion expressed by my learned friend John. I have found that the most dramatic improvements I can make to a reporting system lie within the database. Within a tool there is usually nothing I can do to improve the performance that you get out of your database, but there is an awful lot you can do, and typically have done, to mess it up.
Above everything else, I am a reporting mentor and I get called in to work on systems where reporting is not working very well. I can tell you that rarely do I find that making changes to an EUL solves the problem.
Most of the time the fault lies in the database with it not being designed for reporting purposes. What I do is evaluate, formulate and activate. I analyze the problem, I work out the solution then I implement the solution. I have worked on systems where Discoverer reports, which granted are not the fastest in the world to begin with, have taken 30 minute or longer to run. When I am done I have these working in 1 minute or less. In a nutshell, or three words actually, you need to SIP your database, that is to summarize, index and partition the data within it in such a way that it has no choice but to behave.This is something you cannot do with a custom folder.
If anyone reading this is having trouble with a reporting system playing up you need to act now, change it or call someone who can, and make it perform the way you want. Your users will love you for it.
Best wishes
Michael
URL: http//ascbi.com
Blog: http://learndiscoverer.blogspot.com