I've always used SQL to index the title of the post, the date, and the
author.=20

Tried using SQL before for the entire message, but found it slowed as the
archive filled and searching message body was abysmal. Probably some issue
with MS SQL Server, I'm sure the *nix version manages it perfectly. Anyway,
I moved the emails into text files and index them from the SQL database
which contains only the minimum.=20

The OS does a good job of archiving many separate files as long as you don'=
t
put to many in one directory (I don't); access is lightning fast, and the
content index on the old server was actually faster than the SQL text
search. That is to say, it moved from horribly slow to achingly slow. On th=
e
new server, searches seem to be quite zippy once the indexes are in
memory... the first search is slow, after that, it's quick.=20

--
James Newton
1-970-462-7764=20

-----Original Message-----
From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] On Behalf Of
Marechiare
Sent: Friday, September 10, 2010 19:49
To: Microcontroller discussion list - Public.
Subject: Re: [OT] piclist.com archive up but no updates or full text search

> I had not seen this one, but it doesn't appear to have the
> ability to write the fetched email out to a file.

It's easy, ask here and, I'm sure, a lot of people will be happy to
post the C# code on a specific issue.


> I'm sure the source code could be used, but I don't have
> the time.

If you plan on making the code open, I don't see any reason why not
keep the development open.

And why saving emails as text files? Why not MS SQL (Express) as you
surely did before?
--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.