SQL Errors - General Discussions - General Discussions - Progress Community
 General Discussions

SQL Errors

  • SQL Errors
  • Hi,

    We have upgraded recently a client's website to Sitefinity 7.0 and it is working fine. But our client performed SQL check (DBCC CHECKDB(N'DB')  WITH NO_INFOMSGS). When this runs it returns a list of errors with the following summary:

    CHECKDB found 0 allocation errors and 58 consistency errors in table 'sf_version_chnges' (object ID 962102468).

    CHECKDB found 0 allocation errors and 62 consistency errors in database 'Name'.

    repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Name). 

    Is there a way to fix these errors?


  • Sitefinity team, can you please give any advices?


  • Hello,

    In case you do not have a backup, you can run "repair_allow_data_loss" (but create a backup before doing so).

    Anyway considering the fact that the errors are found in 'sf_version_chnges', it does not seems to be a critical issue, so another option is to leave it as it is and you should not notice the presence of this errors while using the product.

    Hope this information helps.

    Vassil Vassilev
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Sitefinity CMS Ideas&Feedback Portal and vote to affect the priority of the items
  • If you have a valid backup then restore the database otherwise try below steps:

    Run a backup and restore this backup as a new (test) database; then run a DBCC CheckDB with one of the "Repair" options: repair_fast, repair_rebuilt, repair_allow_data_loss on this new test database to see if it could be fixed by SQL Server.

    Use database_name (Test database name)




    DBCC CHECKDB('database_name', repair options)


    to return to multi-user mode:

    ALTER <database-name> SET MULTI_USER

    After that run DBCC checkdb again to check if error is fixed

    If this test was successful you could perform the same on your productive database, of course during an "offline" time while no one uses the database.

    If it fails to fix the problem then you would try SQL recovery software from here:




  •  You can find more information here:


    Good luck)

  • SQL Server corruption and crashes can be very unproductive. And whats worse is to recover data from the SQL Server. SQL Database Recovery Tool lets you recover data from damaged or corrupt SQL Server and would save the recovered data in their original format and maintain perfect hierarchy.

    This tool is capable of recovering all data from corrupt SQL Servers, however severe the corruption may be.