TechTutorials - Free Computer Tutorials  

How to Resolve SQL Server Error 2515?  Popular

Added: 08/14/2009, Hits: 3,501, Rating: 5, Comments: 4, Votes: 2
Add To Favorites | Comment on this article
SQL Server allows you to use a LSN (Log Sequence Number) that can be used as a recovery point for database restoration before the point of failure. When you perform differential backup process for your database, it is dependent upon a bitmap page that holds a bit per extent. Thus, corresponding changes are required to be marked in this differential backup bitmap or else will generate errors in database pages. You might need to restore the damaged database from the latest backup present. But sometimes, you donít get complete restoration results from your backup as it is incomplete or invalid. In such situations, you should use advanced MDF Repair tools that use powerful scanning algorithms to repair damaged SQL Server database.

As an instance, you might receive the below error with your SQL Server database:

Server: Msg 2515, Level 16, State 1
Page P_ID, object ID O_ID, index ID I_ID has been modified but is not marked modified in the differential backup bitmap.


The above error is a result of database check that is performed only if the differential bitmap is free from errors. The error suggests that the page specified with P_ID has a Log Sequence Number and has got a higher value than differential base Logic Sequence Number in FCB (File Control Block) of file or differential reference Log Sequence Number in BackupManager (whichever is the more recent value). The error occurs when this change has not been marked in differential backup bitmap. Since repair process doesnít depend upon the number of pages included in the database, the P_ID refers to the first page of database.


To recover from such situations, you need to deploy these methods:

  • Check and fix your system for possible hardware issues through Windows, application and SQL Serve error logs.

  • Restore the damaged database from the latest backup available.

  • Run DBCC CHECKDB without using any repair clause to determine extent of corruption and repair clause. Next, again execute DBCC CHECKDB but with the suggested repair clause. But this might cause data loss.

  • For safe repair mdf file, use commercial tools to repair and restore damaged SQL databases. MDF Repair tools are built with powerful technology and provide you self-explanatory user interface and safe repair options.

  • Stellar Phoenix SQL Recovery is an advanced mdf repair utility to repair damaged databases created with SQL Server 2008, 2005 and 2000. It is a fully-competent tool that restores all database components including triggers, stored procedures, views, rules and more. It is compatible with Windows Vista, XP, 2003, 2000 and NT.

    Comments (4)

    Review By: elliswhite [06/06/2014]
    Review Text: Must visit here for perfect and abrupt solution:-

    Review By: Matthewrobbin [08/05/2016]
    Review Text: Recovers MDF file, NDF File components like triggers, tables, views, rules and stored procedure with ease as well as recovers the deleted tables of the SQL database.More details you can visit this site:

    Review By: johnparkfix [12/08/2016]
    Review Text: Restore entire SQL server database data, such as stored procedures, views, triggers, tables, indexes, rules and user defined functions from the damaged/inaccessible MS SQL database in an easy and hassle free environment. Get more information about this application from here:-

    Review By: xiuxiuchiu [06/01/2017]
    Review Text: There are several other software also available for SQL Recovery, I would also like to mention here one of them. By this effective application, you can instantly repair damaged MDF file with in few clicks. You can get more details along with a free trial from here :-

    Items Per Page:

    Related Items

    7 Seconds Resources, Inc.

    IT Showcase