Viewing 15 posts - 51,916 through 51,930 (of 59,067 total)
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
dan (3/10/2008)
Some dates appear as '20080310' and others appear as '10/03/2008'.I have been asked to make all the dates appear consistently, as '20080310'. I've tried several variations of this:
You...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 2:06 pm
I have an OrderLookup table, where the PK is the PurchaseOrderID.
You actually named a table "OrderLookup" to hold Purchase Orders and gave it a Primary Key on a column called...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 1:49 pm
Will C2 Auditing help in this area?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 1:45 pm
Ummmm... let me get this straight... you got a job as a designer and you don't really know how to design?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 1:43 pm
SELECT CAST('2007' AS DATETIME)
SELECT DATEADD(yy,1,CAST('2007' AS DATETIME))
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2008 at 1:42 pm
Viewing 15 posts - 51,916 through 51,930 (of 59,067 total)