http://dustyreagan.com/haunting-sql-statement/ On Technology & Entrepreneurship Sat, 28 Jan 2012 10:10:30 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://dustyreagan.com/haunting-sql-statement/comment-page-1/#comment-21 Dusty Reagan Sat, 29 Jul 2006 02:57:00 +0000 http://dev.dustyreagan.com/?p=14#comment-21 Oh yes, that's quite an elegant solution to my language select list problem. Thanks for the input!I'm glad you enjoyed the haunted statement. As far as daisy chaining equality assignments in SQL being documented... sure it is! You can read about it on www.dustyreagan.com! ;) heheThanks again for the feedback Zackaroo. It's greatly appreciated. Oh yes, that’s quite an elegant solution to my language select list problem. Thanks for the input!I’m glad you enjoyed the haunted statement. As far as daisy chaining equality assignments in SQL being documented… sure it is! You can read about it on http://www.dustyreagan.com! heheThanks again for the feedback Zackaroo. It’s greatly appreciated.

]]> http://dustyreagan.com/haunting-sql-statement/comment-page-1/#comment-20 Zackaroo Wed, 05 Jul 2006 08:46:00 +0000 http://dev.dustyreagan.com/?p=14#comment-20 The haunting Sql statement article is <i>AWESOME</i>. All this time working in Sql, and I had no idea you could daisy chain equality assignments like that. Areyou sure that's documented? LOL.The language list though... I think you're taking 3 steps to do what could be done in 1. I know this is a small dataset so it's not obvious that even aseveralfold improvement in performance makes a practical difference, but... if this procis being called from a website that's getting hit by a gazillion users for example, it could become relevant. Also, you're doing an update statement at one point, which is a logged operation, which will also impact speed performance, and if you've got a gazillion usershitting your website, your log will start to fill up.The first thing you could do, is replace your temp table usage with a table variable, and do an insert into that, rather than a select into the temp table. Because table variables arescoped, SQL nows whatever table you're constructing will disappear after the code that's using it is done running. So, inserts, updates, and deletes into, to, and from table variables are <i>not</i> logged.But even simpler and faster, you could do this:select l.LanguageCode,lln.LanguageNamefrom dbo.LocalLanguageName llnjoin dbo.Language l on lln.LanguageId = l.LanguageIdwhere lln.LocalLanguageId = @LocalLanguageIdorder by case when l.LanguageCode = @LanguageCode then 0 else 1 end ,lln.LanguageNameBut man, I gotta go back and give you kudos for the haunting Sql thing a second time. I can already think of a dozen places in my own code where that will comein <i>very</i> handy. The haunting Sql statement article is AWESOME. All this time working in Sql, and I had no idea you could daisy chain equality assignments like that. Areyou sure that’s documented? LOL.The language list though… I think you’re taking 3 steps to do what could be done in 1. I know this is a small dataset so it’s not obvious that even aseveralfold improvement in performance makes a practical difference, but… if this procis being called from a website that’s getting hit by a gazillion users for example, it could become relevant. Also, you’re doing an update statement at one point, which is a logged operation, which will also impact speed performance, and if you’ve got a gazillion usershitting your website, your log will start to fill up.The first thing you could do, is replace your temp table usage with a table variable, and do an insert into that, rather than a select into the temp table. Because table variables arescoped, SQL nows whatever table you’re constructing will disappear after the code that’s using it is done running. So, inserts, updates, and deletes into, to, and from table variables are not logged.But even simpler and faster, you could do this:select l.LanguageCode,lln.LanguageNamefrom dbo.LocalLanguageName llnjoin dbo.Language l on lln.LanguageId = l.LanguageIdwhere lln.LocalLanguageId = @LocalLanguageIdorder by case when l.LanguageCode = @LanguageCode then 0 else 1 end ,lln.LanguageNameBut man, I gotta go back and give you kudos for the haunting Sql thing a second time. I can already think of a dozen places in my own code where that will comein very handy.

]]>