Viewing 15 posts - 43,981 through 43,995 (of 59,101 total)
RBarryYoung (4/30/2009)
Chris Morris (4/30/2009)
@Barry - get well soon mate, that sounds like some horrible stuff you're dealing with. You will be hugely missed while you're away for the op.
Thanks, Chris....
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2009 at 10:44 am
DKG (4/30/2009)
Of couse this is not a good practive to take backup on DVDs
I'd say the jury is still out on that one for smaller systems. With compression, you...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2009 at 10:29 am
Well stated... but doesn't that show that embracing OOP took even longer for most folks? 😉 I believe that was the real point trying to be made. :hehe:
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2009 at 10:26 am
Florian Reischl (4/30/2009)
Jeff Moden (4/29/2009)
http://www.sqlservercentral.com/articles/T-SQL/63003/Thanks Jeff!
Great article! Am I allowed to refer to?
Greets
Flo
Absolutely.
I also have some code for you on cleaning a string. I've repaired the performance problem...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2009 at 10:22 am
DECLARE @counter int
SET @counter = 0
UPDATE custom.table1
SET @counter = table1.number = @counter+1
Also, since you got that to execute previously, you may have to add an "anchor" column and it should...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2009 at 10:18 am
m.berggren (4/30/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2009 at 10:16 am
greatheep (4/29/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2009 at 11:59 pm
The problem is that CheckSum_Agg just does a simple XOR. You can cheat... it's no guarantee, but it's more likely to find something different...
DECLARE @CS1 bigint
SET @CS1 =...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2009 at 11:41 pm
It would be a whole lot easier if you could use xp_CmdShell and BCP in a T-SQL loop. Are you allowed to use xp_CmdShell?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2009 at 10:55 pm
Just curious... what will this CLR Stored Procedure do?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2009 at 10:26 pm
Heh... oh my... someone is as crazy as I. Ya gotta be to know songs like that. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2009 at 10:20 pm
I ran into a server that had that many jobs, once. I disabled them all (except for know server maintenace) and would only turn them back on if someone...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2009 at 9:07 pm
Bob Griffin (4/29/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2009 at 8:58 pm
john.arnott (4/29/2009)
Now, if we're lucky, someone can help us figure out a single pass solution.
Use two counters and a case statement in the SET.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2009 at 8:56 pm
m.berggren (4/29/2009)
DECLARE @counter int
SET @counter = 1
UPDATE custom.table1
SET @counter = table1.number = @counter+1
The problem with that is that you've included the table schema in the set clause. It should...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2009 at 8:54 pm
Viewing 15 posts - 43,981 through 43,995 (of 59,101 total)