One of the most common things that people do during a migration from older versions of SharePoint into the 2010 version is using the PowerShell's Test-SPContentDatabase cmdlet to see how healthy the database is. When this test is performed, the cmdlet produces some results that will be very instrumental in figuring out what is going on with the database. In environments where we have a smaller number of content databases this is a very easy thing to do, but what does one do when there are several hundred databases with terabytes of content? I ended up in a situation like this and I decided to go & write a script using PowerShell that will come to my rescue.
