InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 20 Jun 2013 06:24:51 GMT20http://www.sqlservercentral.com/Forums/Topic148433-163-1.aspx<P>The first part of the procedure is good enough, but a better solution could be done for the final evaluation. Instead of using a temporary table, we can use output parameters in the sp_executesql procedure, like this:</P><PRE><FONT color=#1111ff>SET @boolExp='SELECT @res=CASE ABS(' + @boolExp + ') WHEN 1 THEN ''TRUE'' ELSE ''FALSE'' END'EXEC sp_executesql @boolExp, N' @res varchar(5) OUTPUT', @res OUTPUT</FONT><FONT color=#1111ff></PRE></FONT><P>This way, we replace about 5 lines of code with only 2 and avoid the overhead of using a temporary table. To use the sp_executesql procedure we need to change the type of the @boolExp parameter to nvarchar(300) instead of varchar(300).</P><P>Razvan</P><P>PS. The SET NOCOUNT OFF and the DROP TABLE #temp at the end of the procedure are useless (because they are done anyway, automatically). Also useless is the big BEGIN/END block that contains the entire procedure.</P>Wed, 22 Dec 2004 03:24:00 GMTRazvan Socolhttp://www.sqlservercentral.com/Forums/Topic148433-163-1.aspxComments posted to this topic are about the content posted at <A HREF=http://www.sqlservercentral.com/columnists/lPeysakhovich/evaluatingbooleanexpressionsusingtsql.asp>http://www.sqlservercentral.comMon, 29 Nov 2004 13:06:00 GMTLeo Peysakhovich