Viewing 15 posts - 49,051 through 49,065 (of 59,093 total)
The "Unexpected end of file errors" may be something that you have to put up with if the data file has crud at the end of the file. That,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 28, 2008 at 5:48 pm
Thanks for the kudo, Grant. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
July 28, 2008 at 5:42 pm
Thanks again...
You keep saying that a "ROW" returned about 1MB of data... what is a "ROW" in this case?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 27, 2008 at 9:27 am
Good example of an Insert... that's not inserting into a scalar variable, though.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 27, 2008 at 8:56 am
I was looking for Avinish to provide the code example since he also made the suggestion with no code. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
July 27, 2008 at 8:52 am
Interesting, indeed. I'm curious... what do you mean by "1mb per row"? Do you mean that you calculated that you have to "touch" 1MB to process each CDR?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2008 at 7:58 pm
I'm probably a bit predjudiced, but I like the following article a lot better... 😛
http://www.sqlservercentral.com/articles/T-SQL/63003/
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2008 at 1:31 pm
Thanks for the feedback...
Are these records "CDRs"? Does the billing process have anything to do with telephony, DSL, or VoIP?
And, when you say it returns 1 to 7...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2008 at 1:02 pm
Seems to be the max memory thing was what most of the problems I read about were... it's a good idea to set that even on a 32 bit machine,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2008 at 10:57 am
You already have a true whole number function and it works well. The only problem is with how you tested it... you've passed a numeric value to the function...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2008 at 8:52 am
SQL Noob (7/25/2008)
if it wasn't for 64 bit SQL we would have to go to 64bit Oracle because the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2008 at 8:05 am
Try this, Michael... It's not done yet, but it'll do what you want without hitting up xp_CmdShell....
CREATE PROCEDURE dbo.GetDirDetails
/**************************************************************************************************
Purpose:
Replacement code for the sp_GetFileDetails proc that was available in...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2008 at 8:46 pm
GSquared (7/25/2008)
Just tested it. Transactional replication from one instance to another. Updates, inserts, deletes, all transfer successfully (and immediately).
Truncate gets this error:
Msg 4711, Level 16, State...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2008 at 6:03 pm
Jonathan Kehayias (7/23/2008)
Perhaps in my attempt to demonstrate an overly simplistic TSQL Example, I made it far to simple. The OP wants to SELECT a value from any column...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2008 at 5:52 pm
Heh... with all the problems I've seen on forums with 64 bit technology and SQL Server, so far... I'm going to wait for SQL Server 2011 before I recommend 64...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2008 at 5:47 pm
Viewing 15 posts - 49,051 through 49,065 (of 59,093 total)