Check the data itself before doing the backup !!!

[sarah77]

Hi,

We can use DBCC CHECKDB and DBCC CHECKCATALOG If database or index is damaged before applying any backup.

But can anybody tells how do I check if the data itslef inside the tables is infected by virsues or it contains garbage ?. (such as comparing data with transactio log), How?

Any comment will be much appreciated.
Thanks

 

[Guest_imported]

A good practice to ensuring that the database backup is ok is to do regular restores on a test box which mirrors the production system. If the database is very lary and such a process would be very time consuming SQL server uses file groups to allow tables to be backed up rather than a whole database.

I run the DBCC comands along with the checkdb. Depending on your version of SQL server there are some additional dbcc comand for checking page tears etc in SQL 2000.

 

[sarah77]

I'm using SQL2000 server and you may misunderstand my question !.

What I want is how to check the data if its good or bad before I doing my backup ?!.

Bad data means the data itself is not good (such as infected by virus that change some columns to garbage, for example Salary was: 9100$ but its changed for some reason to %^~).

In my case indexes and databases are good but the data itself is bad so DBCC CHECKDB and DBCC CHECKCATALOG will not help us on this situation.

Does anybody have an idea !!

 

[sguslan]

Hi Sarah ..

I think you are confusing the issue !

Unless you are storing susceptible documents such as word/excel or an executable in a BLOB in SQL, I am not sure how your data will be infected ...Again, if you do store such documents, you'll have to extract each BLOB into an OS file and run a scanning software on it ...You may be able to automate the process using VB6 or a similar tool...

Good Luk


Salim