Viewing 15 posts - 53,251 through 53,265 (of 59,089 total)
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2007 at 10:34 pm
You crammin' for an interview or a test? Or, is this a take home test.
Please, do your own homework.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2007 at 10:24 pm
Not sure, but I think i answered this on the other post.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2007 at 10:12 pm
but we don't want to implement both and then run timings to determine which is better.
Yeah... you do...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2007 at 10:06 pm
Nope... that's pretty much it...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2007 at 10:03 pm
That's not a whole lot of information for me to go on...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2007 at 10:02 pm
I agree... and, if folks are going to post questions that have no backwards compatability, they should identify which version of SQL Server.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2007 at 10:15 am
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2007 at 10:08 am
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 29, 2007 at 8:09 pm
Can you show the code that you're calling the sproc with, please?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 29, 2007 at 7:40 pm
I believe you're missing the sample in your post...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 29, 2007 at 6:13 pm
What is v_un, v_1, v_2, etc, etc? They're views aren't they? You should probably post at least 1 of those and some easy to load data... see...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 29, 2007 at 5:56 pm
Heh... thought you said you "Frankly, I don't want to waste time working on something that's a bad idea or trying to prove which one is better"
--Jeff Moden
Change is inevitable... Change for the better is not.
December 29, 2007 at 5:48 pm
Nah... they've got views for that stuff...
SELECT *
FROM Information_Schema.Columns
WHERE Data_Type = 'UniqueIdentifier'
--Jeff Moden
Change is inevitable... Change for the better is not.
December 29, 2007 at 11:52 am
james.simonsen (12/18/2007)
Thanks! Now how do I do that on a regular calculator other than press the keys 36 times?
Ummm... Windows' calculator has a very nice scientific mode. And Jason...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 29, 2007 at 11:02 am
Viewing 15 posts - 53,251 through 53,265 (of 59,089 total)