Re: 10053 Trace File anomolies

OK that makes sense, but the confusing part is that these 2 databases were exact clones of each other 2 days ago so they should be working off the same datasets.

The strange part is that the first join order that the optimizer checks in each of the 10053 traces is totally different.

Shouldn't they at least start with the same join order (as stated below - from Wolfgang Brietling's doc: A LOOK UNDER THE HOOD OF CBO: THE 10053 EVENT) "The initial join order is chosen by ordering the tables in order of increasing computed cardinality."

Matt Received on Mon Jun 27 2005 - 06:09:04 CDT