Viewing 15 posts - 43,636 through 43,650 (of 59,063 total)
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
Are the 200 million rows all CDR's?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 26, 2009 at 3:21 pm
Tim Daly (5/26/2009)
And thank for...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 26, 2009 at 1:56 pm
Chris...
I don't know if you saw the links... just in case...
http://www.sqlservercentral.com/articles/T-SQL/63681/
http://www.sqlservercentral.com/articles/cross+tab/65048/
I have to appologize for what they did to the code windows. They used to be almost full sized...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 26, 2009 at 1:50 pm
Damus (5/26/2009)
Lynn Pettis (5/26/2009)
Damus (5/25/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 26, 2009 at 1:40 pm
josephptran2002 (5/24/2009)
How are you doing? I am greatly appreciated your helps, I already solved the problem by using SSMS or Import/export wizard. You are very nice person, and may...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 24, 2009 at 5:22 pm
martin.edward (5/24/2009)
The parameters we were using were hardcoded. They need to be input by the user. I guess...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 24, 2009 at 5:10 pm
Allister Reid (5/24/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 24, 2009 at 4:59 pm
After seeing how fast the various renditions of the function run on a million rows, I'd say that it is NOT the function that is the problem. Adding such...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 24, 2009 at 4:43 pm
Viewing 15 posts - 43,636 through 43,650 (of 59,063 total)