Viewing 15 posts - 49,396 through 49,410 (of 59,091 total)
rbarryyoung (7/7/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 6:46 am
Here's the thing, though.... Eric said...
emamet (7/4/2008)
I am trying to write a stored procedure that splits a [font="Arial Black"]file content [/font](sent as one VARCHAR(MAX) parameter) into as many rows...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 12:34 am
GilaMonster (7/7/2008)
Jeff Moden (7/6/2008)
I wonder how many questions they have on cursors now adays... If it's more than 5, I would flunk because I avoid them like the plague.
I don't...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 12:29 am
Sorry... I misinterpreted what you said... I thought you said there weren't that many changes. My mistake.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 12:22 am
That's what I was afraid of... the Recursive CTE is a quick way out for you. Sure, it works fine, but there has to be something better than constantly...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 12:03 am
If you are trying to split the lines into a table, why are you just returning the separators? Do you actually want separate rows in a table or???
If the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2008 at 11:31 pm
pallavikiran.deevi (6/10/2008)
Hi,Thank you very much for your reply.I used that code ,it works fine.I amso happy.
Regards,
Pallavi.
It would be better, in the long run,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2008 at 11:12 pm
MichaelC (6/5/2008)
I have been trying to debug a simple CLR function
Just curious... what does you "simple CLR function" do?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2008 at 11:08 pm
Marios Philippopoulos (5/30/2008)
I have a SQL CLR sproc that lists the contents of a folder.
Just curious... what columns are you returning fo this?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2008 at 11:06 pm
You still haven't answered the very important question of...
What have you written a CLR for that you think can't be done in T-SQL? Dude... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2008 at 11:03 pm
robert (7/2/2008)
SUM(CAST Duration AS datetime) wont work either...
Since that's basically the correct way to do it, tell me... what do you mean it won't work?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2008 at 10:07 pm
It's a whole lot easier than you think...
SELECT Date-1
FROM Calendar
WHERE Day(Date) = 1
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2008 at 10:00 pm
Oh, no... sorry if this sounds nasty but I wouldn't use any of those... especially (sorry to say) the "Celko" version...
Try this instead, please...
First, create a function like...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2008 at 9:16 pm
The bottom line is... if you expect the database to grow back to the same size in the next week or two, don't shrink it...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2008 at 8:59 pm
I've already proven that it will return more than one NEWID()... just not the way you did it because the view only returns one row. Go back and look...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2008 at 8:54 pm
Viewing 15 posts - 49,396 through 49,410 (of 59,091 total)