Viewing 15 posts - 39,061 through 39,075 (of 59,098 total)
olie480 (4/5/2010)
CirquedeSQLeil (4/5/2010)
olie480 (4/5/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2010 at 6:14 pm
CirquedeSQLeil (4/5/2010)
Jeff Moden (4/4/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2010 at 6:07 pm
CirquedeSQLeil (4/5/2010)
Jeff Moden (4/5/2010)
Tom.Thomson (4/5/2010)
who are prepared to lie about how much testing they have done because they think they will get away with it.
Heh... I love it when...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2010 at 5:45 pm
CirquedeSQLeil (4/5/2010)
Jeff Moden (4/5/2010)
I'd rather see the discussion continue on the thread which started it all rather than essentially double posting. Sorry Jason.
I know. There are reasons to...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2010 at 5:32 pm
Steve Jones - Editor (4/5/2010)
Why are you doing this? Is it for reporting or are you considering storing the data in this format?
Heh... what the hey... Microsoft saw fit to...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2010 at 5:31 pm
CirquedeSQLeil (4/5/2010)
I have started a new thread on this topic.http://www.sqlservercentral.com/Forums/Topic897076-10-1.aspx
Nah.... I'd rather see this discussion continue here instead of essentially double posting. Sorry Jason.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2010 at 4:34 pm
I'd rather see the discussion continue on the thread which started it all rather than essentially double posting. Sorry Jason.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2010 at 4:32 pm
Heh... everyone forgot how to eliminate all contention for the table immediately... rename the table. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2010 at 4:31 pm
if 234 is 02:34 then why on Earth would 1 be anything but 00:01???? :blink:
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2010 at 4:28 pm
kkapferer (4/5/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2010 at 4:25 pm
Do what every screen saver company has been trying to do since computers first came out... turn them into an aquarium! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2010 at 4:19 pm
Paul White NZ (4/5/2010)
Technically, neither of these functions are guaranteed to never produce a duplicate
Actually, they are. From Books Online:
If an application must generate an identifier column that...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2010 at 4:04 pm
konstantinos.christodoulakis (4/5/2010)
More info:Table name: MSP_RESOURCES
EmployeeID: RES_UID (PK, UID(uniqueidentifier)
EmployeeName: RES_NAME (NAME(nvarchar(255)),not null)
EmployeeApprover: RES_TIMESHEET_MGR_UID (UID(uniqueidentifier),null)
Do I need to create a new table and select from there?
It would be much more handy if...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2010 at 3:43 pm
konstantinos.christodoulakis (4/5/2010)
It's really a recursive query, but easier that you make it:
SELECT e1.RES_UID, e1.RES_NAME, e1.RES_TIMESHEET_MGR_UID, e2.RES_NAME AS TimesheetManagerName
FROM MSP_RESOURCES e1 LEFT JOIN MSP_RESOURCES e2 ON e1.RES_TIMESHEET_MGR_UID...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2010 at 3:41 pm
COldCoffee (4/5/2010)
SELECT
EH.EmpID AS EmpID,
EH1.EmpName AS EmpName ,
EH.EmpName...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2010 at 3:40 pm
Viewing 15 posts - 39,061 through 39,075 (of 59,098 total)