Saxon

Legacy ID: #8420003 Legacy Poster: Michael Kay (mhkay)

Saxon-EE has a more powerful optimizer which will often dramatically improve the execution time for this kind of query - it seems fairly clear from your figures that there's probably some kind of join going on, and that's usually where the Saxon-EE optimizer comes into its own. There are two possibilities why you're not seeing an improvement. One is that your query isn't using any of the coding patterns that the optimizer recognizes and can handle (for example, it might be doing a non-equijoin); the second is that although you've downloaded the Saxon-EE software, you haven't actually activated it properly, which could be because it didn't find the license file, or something like that. The easiest way to guard against the second possibility is to use something (e.g. the -val option on the command line) that requires Saxon-EE to be enabled. If it's the first possibility - the optimizer isn't recognizing any opportunities for optimization - then I'm happy to take a look at it; the only way the optimizer improves is by adding to the set of coding patterns that it recognizes and handles specially. Or I might be able to suggest a better way of writing the query.