Hello!
Johan De Meersman wrote:
>> From: "Vikram A"
>
>> Thank you for info. Now we enabled the logs. The DB administrator
>> itself made a mistake that he restored the back up
>
> This may be obvious, but keep your logs on separate disks if you can - full
> query logs take quite a bit of I/O
Sir,
Ok sir, thank you for your advise. We shall keep the logs in another
Disk/Drive.
From: Johan De Meersman
To: Vikram A
Cc: MY SQL Mailing list
Sent: Fri, 11 March, 2011 2:43:33 PM
Subject: Re: Table Records Deleted by anonymous user!
From: "V
> From: "Vikram A"
> Thank you for info. Now we enabled the logs. The DB administrator
> itself made a mistake that he restored the back up
This may be obvious, but keep your logs on separate disks if you can - full
query logs take quite a bit of I/O away, so if you have them on the same disks
say that it is done intentionally but could not point anyone because
we did not enable the logging feature in MySQL.
You already said it yourself: you don't have logging enabled, so that data
is not available.
If you have binary logs, you could comb through those for the delete
statements; t
- Original Message -
> From: "Vikram A"
>
> say that it is done intentionally but could not point anyone because
> we did not enable the logging feature in MySQL.
You already said it yourself: you don't have logging enabled, so that data is
not available.
If you have binary logs, you
Dear Experts!
Our institution has a centralized MySQL server which is accessed by several
clients. Today we found that a particular table's records are missing. We could
say that it is done intentionally but could not point anyone because we did not
enable the logging feature in MySQL. I w
