The number of records will have no bearing on the time taken to modify/create/delete a join. The join is simply a db view that defines the tables, columns, and relationship between two or more tables or views. When a query is executed against a db view (aka. join form), the work is done at that time to evaluate the results.
The longest time I've seen to create a join is when I create a join in the context of a deployable application. Not sure why, but arserverd floors the cpu and it takes a long time to initially create forms in general inside a deployable app. Probably has to do with the permission stripping/role translation that is performed when working in that context. We are talking in the neighborhood of 2 minutes. Axton Grams On 10/17/06, Joe DeSouza <[EMAIL PROTECTED]> wrote:
** Could I get some stats on the max time some of you took to rebuild a join form (after modifying the join criteria from the Remedy application level) between tables that have a record count of about 200K to 300K... What I want to know is after you save the join, how much time does it take to rebuild the join view internally in the DB.. is it instantanous? Or does it take a while during which time it might appear that records that were existing in the join are no longer in it and then when the join built is complete you get to see the 'missing' records? This may be a stupid question.. I am having a long day so for some reason I'm begining to doubt some of my knowledge on a couple of basics of table join.. I know this stuff takes time, but just wanted to reconfirm.. Rgds Joe. __20060125_______________________This posting was submitted with HTML in it___
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
