I know nothing about the intricacies of MS SQL but what I think he was getting at is that if you use a function in a query it will be evaluated for every row which will slow the query down whereas if you use variables which are preset to the function value the function is only evaluated once.
John Weller 01380 723235 07976 393631 > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Derek Kalweit > Sent: 15 May 2007 14:57 > To: [EMAIL PROTECTED] > Subject: Re: [NF]MSSQL Statement-- performance inconsistency? > > > > In MSSQL there is no such thing as getdate()-7. > > > > Why not just trim the idea a bit? > > > > SELECT distinct iUserID > > FROM OrderHistory > > WHERE tDate between dateadd(day, -7, getdate()) and > > getdate() > > Can you please explain? getdate()-7 works just fine-- I use implicit > dateadd math frequently with MSSQL. Open Query Analyzer and type > "select getdate(), getdate()-7" and hit F5-- notice you get results-- > the 7 is treated as 7 days. This may not be the best form for some > reason, but "there is no such thing" doesn't hold true... > _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
