Depends on what you need.

exec spAnomResults qte = 1, Cost = 1

WITH ORS

Create proc spAnomResults @qte as int = null, @price as decimal(18,4) = null, @Cost as decimal(18,4) = null,...

Maybe I'm blind but I don't see anything wrong with the function. Have you tried this :

GO

create function calc_interest ( @principal int , @rate numeric(10,5) , @years int...

I wish I didn't lose the link to this great article about sets vs selects but :

"To sum it up very briefly - both is allowed, SET is recommended...

Maybe something like this could be a substitute for the OR requirements :

Create proc spAnomResults @qte as int = null, @price as decimal(18,4) = null, @Cost as decimal(18,4) =...

Think about what you just said.

Create proc spAnomResults @qte as int = null, @price as decimal(18,4) = null, @Cost as decimal(18,4) = null, @DateStart as datetime, @DateEnd as datetime, @CostPriceCheck...

assuming both fields are numbers

Select CAST(IDNUMBER as varchar(15)) + CAST(PRINTCOUNT as varchar(10)) as ConcatenatedField from dbo.MyTable

The short version :

SET is the AISNI 92 standard and you should use it unless you are doing err handling. In which case you have no choice but...

I'm not gonna say this again to you. DON'T USE DYNAMIC SQL FOR THIS.

Create proc spAnomResults @qte as int = null, @price as decimal(18,4) = null, @Cost as decimal(18,4) =...

HTH

Article on dynamic sql and why it should NOT be used... especially in this case.

http://www.sommarskog.se/dynamic_sql.html

Create proc spAnomResults @qte as int = null, @price as decimal(18,4) = null, @Cost as decimal(18,4) = null, @DateStart as datetime, @DateEnd as datetime

Select * from dbo.Orders where OrderDate between...

What I proposed will do it... but you will have to code something on the client side to check if the record has been updated, if yes then fetch the...

Are you thinking of using this method to lock records from further updates by different users?? If it's the case then you could use a timestamp column which is...

if the string is 20 then 20 unless it's nvarchar then it would be 40... plus 2 bytes overhead to keep the lenght of the string.

UT is the alias of the derived table. You can alias tables just like you alias columns.