Thursday, July 30, 2009

Resolving SQL Server Error 2511

SQL Server stores database in b-tree presentation. It is the general method of locating and placing data in a database, purposed for minimizing seek and access time for a particular record. If you have stored the table by using clustered index to sort it, its location can be comprised of components like page number, file number and slot number for the row. But sometimes, SQL Server reports keys being out of order for a particular page in a table. Such errors generally indicate table corruption, which are required to be restored from backup. On the other hand, the unavailability or invalid state of backup requires you to use commercial SQL recovery applications.

As an example, you might experience the below error message with your SQL Server database:

Server: Msg 2511, Level 16, State 2
Table Corrupt: Object ID %d, Index ID %d. Keys out of order on page %S_PGID, slots %d and %d.
Table error: Object ID %d, Index ID %d. Keys out of order on page %S_PGID, slots %d and %d.

Cause

As the error message suggests, it occurs when two specified slots are in incorrect order and are not in accordance to comparison of their keys. Here, P_ID represents the index page and data page.

Solution

You should consider these steps in order to correct the above issue:

You first need to ensure if system is free from hardware errors. For this, you should run hardware diagnostics and correct the problem, if exists any. You can also check Windows, application and SQL Server error log to determine the exact cause.
Restore the damaged database from your most recent backup, if exists and has valid state.
In case of backup concerns, you should run DBCC CHECKDB command without using any repair clause, which will determine the repair clause that should be applied. Next, run DBCC CHECKDB command with the suggested repair clause.
The above step can cause data loss and hence, for safe database repair, you should use third-party SQL Repair tools. These are graphically rich SQL Recovery software designed to achieve complete SQL database repair results.

Stellar Phoenix SQL Recovery is the most powerful tool that repairs and restores damaged SQL databases. It supports SQL Server 2008, 2005 and 2000. It can recover all database objects like tables, views, stored procedures, user defined functions etc. Phoenix SQL Recovery is a read-only tool that is compatible with Windows Vista, 2003, XP, and NT.

Monday, July 27, 2009

How to Resolve SQL Server Error 8961?

The rows of a SQL Server table are divided into partitions that are numbered from 1 to n. By default all rows are consisted in a single partition, however one can also define the size of partition. All rows of partition are stored as a B-tree or heap structure. The actual data is stored in leaf nodes of leaves (called text data node), while rest other nodes (called text index nodes) are used to store index values for leaf node. But sometimes, you observe table inconsistencies because of mismatch between one or more child nodes and their corresponding parent nodes. As a result, you receive table corruption errors. Such situations need to be resolved using DBCC CHECKDB command, backup or commercial SQL recovery utilities.

You might encounter the following error with your SQL Server database table:

Server: Msg 8961 , Level 23, State
Table error: Object ID O_ID. The text, ntext, or image node at page P_ID1, slot S_ID1, text ID TEXT_ID does not match its reference from page P_ID2, slot S_ID2.

Where, ‘state_number’ might be 1, 2 or 4.

Cause

SQL Server displays error 8961 when it finds mismatch between child node and parent node and corruption in a text object. Specifically, you might infer the exact cause of error message by the ‘state_number’ it is displaying:

State 1: It occurs when timestamps in node and parent don’t match with each other.

State 2: The child node is text data node and has greater size as what is supposed by its parent. It might also occur if the child node is text index node and has different size as what is supposed by its parent.

State 4: The child node is actually a text index node, but its parent supposes it to be a text data node or vice-versa. This might also occur due if the level of child node is different from what is supposed by its parent.

Solution

In order to solve such problems, you should follow these steps:

• Check your system for possible hardware problems
• Restore database from clean backup, if available
• Execute DBCC CHECKDB command without using repair clause if no valid backup is available. Again run DBCC CHECKDB but with the repair clause suggested by the previous check
• Running DBCC CHECKDB causes data loss. Thus, for safe SQL Repair, use third-party database repair applications. These SQL Recovery tools are built with powerful technology to safely scan and repair a damaged SQL Server database.

Stellar Phoenix SQL Recovery is a premier tool to repair damaged SQL databases. It supports SQL Server 2008, 2005 and 2000. With self-descriptive and exceptionally realistic interface, advanced repair options and read-only design, it is an effective SQL Repair tool to repair all database objects. The software is compatible with Windows Vista, XP, 2003, 2000 and NT.

