![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
I wish there was a nearby shrine to MySQL I could go visit. I'd like to go there and burn some incense or something.
In the middle of some pretty hairy DB work in order to make the revenue reports work, and I swear to you, all my guesses as to syntax for bizarro table relations that looked like they might work actually did work.
If this were Oracle, this would have taken me a week to figure out.
In the middle of some pretty hairy DB work in order to make the revenue reports work, and I swear to you, all my guesses as to syntax for bizarro table relations that looked like they might work actually did work.
If this were Oracle, this would have taken me a week to figure out.
Now is the time to automate mysqldump
Date: 2006-09-18 12:28 pm (UTC)Now is the time to think about consistently backing up your database. The good news is this is pretty easy. Here's a redacted version of what I use in a number of places:
This would be a welcomed addition to a crontab. You may want to adjust the prune period.
Rock, rock on.
Re: Now is the time to automate mysqldump
Date: 2006-09-18 03:02 pm (UTC)Re: Now is the time to automate mysqldump
Date: 2006-09-18 04:49 pm (UTC)Otherwise, you'll either need to copy the binary *ISM and index tables, which can be problematic when dealing with different architectures.
Having the SQL is really helpful, since you can always edit those commands to rebuild tables selectively.
Anyway, good luck.
Re: Now is the time to automate mysqldump
Date: 2006-09-18 10:30 pm (UTC)My trick, which I haven't done with Volity yet, is to keep snapshots of the last 15 days of important databases, stored using MyISAM compressed tables. Doesn't take up too much space and gives live access to older data.
no subject
Date: 2006-09-18 04:00 pm (UTC)I do a lot of Microsoft SQL Server stuff on a daily basis, including supporting a variety of financial stuff, so I'm happy to try to help if you get stuck.