Concur... trips through CHAR/VARCHAR conversions are somewhat slower especially over millions of rows.

Or, if the indexes are correct... an Index Scan which can be a little faster because there's usually fewer pages to step through. If...

Yes... it works.

No, no difference to the sever.

Yes... difference in readability but depends on what you're used to. I prefer the use of "=" to "IN" for single value...

This would be a very good place for you to lookup the POWER function in Books Online... it has a full explanation.

"Set-based" is the whole idea behind databases......

You code calls on V-1... i see no example of V_1.

Further... all of these views call on the table EmpBase... why do you need the views at all?

Instea of trying...

You crammin' for an interview or a test? Or, is this a take home test.

Please, do your own homework.

Not sure, but I think i answered this on the other post.

Yeah... you do...

Nope... that's pretty much it...

That's not a whole lot of information for me to go on...

I agree... and, if folks are going to post questions that have no backwards compatability, they should identify which version of SQL Server.

DECLARE @AsOfBeginDate datetime

DECLARE @ParmAsOfDate datetime

set @ParmAsOfDate='09/01/2007'

SET @AsOfBeginDate = dbo.uf_RptGetDayBeginDate(@ParmAsOfDate)--@ParmAsOfDate)

Print @AsOfBeginDate

The item hilighted in red is incorrect. It must be a SELECT...

DECLARE @AsOfBeginDate datetime

DECLARE @ParmAsOfDate datetime

set @ParmAsOfDate='09/01/2007'

SET @AsOfBeginDate = (SELECT...

Ok... that's for the "If I give the dates directly The stored procedure is giving the result is good." part you were talking about... but you also said "If I...

Can you show the code that you're calling the sproc with, please?