Wednesday, July 22, 2009

Resolving 8905 Error Message in SQL

DBCC (Database Console Commands) commands are vital for T-SQL (Transact-SQL) as they check logical and physical integrity of all objects under a selected database. The DBCC CHECKDB statement enables the user to catch and repair all the possible errors that can occur while accessing a SQL database. A DBCC CHECKDB command uses three parameters (repair_allow_data_loss, repair fast and repair rebuild) to perform absolute repair of the SQL database. However, there are certain issues that the DBCC CHECKDB command can not resolve. These issues make the data saved in the SQL database inaccessible. To access the SQL database and perform complete repair and restoration, if the database user has not created any back up, an efficient SQL Repair tool is required.

While shrinking the SQL database using DBCC SHRINKDATABASE command, the database user may encounter the following error message:

“Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:192) in database ID 10 is marked allocated in the GAM, but no SGAM or IAM has allocated it.”

After the above error message appears, the extent in the SQL database becomes inaccessible. An extent in SQL database is the basic unit in which space is allocated to tables and indexes. These types of error messages are normally accompanied with one or more occurrences of error 8909. Furthermore, these errors are mainly caused in multi processor environments. The main cause of the above error message is that database user is using the shrink database and reindexing operation simultaneously. To prevent the SQL database from the above issue, the database user needs to reschedule the operations to execute at different times and turn off the Auto shrink option for that particular database.

To resolve the above issue and access the SQL database, the user needs to execute DBCC CHECKDB command with repair_allow_data_loss option. This command performs complete repair and also includes allocation and de-allocation of pages for rectifying allocation errors and deletion of corrupted text. However, this repair utility can also result in loss of data. In such scenarios, the user needs to recover the lost data by using effective SQL database recovery application. Such SQL Recovery software ensure complete repair and recovery of lost SQL database components by employing advanced and powerful scanning algorithms.

Stellar Phoenix SQL recovery is an excellent SQL Recovery application that performs complete and orderly recovery of SQL objects. It provides interactive and intuitive graphical user interface. It is compatible with MS SQL Server 2005 and MS SQL Server 2000. It also recovers and restores the back up files of MS SQL Server.

Sunday, July 19, 2009

Error 945 while opening the SQL Server Database

At times when the user attempts to open the SQL Server database, he comes across an error message. This error message does not allow the user to open the database. Various factors responsible for the occurrence of this error message are less hard drive space, no permissions granted to the user, virus infection etc. In such situations, if the user has not created any back up of the inaccessible SQL database, then he needs to use effective SQL Database Recovery software.

As a practical example, when a user attempts to open a SQL Server database, he encounters the below error message:
“SQL SERVER - FIX : Error 945 Database cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server error log for details”
This is one of the most common error messages that the user receives while opening a SQL database. After receiving the above error message, SQL database can not be mounted. The various factors that can result in the occurrence of the above error message are less hard drive space, Autogrow feature, .mdf or .ldf files are marked as read only or the user is not granted permission to open that SQL database. To solve the above problem and to access the SQL database, the user needs to follow the following steps:
1) The user needs to add more hard drive space either by removal of unnecessary files from hard drive or by adding another hard drive with larger size.

2) The user needs to disable the Autogrow feature of the SQL database.

3) The user needs to check if the account from which he is trying to access the database has enough permission to open the database.

4) The user needs to make sure that .mdf and .ldf files are not marked as read only on operating system’s file system level.

If the above error message appears even after following the above steps, then the user needs to recover and restore the inaccessible SQL database. To do so, the user needs to use powerful SQL Database Recovery application. Such SQL recovery utilities incorporate influential scanning methods to recover and restore the inaccessible and lost SQL database.

Stellar Phoenix SQL repair is a read only SQL Database Recovery application that ensures systematic and absolute SQL Recovery. It is designed with highly graphical user interface and supports MS SQL Server 2005 and MS SQL Server 2000. This SQL Repair utility can Repair SQL objects like, tables, views, stored procedures, rules, defaults, user defined data types and triggers. This SQL Repair application recovers and restores the backup files of MS SQL Server.

