Viewing 15 posts - 46,921 through 46,935 (of 59,102 total)
Charles Kincaid (11/29/2008)
Best to store unknown dates as NULL anyway.
I agree... if you don't know a date, store it as a NULL and convert it in the GUI.
Some folks store...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 5:52 pm
Heh... not to worry... it's not as bad as that dummy that thought the sum of the differences between two points could be used to determine the closest point., 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 5:49 pm
Jonathan Kehayias (11/29/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 5:46 pm
rbarryyoung (11/29/2008)
GilaMonster (11/29/2008)
Hell, no! Plenty areas I don't know well (and that's ignoring BI).Have you seen me answer an xml question recently?
Heh, I just assumed that you were leaving something...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 5:41 pm
rbarryyoung (11/29/2008)
CREATE PROC spWhichTable
@ColumnName varchar(50)
AS
SELECT o.name as [Table]
, c.name as [Column]
FROM sys.tables o
JOIN sys.columns c ON o.object_id = c.object_id
WHERE c.name =...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 5:22 pm
Nope... no digging required. That's basically what I meant but a whole lot shorter. 😉 Your good explanation is, of course, the most accurate... I was just trying...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 4:58 pm
Sergiy (11/29/2008)
The biggest mistake of MS, as for me, is to make SQL Server interface and syntax look familiar to those who don't have a clue about database programming.
Here hear!...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 4:53 pm
I find it's an unnecessary form of "ring knocking"... especially if you only have 4 visits, 1 post, and have never answered a question on the forum... then, it's just...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 2:24 pm
So you're saying that a derived table takes no memory?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 2:19 pm
rbarryyoung (11/29/2008)
Jeff Moden (11/29/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 2:15 pm
Heh... milliseconds per calculation mean a lot if you have millions of shipments to make. And you say what's wrong with being 100% correct? Nothing... but you're 100%...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 11:53 am
The only thing that I can figure out is that the optimizer in 2k5 resolves the sub-query before using it... the one in 2k seems to be trying to resolve...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 10:38 am
Isn't that strange? It's the GROUP BY loosing it's mind and it doesn't happen in 2k5. Not sure what to do about it yet.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 9:20 am
Heh... well never mind... all of the sudden, I'm getting the same bug and I only have a single CPU...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 9:09 am
rbarryyoung (11/29/2008)
Huhn, the bug happens on my last remaining SQL 2000 server also. MAXDOP has no effect on it.
Is it a multi CPU box you're working on? Also,...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 9:06 am
Viewing 15 posts - 46,921 through 46,935 (of 59,102 total)