Hello,
I'am seeking the answer on three hypothetical situation where I need to
recover a database (needed to write out a DRP)
1) suppose somebody updates a table with wrong values and that query is
committed. After a few hours the error is spotted. Is it possible to
recover that individual table without stopping the entire database? If
it is not possible while the database is online, how do I recover the
database without losing the latest transaction on other tables; because
if I set back a backup until the time just before the disaster, I lose
all information since then on the other tables
Maybe two cases must be seen
a) no one changed that table after the update
b) other transactions where done on that table since the update
2) same situation, but one or more tables where dropped.
3) a db user launches a monsterous heavy unoptimized query almost
bringing the databaseserver to its knees. how can I identify which query
is causing the problem and how do I kill it off? Is there a link between
OS processid and a running query?
Thanks in advance,
Filip Sergeys
--
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
* System Engineer, Verzekeringen NV *
* www.verzekeringen.be *
* Oostkaai 23 B-2170 Merksem *
* 03/6416673 - 0477/340942 *
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