Friday, July 17, 2009

Fixing Error 8909 in SQL Database

The DBCC DBREINDEX is a Transactional-SQL command that rebuilds one or more indexes for a table in the SQL database. The DBCC SHRINKDATABASE is a T-SQL command which shrinks the size of the data and log files in the specified database. If these commands are executed concurrently on a particular table, the table is corrupted. In such situations, if the user has not created any back up, he can recover the table by using effective SQL Recovery software.


For example, when a user executes DBCC DBREINDEX concurrently with DBCC SHRINKDATABASE on a table, he encounters the below error message:


“Error: 8909


Table Corrupt: Object ID 0, index ID 0, page ID (1:623). Page Id in the page header = (0:0).”

The above error message halts the shrink operation and makes the table corrupt. The main cause of the above error message is that the user executes the shrink database and re-indexing operations at the same time. This error message mainly appears in multiprocessor environments. To prevent your SQL components from the above problem, the user needs to reschedule the operations to run at different times and turn off the Auto shrink option. To resolve the above error the user needs to execute DBCC CHECKDB command with repair_allow_data_loss option. This command reports the user that the error has been fixed although the error is not fixed. To resolve the error and access the table, the user needs to restore the table from the recent back up. But if the user has not maintained any back up, then he needs to use efficient SQL Recovery software.


Stellar Phoenix SQL recovery software, provided by Stellar Information Systems Limited ensures complete SQL Database Recovery. This application can Repair SQL components like tables, queries, views, triggers and stored procedures by incorporating influential scanning methods. It is read only application that provides safe and non-destructive sql database recovery. This SQL Repair application provides highly interactive and intuitive user interface that makes it easy to understand and implement.


This SQL Repair application can also recover and restore the backup files of MS SQL Server. It supports MS SQL Server 2005 and MS SQL Server 2000. It supports Windows Vista, XP, 2003 and 2000.The demo version of this SQL Repair utility is available on Stellar’ s website and popular shareware websites, which allows the user to preview the lost SQL database components, which the user can recover.

Error 8936 in SQL Server

SQL Server supports b-tree indexes to give fast query results. The pages of B-tree indexes are referred as index nodes, with the top node called as root node. However, the middle nodes are termed as branch nodes and bottom level nodes are denoted as leaf nodes. If table indexes get corrupted, SQL Server reports errors and you fail to access your database. To cope up such situations, you need to use your most recent database backup and restore the lost information. At times, backup fails to restore and thus, it becomes necessary that you use SQL Repair applications.

You might receive the below error message with your SQL Server database:

Server: Msg 8936, Level 16, State 1, Line 1
Table error: Object ID O_ID, index ID I_ID. B-tree chain linkage mismatch. P_ID1->next = P_ID2, but P_ID2->Prev = P_ID3.

Cause

This error occurs when SQL Server detects a break in logical page chain at any level of B-tree. It can happen at any level including root and leaf levels. The error message conveys that the next page pointer of page of P_ID1 points page P_ID2,which is different from page P_ID3, pointed by but page P_ID2's previous page pointer.

Solution

To solve the present issue, you should consider these methods:

• You should run hardware diagnostics as the above problem could occur due to hardware issues. Isolate the hardware issues, if any.
• If the problem persists, restore the database from a clean backup
• In case of unavailability of clean backup, you should run DBCC CHECKDB command to detect the amount of corruption and observe the suggested repair clause. You can then run DBCC CHECKDB command with the suggested repair clause
• If database still remains in corrupted state, you should use commercial SQL recovery tools.

SQL Repair software are advanced tools that can efficiently repair and restore damaged SQL Server databases. Such applications are equipped with graphically rich user interface, to-the-point documentation and read-only design. You can use these tools in any case of SQL database corruption.

Stellar Phoenix SQL Recovery is a complete repair tool for damaged SQL Server databases. It supports safe database repair for SQL Server 2008, 2005 and 2000. This SQL Recovery software is available with self-descriptive interface and restores all database objects (tables, user defined data types and functions, triggers, stored procedures, views, rules etc.). The software is compatible with Windows Vista, XP, 2003, 2000, and NT.