Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are preparing to migrate to a new SAN and I have been tasked with verifying/validating data after migrating a server.

Other than the DBCC commands that would tell me about data integrity, and comparing against a restored backup on a different server (on the old SAN), what would you recommend to do in order to V&V the migration?


ps - I will have instances that range from MSSQL 2000-2008

share|improve this question
up vote 2 down vote accepted

I'd compare the data using, say, Red Gate SQL Data Compare in addition to DBCC. Comparing all data in all tables row by row means checking every populated page.

However, for larger databases this will a long time, so you can run aggregates over columns (say AVG or CHECKSUM_AGG). I use this to quickly compare results but it would scale and force data to be read.

share|improve this answer

It really depends on how you are going to perform migration. If you are planning to stop SQL services and copy data and log files from old LUNs to new ones, then there is no change in logical database structure and therefor no need for comparing data at that level.

I would recommend using a good copying program that calculates checksums and verifies that all files have been copied correctly.

In a similar project I used FastCopy which is very fast and reliable tool.

On the top of that, I would run old good CHKDSK on the new LUNs, just to make sure that there is no errors on NTFS level.

Good luck with your migration


share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.