Sergey,

I do not see much of a difference here and don't think there would be any difference in optimizing.

Please read http://blogs.lessthandot.com/index.php/DataMgmt/DataDesign/avoid-conversions-in-execution-plans-by-

and

http://blogs.lessthandot.com/index.php/DataMgmt/DataDesign/changing-exec-to-sp_executesql-doesn-t-p

for more in depth discussion.

>Hello All.
>What code is more likely for SQL Server query optimizer :
>
>

>DECLARE @IntVariable INT;
>DECLARE @SQLString NVARCHAR(500);
>DECLARE @ParmDefinition NVARCHAR(500);
>
>/* Build the SQL string one time. */
>SET @SQLString =
>     N'SELECT * FROM AdventureWorks.Sales.Store WHERE SalesPersonID = @SalesID';
>/* Specify the parameter format one time. */
>SET @ParmDefinition = N'@SalesID int';
>
>/* Execute the string with the first parameter value. */
>SET @IntVariable = 275;
>EXECUTE sp_executesql @SQLString, @ParmDefinition,
>                      @SalesID = @IntVariable;
>

>or
>
>

>DECLARE @IntVariable INT;
>DECLARE @ParmDefinition NVARCHAR(500);
>
>/* Build the SQL string one time. */
>SET @SQLString =
>     N'SELECT * FROM AdventureWorks.Sales.Store WHERE SalesPersonID = @SalesID';
>/* Specify the parameter format one time. */
>SET @ParmDefinition = N'@SalesID int';
>
>/* Execute the string with the first parameter value. */
>SET @IntVariable = 275;
>EXECUTE sp_executesql N'SELECT * FROM AdventureWorks.Sales.Store WHERE SalesPersonID = @SalesID',
>          @ParmDefinition,
>          @SalesID = @IntVariable;
>