Viewing 15 posts - 46,906 through 46,920 (of 59,095 total)
Chris Morris (11/30/2008)
Jeff Moden (11/29/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 7:39 am
Grant Fritchey (11/30/2008)
The broke chain wipped around and touch my face & shirt.
Wow... last guy I heard of that happening to had to have major reconstructive surgery... you're a lucky...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 7:36 am
Jonathan Kehayias (11/29/2008)
Jeff Moden (11/29/2008)
Jonathan Kehayias (11/29/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2008 at 7:31 am
What's really amazing to me is that this thread has taken over 5,000 hits. D'ya s'pose anyone is actually learning anything for this? We can only hope.
Good chattin'...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 7:32 pm
brijbmishra (11/28/2008)
Can we develop a CLR based Stored Procedure without using Visual Studio?
What do you intend the CLR to do?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 7:17 pm
Heh... not trying to be a smart guy here... FEDEX overnight. Works great.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 7:00 pm
Lynn Pettis (11/29/2008)
Sometimes even those of us with lots of points to left need help. Heck, I think I even have seen Jeff post a question or two here.
Yep......
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 6:54 pm
Either that, or a partitioned view.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 6:11 pm
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
Viewing 15 posts - 46,906 through 46,920 (of 59,095 total)