The LMS stores text data internally in column-segregated compressed form. It does not internally store BLOBs, however, it is conceivable to store references to file locations where BLOBs are stored and create user-defined functions to use or access BLOBs in various ways from within LMS loads and queries. What kind of BLOBs are you interested in storing? How does this data need to be accessed in the context of log analysis? I'm very interested in these use cases and can possibly be more specific in my answer. Christina Noren director, systems consulting Addamark Technologies Inc. cfrlnat_private www.addamark.com 415-613-5441 cell > > The Addamark Log Management System turns the filesystem itself into a > > database. It stores log data as compressed files segregated in a b-tree > > index on time, with an SQL front end for querying. Because we parse the logs > > for each time segment into columns with more data redundancy than full rows > > we actually use less disk than gzipping flat files. Our engine runs on > > How about storing also BLOBs, not just flat text? Is LMS able to handle > it gracefully? > > -- > Florin Andrei > > It's ok to use the names of your pets or children as passwords > as long as they contain several non-alphanumeric characters. > > _______________________________________________ > LogAnalysis mailing list > LogAnalysisat_private > http://lists.shmoo.com/mailman/listinfo/loganalysis > _______________________________________________ LogAnalysis mailing list LogAnalysisat_private http://lists.shmoo.com/mailman/listinfo/loganalysis
This archive was generated by hypermail 2b30 : Mon Dec 02 2002 - 18:17:28 PST