Viewing 15 posts - 48,541 through 48,555 (of 59,095 total)
sqluser (8/29/2008)
Hi,try the below one.
DECLARE @Text VARCHAR(16)
SET @Text = 'ABC222'
SELECT SUBSTRING(@Text,PATINDEX('%[0-9]%',@Text),LEN(@Text)) + 100
---
Doesn't return the "ABC" part... 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2008 at 3:54 pm
Here's the times on my box
P5 1.8 GHZ, twin 80GB IDE hard drives, 1GB Ram
208 Update
629 Cursor
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2008 at 3:23 pm
rbarryyoung (8/30/2008)
balbirsinghsodhi (8/29/2008)
String or binary data would be truncated.
but when I create...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2008 at 1:57 pm
raym (8/29/2008)
I've attached the the spreadsheet with the tables I want to bcp out
Your largest table contains 1.2 BILLION rows... the average output for BCP in the native format is...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2008 at 1:52 pm
I've gotta go with Gus on this one... even the seemingly unsurmountable task of doing a running total can be done at extremely high speeds, even in SQL Server 2000,...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2008 at 9:54 am
I gotto go with Jack on this one... use a Tally table instead of a While loop. In fact, here's an article on what a Tally table is and...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2008 at 9:48 am
Damned smiley faces... 🙂
Ok... here it is again without the smiley faces... it's not as "pretty", but it'll do...
/**********************************************************************************************************************
Purpose:
Returns a single result set similar to sp_Space used for...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2008 at 9:04 am
balbirsinghsodhi (8/29/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2008 at 8:56 am
You're parsing 200 million rows of data in 0.4 seconds or less? Gotta see that one... would you mind posting the code?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2008 at 1:36 pm
All of the methods used where a correlated sub-query uses the < or <= relationship is doomed to performance failure. If you want a very high speed (1 million...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2008 at 10:59 am
Heh... if you're already working 10 or 12 hour days, a 4 day work week would be very welcome! 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2008 at 10:50 am
Kajal (8/28/2008)
Can u brief me how to use it in such scenario..i know a litle bit settin lineage IDThanks
Anything I say would be a simple regurgitation of what's in Books...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2008 at 8:17 am
Even that's not true, Hugo... the security on sp_MakeWebTask changed without warning on sp4 of 2k.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2008 at 8:16 am
Again... very cool and thanks for taking the time.
You should write an article on this... good stuff. I'll be "playing" with all of this all next week. Thanks,...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2008 at 8:12 am
Hugo Kornelis (8/29/2008)
On second look - the string concatenation technique used to piece the bits back together is undocumented, and might cause unexpected results. Not good for production code.
Heh... even...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2008 at 6:03 am
Viewing 15 posts - 48,541 through 48,555 (of 59,095 total)