When, creating new Databases, does ISINTEG need to be run? If not, can someone explain why ISINTEG reports errors/runs fixes on newly created (empty) databases? Is it because it's empty? isinteg -s server01 -fix -test alltests isinteg -s server01 -fix -test rowcounts

I would guess since there is nothing in it. You don't need to run ISINTEG when creating a new database.Mark Morowczynski|MCT| MCSE 2003:Messaging, Security|MCITP:EMA 2K7,EDA Win 7,ES,SA,EA|MCTS:Windows Mobile Admin|Security+|http://almostdailytech.com

Not sure I understand are you getting these errors from the application logs when a new database is created?Chris cbfive.com

No errors in the application log, just curious why ISINTEG reports issues with a new DB. I actually found a KB article that explains it and says it's fixed in SP2. http://support.microsoft.com/kb/941775 This issue occurs because several columns in a newly created database do not have any values. However, the Isinteg command expects these missing initialized values.