The idea is to easily see relevant differences, and I suspect that for example SQL code backup is not the best way to do that.
Let me see if I understand your question -- you want to quickly see changes in your database over some period of time? So you really aren't interested in a back-up per se, but in a quick way to see which data in your database has changed, and how, over some period of time?
If what you really want to see is a change in your database, you could use triggers. A trigger lets you make something happen when an insert, update, or delete is done on a table. So, for example, if you want to keep track of changes to a table "my_table" in a database, you could create a second table, called "my_table_audit" (or something like that) and then create a trigger which copies the old (or new) data in the "my_table" table into "my_table_audit" each time "my_table" undergoes an insert, update, or delete. You probably want to add a column or two to the audit table to record the time the change was made, and so forth.
Just watch out if you do this that you clean out the audit table every so often so it doesn't fill up your database.
You can get trigger syntax and a better explanation of how they work than what I have above at http://dev.mysql.com/doc/refman/5.0/en/triggers.html
we have a software NAVICAT. you can use its LITE version which is free
connect to server, open related database, right click on it and select DUMP SQL option.
you may also have scheduled backup option on the standard version of navicat (need to purchase it, although trial is available to download)
maybe
0 ความคิดเห็น:
แสดงความคิดเห็น