thoughts:
1. why even use a relational database for logging ? especially with 5M
rec/month/device/customer, how often is there a genuine SELECT with special
criteria for those records ?
2. im not a huge fan of table-per-record. relational schemas aren't designed
to work this way, the
1: The logs are selected quite often based on indexed columns, and this is
done via a web portal graphing tool. Maybe I shouldn't refer to them as
logs for clarity, but the data is specific snmp fields where a schema fits
well and the queries are fairly basic with some group by aggregation.
2.
Hiya,
In the top-right corner of http://www.sqlalchemy.org/ , there's a link to
the 0.7.8 documentation - except it's not :-(
The link points to http://www.sqlalchemy.org/docs/07/ , which redirects to
http://docs.sqlalchemy.org/en/latest/ , which is the doc site for 0.8.0
beta 1. I don't know
OK well it's MySQL, so sure if you want to make a table per customer, its not a
terrible drain on MySQLthe create tables on the fly thing makes DBAs very
upset but then again, MySQL DBs are usually not DBA controlled...
still, it seems like these tables aren't referred to by any other
whoops! good call. There's a series of .htaccess files I forgot to update,
fixed.
On Jun 30, 2012, at 2:37 PM, thomat...@gmail.com wrote:
Hiya,
In the top-right corner of http://www.sqlalchemy.org/ , there's a link to the
0.7.8 documentation - except it's not :-(
The link points to
hehe. That's a very good MySQL observation. :)
I was trying to avoid hadoop map reduce because my data doesn't grow more
than ~5 million / device (appliance) .. At 5 million, I am still able to
run my queries at a very reasonable time and most if not all the queries
need to be realtime and
On Jun 30, 2012, at 6:35 PM, espresso maker wrote:
hehe. That's a very good MySQL observation. :)
I was trying to avoid hadoop map reduce because my data doesn't grow more
than ~5 million / device (appliance) .. At 5 million, I am still able to run
my queries at a very reasonable time
