Viewing 15 posts - 56,626 through 56,640 (of 59,086 total)
Heh... "Employe" is a "short timer"
Had to leave something for him to troubleshoot ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2007 at 8:32 am
Oh yeah... I like the ROW_Number thing, especially. Haven't had the pleasure of using it in 2k5 but have done some cool things with it in (yeech) Oracle.
On the time...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 7, 2007 at 12:00 am
Whew! Thought I had a "senior moment" or something. Thanks for the feed back.
I used the date comparisons I did because I didn't know if times were involved nor whether...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2007 at 10:27 pm
Uh oh... whose tests failed? I was pretty sure I tested all 4 scenarios you posted and was pretty sure they came out right. 'Course, it's late and I might...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2007 at 10:18 pm
p.p.s..... you don't need a CTE for this... the derived tables have nothing in common. EXCLUDE will probably work but that's a poor man's excuse for a good solid OUTER...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2007 at 9:57 pm
By the way... it looks like it'll be a tiny bit faster if you change this...
ON inc.EmployeeID = exc.EmployeeID
... to this...
ON a.EmployeeID = exc.EmployeeID
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2007 at 9:54 pm
Heh... sorry Jason... had to make sure... the post was too perfect (well done, by the way!!!)... you should teach! You had "Use Cases" and everything!
Anyway, using the test tables...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2007 at 9:47 pm
Outstanding post, Jason... everything is there and very easy to read... while I'm looking at this, tell me what you've tried just so reassure me that this isn't homework, please.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2007 at 8:20 pm
Halifaxdal,
I/we are trying to help... in order to do that, I need answers to the questions I posed, earlier. Of course, if you don't want the help or think you can...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2007 at 7:49 pm
David,
What I was looking at were the numbers from one of the previous posts (reprinted here for convenience...)
Warning: The table 'IISLog' has been created but its maximum row size (13625)...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2007 at 7:38 pm
Thanks for the kudo, Dave.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2007 at 7:26 pm
Did you even try to figure out the error, Frances? Remember, lot's of folks don't have the time to setup test data if you don't provide it in an INSERT/SELECT...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2007 at 6:11 pm
A 25 column covering index just might do it
... but I'm thinking the view is written incorrectly. Do you have calculations on the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2007 at 6:03 pm
I'm thinking you still need to remove the "e." from the column alias... everything else in David's post should be just about spot on.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2007 at 5:36 pm
Oh.... that's why the turnover rate is so high ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2007 at 5:31 pm
Viewing 15 posts - 56,626 through 56,640 (of 59,086 total)