A few random ideas from my own experience:
- Importing from raw data or other databases. Exporting to data warehouses.
- Cleaning legacy data (Especially unnormalized data. See some inspirational material at Database normalization the easier way. Also, columns with multiple values, such as name and address in one field).
- Using DBI with cron jobs. Security implications related to the cron user grants. How to test for a cron job with DBI (it works on the command line but fails at 2:00AM).
- On the same vein, using the DBI in CGI or mod_perl scripts can lead to problems related to user authorizations. Many people here in the Monastery ask why their script runs fine interactively and fails when Apache takes over. (see Protecting your DBI user/password in scripts?)
- I guess that data and schema movement also implies finding differences between databases and synchronizing them (see DBI -- Synchronize table diffs?).
- It might be OT, but you may find some ideas from the MySQL Cookbook table of contents.
Good luck for your enterprise!
_ _ _ _
(_|| | |(_|><
_|
-
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.
|
