Hi all. I’m running a Movable Type blog and I do have a current MySQL database. My question is, did most of you running blog software use the same database that your blog software is using for Mint as well? I’ve read that some people have experienced website performance issues based upon certain peppers being installed. I’m actually running Mint on another database that I created specifically for Mint. Is it a good idea to do this? Has anyone else done this? Thanks everyone for the support. Great community here.
Did you make another MySQL database for Mint?
IMHO, it’s always better to have a separate DB for separate apps. Mint is its own app. So is MT. They have separate, distinct functions, therefore, should have separate, distinct DBs. Performance is an issue, certainly, because Mint writes data to the DB constantly and that DB size grows very quickly.
There’s also a data-integrity issue here too. You never know if and when one or the other app (or a poorly written plugin/addon to said app) will flake out and corrupt your DB in some way. You don’t want one app wiping out all of your data.
Thanks very much for the response. I eventually created another database for Mint. I’m glad I did.
I’m running both – my blog (serendipity) and mint – from the same database, and I don’t see why I shouldn’t.
Since MySQL stores every table in three separate files (layout, data, indizes) there will definitely no performance increase when using different databases. Different servers may help, but unless you’re hosting a high traffic site which counts its unique visitors in packs of 10k you won’t be needing this.
Next thing is that MySQL supports rights per table – so just create a user for mint who has access to mint’s tables only, and one for your web application that has access to the website’s tables only. Neither of them will be able to “wipe out” the other.
I’ve done (and still do) it both ways. Never had a problem with either set-up.
You must be logged in to reply. Login above or create an account