Joinutility seperatorLogin utility separator Infobright.com
   
 
sql 89 and sql 92
Posted: 02 December 2009 03:51 AM   Ignore ]  
Newbie
Rank
Total Posts:  16
Joined  2009-07-10

Is there a difference performance wise between sql 89 and sql 92. I admit we should be using sql 92. But I am using Microstrategy and if I use sql 92 it produces a cross join and if I use sql 89 it does normal join.
Although the results with cross join and join in the current specific case are identical. It is just how Microstrategy engine generates sql in one of the cases I am dealing with.
With sql 89 it is producing exact sql that I want. So can I stick to an older syntax for few cases.
Please share your thoughts. I apologise for an abstract question but would be more than happy to post detailed question if the information is not adequate and more is required for a correct answer.
Thanks a lot,
Som

Profile
 
Posted: 02 December 2009 10:26 AM   Ignore ]   [ # 1 ]  
Sr. Member
Avatar
RankRankRankRank
Total Posts:  505
Joined  2008-08-18

It turns out that in a few specific cases, there can be a difference based on the way the SQL is processed by the MySQL query parser. In general it is safer to use SQL 89 syntax. In most cases there is no difference, but we know of a few specific cases where the SQL 92 performs worse than SQL 89.

For outer joins, you have to use the SQL 92 syntax.

See attached screenshots for how to set up the MicroStrategy VLDB settings for Infobright.

Geoffrey

[ Edited: 02 December 2009 10:48 AM by Geoffrey Falk]
Image Attachments  vldb2.pngvldb1s.pngvldb3.pngvldb4.pngvldb5.png
Signature 
Profile
 
   
 
 
‹‹ api supported      Ruby development with ICE ››