I work for a firm that does marketing for 90+ car dealerships around the US. A big part of what we do to prep for data mining is standardizing and importing data from assorted dealership systems, some archaic and some not (ADP, R&R, Advent, Arkona, Quorum, Scorekeeper, etc.), and this sometimes requires processing service files of up to 200-300 MB with hundreds of thousands of records. Theoretical maximum could be even larger. Input format might be CSV or more of a vertical text format (key value), depending on how we're acquiring the data, but it's always text and never fixed-length. We use custom Perl scripts / mySQL for the most part, and we recently upgraded to a pretty fast server with 4 GB RAM (Cari.net, their pricing and service is pretty good and we also had our previous server there). OS is of course some popular Unix variant that I forget.
EDIT: We also import sales, leases, and a variety of other stuff, but the service file is just the largest part of that. I imagine the databases in uncompressed form could run upwards of 500 MB to a GB each over time.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
