Viewing 15 posts - 51,946 through 51,960 (of 59,102 total)
Thanks for the feedback, Marvin. Yeah, and if you throw in a check by IsDate, you can control the error instead of throwing it against the wall to see...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 7:03 pm
Thanks Timothy... That's why I normally don't use VBS scripts... I can do almost everything with T-SQL. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 6:59 pm
There's just nothing like someone providing instant confirmation for us folks just finally getting into 2k5... 🙂 Thanks, Matt.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 6:56 pm
rbarryyoung (3/10/2008)
Lynn Pettis (3/10/2008)
Cursors may be evil, but they may be a necessary evil...
In my experience they are necessary and acceptable for only one thing: variable-izing SQL objects in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 6:44 pm
kent waldrop (3/10/2008)
What are the circumstances for that? When I run the following query it get the commented results:
use tempdb
go
select name as before from sysobjects where type = 'U'
exec...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 5:15 pm
Guess it's time for porkchops here... Vika, if you want really good answers the first time around, see the URL in my signature line...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 5:03 pm
Pivot also has some limits... I believe you can only Pivot based on one column...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 5:00 pm
I disagree... a lookup or definition table better have a Primary Key...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 4:57 pm
Sorry Lynn... it was more directed at the OP than you...
Also, we'll probably disagree on this, but the new DATE only and TIME only datatypes are a real loss of...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 4:55 pm
Problem is... most people give up on trying to find a good set-based solution way too early...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 4:43 pm
OK, then move on to one that does interest you
Whether I agree or not, it's still interesting and dialog about such subjects are one way for folks to exchange ideas...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 3:14 pm
alorenzini (3/10/2008)
That worked fine. Thanks.
See above and reconsider how much hell you will go through if any of the dates ever come in with a time other than midnight... and...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 2:58 pm
Lynn Pettis (3/10/2008)
SELECT @startdate = CAST('2007' AS DATETIME)
SELECT @enddate = DATEADD(yy,1,CAST('2007' AS DATETIME)) - 1
I know why...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 2:56 pm
There are, of course, exceptions to every rule... but most people name a table after what a single row in the table holds. For example, the Customer table would...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 2:51 pm
First, I thought you said the "records" looked like this...
PunchIn, PunchOut, Break, PunchIn, Punchout.
Second... are your really happy with the solution? Try it with multiple days...
USE tempdb
go
Create Table Punches(empid...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 2:32 pm
Viewing 15 posts - 51,946 through 51,960 (of 59,102 total)