Re: [sqr-users] Thinking about trying something - looking for ideas

[Arun Kumar <arunkumar13@yahoo.com>]

I am not sure about this.

If all the data comes in to the PS database thru its front end then orphan rows 
are impossible to create in first place.

Orphans row exists because of data imported thru back doors and most of the 
time during the initial conversion.

Once you fixed those process you will never have orphans, right?

Just my 2 cents.



----- Original Message ----
From: "Overcashier, Patricia" <Patricia.Overcashier@aam.com>
To: This list is for discussion about the SQR database reportinglanguage from 
Hyperion Solutions. <sqr-users@sqrug.org>
Sent: Thursday, January 4, 2007 1:15:33 PM
Subject: RE: [sqr-users] Thinking about trying something - looking for ideas

John,
This sounds like it would be a very useful sqr.  Could you please pass
on any suggestions you may get.  I'm interested in looking for orphans
too and agree that it is easy to imagine and put together an sqr to do
that, using dynamic sqls selecting from the tools tables, but also agree
that it would take forever to run.  
Thanks,
Patti

-----Original Message-----
From: sqr-users-bounces+patricia.overcashier=aam.com@sqrug.org
[mailto:sqr-users-bounces+patricia.overcashier=aam.com@sqrug.org] On
Behalf Of john.tucker@oracle.com
Sent: Thursday, January 04, 2007 1:06 PM
To: sqr-users@sqrug.org
Subject: [sqr-users] Thinking about trying something - looking for ideas

I have a rather different question today.  I am thinking about writing
an SQR that would look for orphan data anywhere in a PeopleSoft
database, using PeopleTools tables to figure out what to look at rather
than using a static list of tables.  I have an idea or two about how to
go about this... but I wondered if anyone out here had already written
something similar and/or had some suggestions for things to do/avoid.

For example, there will be a lot of dynamic SQL getting processed in
this SQR.  Does that usually stop indexes from being used?  If so, is
there any way I can force indexes to be used?

Also, would it be better to say "select [whatever] from [child] where
not exists ([whatever] in [parent])" or would it be better to write two
select statements, pulling all rows from the child table and trying to
match them with rows in the parent table in a separate select statement?
Either way, I already know this thing is going to take forever to run.

I don't want you fine folks to do my work for me, but I was pretty sure
someone out there would have suggestions on how I can make this a
better, faster tool than the way I would have written it without asking.

-John T.


_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users

_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users






__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users