Viewing 15 posts - 55,681 through 55,695 (of 59,098 total)
Heh... I just noticed that the dates in the example data are in the "dmy" format which means the examples posted are not in the correct date order and the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2007 at 9:42 pm
Chaitra,
Any feed back on this? Was that the problem or something else?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2007 at 8:54 pm
Oh shoot... although the answer to the formula above may have originally been posted incorrectly, I think I finally get this process that you're looking for... Not sure what the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2007 at 8:38 pm
And, sorry, I'm still not getting it... (2(20)+2(20-15)) = 50... not 45... True?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2007 at 8:24 pm
You bet. Thank you for the feedback, Ram.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2007 at 8:13 pm
Shoot, Lynn... I knew that... you knew that... I just wanted to make sure Kung Lao knew that.
Whether anyone suggests changing the server...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2007 at 7:47 pm
??? He's already deleted the data by mistake... how is either method you suggest going to recover data that's already been deleted?
I agree...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2007 at 7:32 pm
The other thing about Carl's trigger, is that it will actually update more than 1 row in the DCParty table whereas the original trigger would only update one row in...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2007 at 6:25 pm
Nope... not a PATINDEX bug... and you don't need to mess with the server default settings (case sensitive servers are a huge pain!).
This will do it for you...
SELECT PATINDEX...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2007 at 5:27 pm
Sure... if the @Column_Name variable contains something less than 2 characters, then because of the "-2" modifier in it, BOOM!
Can't help much more than that 'cause I don't know what...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2007 at 4:44 pm
Back button has never worked for me ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2007 at 4:28 pm
Good workaround, but a bit slow and resource intensive if you have millions of rows...
Something like the following works very fast... yeah, it does use dynamic SQL but that's only...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2007 at 8:44 am
Why do you need a white paper on the fact that if two users use a function, they get their own answers? It's that way with any function in any...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2007 at 8:38 am
Also, almost forgot... you can shrink TempDB (by file) as with any other DB without bouncing the server (possibly as Sugesh suggested). It could cause a fairly long wait time, though......
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2007 at 8:33 am
If the batch size of BCP/BULK INSERT is relatively small (less than a million rows, say), then those are likely not the problem. Rumor has it that the extensive use of...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2007 at 8:30 am
Viewing 15 posts - 55,681 through 55,695 (of 59,098 total)