26GB text file

[l a u r e n]

:wtf:

---

"penguins have no bill"
biz stuff   about me

[Radoslav Bielik]

:eek: Now that will be a loooooooooooooooooooong read :laugh: Rado

[Jorgen Sigvardsson]

vim :) -- Gnnnnmmmpppppppfffffhhh!

[lsauer]

well actually total commander internal lister (F3). The only possible solutions, as far as reading only goes. The advantage is that it takes virtually no resources and 0 loading time or that stuff it streames dynamically, so size is just limited by your HD and OS but not by this app.

[Brian Delahunty]

Ok.. notepad is out of the question. Regards, Brian Dela :-)

[Daniel Turini]

UNIX tools use longs for file positioning and don't support files > 4GB.

// Quantum sort algorithm implementation
while (!sorted)
;

[John M Drescher]

I really want to only look at the end. It is an error log and I can see that there are a few database errors. The thing is that the system is working as expected... John

[John M Drescher]

That was my reaction when I found out that the log file was eating up the entire system partition. I'm glad I did not put it on the data partition it would have another 100GB to go... John

[Atlantys]

:eek: The kindest thing you can do for a stupid person, and for the gene pool, is to let him expire of his own dumb choices. [Roger Wright on stupid people]

[Ted Ferenc]

edlin in a "DOS" box!

---

If I have seen further it is by standing on the shoulders of Giants. - Isaac Newton 1676

[Bijesh]

You'll probably be better off writing your own program to read the last few lines and write in in another file.. Visual Studio just gives up if the file is too big... --------------------------------------------------

[Daniel Turini]

Import it via DTS/BCP/SQL*Loader (each line is a record), create a full text search index, and run SQL queries to find the info you need. And next time, create more manageable log files :)

// Quantum sort algorithm implementation
while (!sorted)
;

[John M Drescher]

Daniel Turini wrote: And next time, create more manageable log files I'll be working on the fix for that ASAP... John

[Jorgen Sigvardsson]

How long do you think such an import would take? :rolleyes: :-D -- Gnnnnmmmpppppppfffffhhh!

[Jorgen Sigvardsson]

Depends on what UNIX. Most modern ones have been upgraded to use 64 bit positions. Of course, YMMV with SCO.. :) -- Gnnnnmmmpppppppfffffhhh!

[John M Drescher]

:omg: It took me forever (> 30 minutes) just to copy the file to a RAID 0 array... John

[Tim Ranker]

del How useful could it be anyways? :)

[Scott Lee]

Quick... Someone tell me approximately how man mallocs were used during the creation of such a file. :-D

[John M Drescher]

I just wanted to see what recent operation was causing the log to balloon out of control.. John

[Daniel Turini]

Jörgen Sigvardsson wrote: How long do you think such an import would take? I've done such imports on about an hour. Indexing will take another one. Querying will be instantaneous. Now, try two or three 26GB searches with a text editor. :-D Talking about large data, DBMS is still one of the best tools.

// Quantum sort algorithm implementation
while (!sorted)
;