Last night we made the backup as usual, in the morning a table is
completely all nulls except for the elements of the key.
We thought there was some error or accident, so we copy that table from
the backup, 30 min later we saw another table with the same problem,
then checking another DB used for testing also had the same problem, is
this an attack, virus ?
We don't know what to do, please someone advise.
SQL Server 2005 Standard 9.0.1399
Thanks
Andres Sanchez
Monterrey MexicoYou could run Profiler to try to track down if someone is submitting such UPDATE statement to your
database instance.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mancha" <andres.sanchez.rendon@.gmail.com> wrote in message
news:1159492282.552559.267590@.i3g2000cwc.googlegroups.com...
> Last night we made the backup as usual, in the morning a table is
> completely all nulls except for the elements of the key.
> We thought there was some error or accident, so we copy that table from
> the backup, 30 min later we saw another table with the same problem,
> then checking another DB used for testing also had the same problem, is
> this an attack, virus ?
> We don't know what to do, please someone advise.
> SQL Server 2005 Standard 9.0.1399
> Thanks
> Andres Sanchez
> Monterrey Mexico
>|||Hi
You don't say how may non-key columns there are, but you may want to review
why they are all nullable.
John
"Mancha" wrote:
> Last night we made the backup as usual, in the morning a table is
> completely all nulls except for the elements of the key.
> We thought there was some error or accident, so we copy that table from
> the backup, 30 min later we saw another table with the same problem,
> then checking another DB used for testing also had the same problem, is
> this an attack, virus ?
> We don't know what to do, please someone advise.
> SQL Server 2005 Standard 9.0.1399
> Thanks
> Andres Sanchez
> Monterrey Mexico
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment