*= and =* are NON-ANSI standard LEFT and RIGHT OUTER joins. THis is
supported only in the compatibility level 80 (SQL 2000) and lower versions.
If the database compatibility is 90 (SQL 2005) then you may need to right
the query using LEFT OUTER JOIN or RIGHT OUTER JOIN.
I've heard a rumour that the *= notation is no longer supported in SQL
Server 2005. I've searched through the knowledge base but can't find any
articles on it. If anybody who currently has 2005 could confirm whether
it
is or isn't supported that would be great.
Re: Query with left outer join all of a sudden wont work? ... just doesn't work if it is a left or right outer join.... rather than on the top most query calling it). ... SELECT * FROM [qryFarmer Contracts]... can you post the whole SQL statement?... (microsoft.public.access.queries)
Re: Need help to modify my query ... This is not very well-suited to SQL,... Here's a query that will produce this report - it works ... then uses an outer join, since there may be different numbers ... left outer join S_usergroup as sug... (microsoft.public.sqlserver.programming)
Re: Using q() to define a query ... I beleive most SQL parsers will ignore white space like that in an SQL query. ... FULL OUTER JOIN jsequipment AS eq ON jsjourneys.equipment = eq.id ... If those were really in the query, I can't imagine the database would run it, so I suppose they're an artifact of the combination of using qto quote my query and using Apache's logger to output it. ... (perl.dbi.users)
again and again... query analyzer and wrong SQL statement plan... + outer join? ... again we have some SQL statement performance problems...... we have aproblem with a query which use 1 inner join and 3 left outer ... Each outer join is a sub-query which contain a group by: ... This query takes more then 10 minutes, but if I precalculate each sub-query... (microsoft.public.sqlserver.datawarehouse)
Re: Cartesian product & outer join ... An Ambiguous Outer Join basically means that your arrows are pointing the ... My suggestion to most query problems is to not try to do it in just one ... >> Post your SQL.... >>> time with overtime time categories and multiplies by civilian overtime ... (microsoft.public.access.queries)
