[thelist] MSSQL 2000 -> 2005 change?

[Ken Moore]

Hi all,

Two things come to mind. First is some kind of a query optimization. Try 
turning off any type of "help" that it gives. Second, MySQL 2005 does lots 
of close and reconnect to save on resources. Try putting this into a 
transaction to eliminate that.

Finally, a quick search on Google indicates that this is a problem 
associated with LEFT JOIN. See if you can re-write with out that.

Ken



Joel D Canfield wrote:


>I have 2000, client has 2005. I've scripted the db structure, which
>script ran fine on the client's box. Connected remotely, copied data
>from 2000 to 2005. Tried to run this query
>
>   select
>     e.firstname, e.lastname, e.didid, e.department, e.title,
>     o.number,
>     p.patchportnumber,
>     s.portnumber,
>     a.description
>   from
>     employees e
>     left join offices o on e.officeid = o.id
>     left join patchports p on p.officeid = o.id
>     left join switchports s on p.switchportid = s.id
>     left join assets a on s.assetid = a.id
>
>it tells me that firstname, lastname, didid, department, title, number,
>patchportnumber, and portnumber are not valid fields (it does not
>mention description)
>
>query runs fine on my 2000 box with identical structure and data. I
>assume this is some fun new difference with 2005.
>
>thoughts?
>
>thanks
>
>joel
>--

_________________________________________________________________
PC Magazine’s 2007 editors’ choice for best Web mail—award-winning Windows 
Live Hotmail. 
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_pcmag_0507