Viewing 15 posts - 43,666 through 43,680 (of 59,101 total)
You appear to be missing part of the query after the AND. What's the full query look like?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2009 at 4:03 pm
Different take on the same thing...
DECLARE @DateString VARCHAR(50)
SET @DateString = '2009-02-26T00:00:00.0000000-08:00'
SELECT CONVERT(DATETIME,LEFT(@DateString,23),126)
+ CAST(RIGHT(@DateString,5) AS DATETIME)
I couldn't remember if you...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2009 at 3:54 pm
ukumawat (5/29/2009)
hi all,is there any method to count number of spaces between two strings?
thanks in advance.
Andrew's method will work just fine, but I have to ask because this sounds like...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2009 at 3:33 pm
andrewd.smith (5/29/2009)
Lookup DATEDIFF TSQL function in SQL Server Books Online
Heh.... try it, Andrew. 😉 You may be surprised how difficult that recommendation actually is.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2009 at 3:29 pm
Do you have to use SSIS for this? Or, can you use xp_CmdShell?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2009 at 3:25 pm
I took a slightly different tact...
DECLARE @DateString VARCHAR(50)
SET @DateString = '20080916131411.000000-300'
SELECT CONVERT(DATETIME,LEFT(STUFF(STUFF(STUFF(@DateString,13,0,':'),11,0,':'),9,0,' '),21))
+ DATEADD(mm,CAST(SUBSTRING(@DateString,PATINDEX('%[-+]%',@DateString),50) AS INT),0)
Can't remember if you're...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2009 at 3:19 pm
Thanks for the awesome compliment, Ravi. I'll try.
BTW, I really like your signature line. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2009 at 7:41 am
Cool... although I don't believe you need to change the datatype on the IDENTITY column. You're only working on 10 million rows. INT goes up to 2 billion....
--Jeff Moden
Change is inevitable... Change for the better is not.
May 28, 2009 at 12:18 pm
That certainly complicates the cross tab section of the code... lemme see what I can phinger out...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 28, 2009 at 10:50 am
Ravi (5/24/2009)
i have used the same code for testing with 10 million records, as code itself is inserting records, so i have nothing to do with the data.
the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 27, 2009 at 2:30 pm
mmunson (5/27/2009)
Jeff, your script work perfect, and I was basically able to understand it. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 27, 2009 at 2:03 pm
Damus (5/27/2009)
Jeff Moden (5/27/2009)
Damus (5/27/2009)
Sending it to you with an explanation.Why don't you just attach it to this thread so the rest of us can take a peek, as well?
The...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 27, 2009 at 8:36 am
Damus (5/27/2009)
Sending it to you with an explanation.
Why don't you just attach it to this thread so the rest of us can take a peek, as well?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 27, 2009 at 8:00 am
Pieter (5/26/2009)
Sorry, I am not familiar with the term "CDR's"
"Call Detail Records" or "Call Data Records". Based on all the talk about phone numbers, I thought you were taking...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 26, 2009 at 8:03 pm
RBarryYoung (5/26/2009)
CDR = "Call Data Record"I used to work in that field too... 🙂
We used to call them "Call Detail Record". Either will do.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 26, 2009 at 8:00 pm
Viewing 15 posts - 43,666 through 43,680 (of 59,101 total)