Wednesday, March 31, 2010

Tips To Resolve “offset 0xADDRESS is invalid” Error Message

A severity level 16 table error message occurs, while trying to open a MS SQL table, when the database table gets badly corrupted. Few causes of severe corruption of a SQL table are improper system/server shutdown, virus infection, metadata structure damage, and human mistakes. The database table records become inaccessible when a database user encounters error message with so much severity. An easy way to access table records post the above error message, is by restoring data from an updated backup. However, if the backup file is unobtainable or deficient, then a user can use DBCC CHECKDB command to repair the table. But, running this command might lead to loss of records saved in the table. To prevent any loss of records, a database user needs to repair his/her table using a third-party SQL Recovery application.

The above situation can be explained better by following severity level 16 error message:


“Table error: Object ID O_ID, index ID I_ID, page P_ID. Test (TEST) failed. Slot S_ID, offset 0xADDRESS is invalid.”

This error message flashes on your screen when you try to open a MS SQL Server table. After the error message pops up, the table can not be opened. The records saved in the table become inaccessible.

Cause:

The above error message appears when table is corrupt, either through logical crash or physical damage.

Resolution:

To get rid of the above severity level 16 error message, you need to identify the cause of corruption. To do so follow the below mentioned steps:

You should review the Server, system, and application logs. In case you find any entry related to a particular damaged hardware component, you should change that system component.

To analyze logical failure, you can run DBCC CHECKDB command without a repair clause. This helps you to identify the exact level of corruption. After doing so, run the same command with an applicable repair clause.

In case logical corruption persists, you should opt for a commercial SQL Database Recovery software. A SQL Repair application repairs logically damaged databases without harming the original database.

SQL Recovery repairs logically corrupt MS SQL Server 2008, 20005, and 2000 databases in a few mouse clicks. The advanced scanning methods used by the software ensure maximum repair of almost all database objects. The read only SQL Repair utility is designed for Windows 7, Vista, 2008, XP, 2003, and 2000.
Posted by at No comments:
Labels: , , ,

Friday, March 26, 2010

Insufficient Disk Space During Upgrade May Corrupt SQL Server Database

You may encounter SQL Server object or database corruption if you fail to provide enough disk space for the database growth while upgrading Microsoft SQL Server database. This situation may damage sysdepends table in model database and the process may stop responding. You do not receive any error message when this process fails and table corruption occurs. After corruption, the database may become inaccessible and you encounter data loss. In order to retrieve inaccessible data from MDF (Master Database File) database of SQL Server, you need to opt for MS SQL Recovery alternatives.

The sysdepends is a SQL Server database table, which provides dependency relationship information between persistent objects of database. The persistent objects can be providers (database objects depend upon them) and/or dependents (they depend upon other database objects).

Root of the problem

This problem occurs if data file is nearly full (only a few pages are free) and file growth on data file is adjusted to 0% (percent). In this case, the upgrade process doesn't have sufficient scape to finish the upgrade of database. In such circumstances, the database is left in partially upgraded and corrupt state. To Recover SQL database in these situations, you need to sort out this behavior.

Solution

To fix the above mentioned problem:

Replace 'model' database. Follow the below mentioned steps to replace it:
Restore a good copy of SQL Server model database to affected server. If you encounter any error regarding 'msdb' database, you can ignore it.
Copy in the model database from new MS SQL Server installation. After copying in a new model database, you may lose the changes that you have made to previous model database.
Restore a model database of the earlier version of SQL Server and increase the size of database. Add new database to SQL Server installation.
Re-run the SQL Server upgrade process.

The above method helps you to fix model database corruption, but can not repair the damaged SQL Server database. To retrieve data from MDF file, SQL Database Recovery is required.

Recovery is best possible with the help of advanced MS SQL Recovery software. These are third-party utilities, which thoroughly scan entire database to extract all inaccessible or damaged data from it.

SQL Recovery is a read-only and easy to use software for absolute recovery of damaged MDF database. The software works well with Microsoft SQL Server 2008, 2005, and 2000. It restores all database objects such as tables, reports, forms, constraints, stored procedures, and triggers.
Posted by at No comments:

Wednesday, March 24, 2010

Improper Configuration Settings in SQL Server May Cause Database Corruption


Are you unable to start Microsoft SQL Server? Is your MDF (Master Database File) of MS SQL Server is inaccessible? This behavior may occur due to inconsistency or corruption in Microsoft SQL Server database. If the SQL Server application can not be accessed, problem can be due to application crash, which may cause MDF corruption. This behavior of MS SQL Server database leads to critical data loss situations, and needs SQL Server Recovery to get your mission critical data back in working state.

In case of corruption of the SQL Server database or Microsoft SQL Server application itself, the database can not be mounted or accessed successfully. There are numerous reasons, which may lead to SQL Server and SQL Server database corruption, such as virus infection, improper system shutdown, operating system failure, application malfunction, missing or damaged system files, and more.

As a practical example of the above problem, you may come across the below error message when you try to start Microsoft SQL Server 2005:

"Could not start the SQL Server (SQL2005) service on Local Computer

Error 14001: This application has failed to start because the application configuration is incorrect.
Reinstalling the application may fix this problem.”

After occurrence of the above error message, SQL Server application can not be opened. In such situations, the MDF database becomes inaccessible and unmountable. In order to gain access of your valuable data in SQL Server database, you need to find out the cause of this behavior and perform SQL Server Recovery by sorting it out.

Cause

The major reason of this problem is problem in SQL Server configuration. The configuration is either corrupt or incorrect. The same problem may also occur if any of the critical system files of SQL Server is corrupt or missing.

Resolution

In order to sort out this behavior of Microsoft SQL Server and access MDF database, you need to reinstall SQL Server application. In case of database corruption, you need to Recover SQL Server database using third-party applications.

The SQL Database Recovery software are particularly designed to carry out in-depth scan of entire database and extract all the corrupt or inaccessible database objects. They come equipped with simple and rich graphical user interface to provide ease of use. With read-only nature, these tools preserve integrity of your database.

SQL Recovery software repairs and restores damaged MDF database in all possible corruption scenarios. The software works well with Microsoft SQL Server 2008, 2005, and 2000. It restores all database objects such as tables, reports, formats, triggers, stored procedures, and constraints.
Posted by at No comments:
Labels: , , , ,

Tuesday, March 23, 2010

SQL Server Database Corruption If You Run a Query with Parallel Execution Plan

You may come across Access Violation if you run an SQL query, which uses parallel execution plan in Microsoft SQL Server 2008. Access violation is an error condition, which may occur while performing general operations on the SQL database. It may occur due to application malfunction, software bug, or database corruption. It renders your database inaccessible and may cause data loss, if you don't have a complete backup to restore data from. To overcome such issues, SQL Database Recovery is required.

As an example of Access Violation in Microsoft SQL Server 2008, consider the below scenario:

In MS SQL Server 2008, you're running a query that includes all the below mentioned clauses:
Inner join
Union all
Group by
The database query is using parallel execution plan.
You execute the query.

In the above scenario, you may face access violation. And, you receive the following error message:

“Location: xbmp.cpp:2038
Expression: 0 != pxteBitmap
Msg 3624, Level 20, State 1, Line 2
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.”

Furthermore, the mini-dump file is returned under the log folder of MS SQL Server 2008.

Cause

As sated in the above error message, this problem may have occurred due to either database corruption or a software bug. After corruption, SQL Server can not read the database and this behavior occurs.

Resolution

Run DBCC CHECKDB utility to try fixing database corruption. If the database is severely corrupted, it may not work. In such cases, third-party SQL Server Recovery applications are worth using.

The MS SQL Recovery applications are particularly designed to thoroughly scan whole SQL Server database and extract all damaged and inaccessible objects from it. They allow you to perform SQL Recovery on your own as they have simple and rich graphical user interface.

SQL Recovery software safely and successfully repairs damaged SQL Server database in all cases of corruption. It works well with Microsoft SQL Server 2008, 2005, and 2000. The software restores all database objects such as tables, reports, forms, macros, and more.
Posted by at No comments:
Labels: , , ,

Saturday, March 20, 2010

SQL Database Corruption If You Shrink The Database When It Is Use

In MS SQL Server, you can shrink tempdb database to a size smaller than last configuration of the database. There are various methods that you can use to remove the unused pages of the database and reduce its size. You can also shrink the individual files in SQL Server database. In some methods, you must not do any operation on the database while shrinking. You should not shrink the database when it is in use. It may damage the database and cause serious data loss situations. If you mistakenly do it, SQL Database Recovery becomes essential.

In Microsoft SQL Server, you should use the SQL Server Management Studio in place of Enterprise Manager and Query Analyzer to carry out the tempdb shrink operations. SQL Server Management Studio doesn't show proper size of the tempdb files after shrink operation. The value of “Currently allocated space” is taken from the sys.master_files DMV and it isn't updated after you shrink the database. You can get the exact size of tempdb database using the below mentioned statement after shrinking the database:

“use tempdb

select (size*8) as FileSizeKB from sys.database_files”

What happens if you shrink the tempdb database using DBCC SHRINKFILE or DBCC SHRINKDATABASE commands while the database is in use:

If you try to shrink the database through DBCC SHRINKFILE or DBCC SHRINKDATABASE that is in use by another process, you may come across various database consistency errors, similar to the below errors:

“Server: Msg 2501, Level 16, State 1, Line 1 Could not find table named '1525580473'. Check sysobjects.”

Or

“Server: Msg 8909, Level 16, State 1, Line 0 Table Corrupt: Object ID 1, index ID 0, page ID %S_PGID. The PageId in the page header = %S_PGID.”

After the above error message, shrink operation fails.

Error 8909 indicates corruption in tempdb database. You may also encounter this problem if the SQL Server database is damaged. In order to sort out this problem and fix consistency errors, use Eseutil utility.

If the above method does not work, Repair SQL database using commercial applications. MS SQL Recovery software methodically scan the damaged database and restore all of its data.

The SQL Repair applications do not demand sound technical skills to restore the database due to simple and rich graphical user interface. They have read-only conduct and thus preserve integrity of your valuable data.

SQL Recovery software works in all cases of MS SQL Server database corruption scenarios. It is designed for Microsoft SQL Server 2008, 2005, and 2000. The software restores all MDF items such as tables, reports, forms, queries, triggers, constraints, and stored procedures.
Posted by at No comments:
Labels: , , ,

Thursday, March 18, 2010

Index Corruption May Damaged Microsoft SQL Server Database

Are you getting index corruption errors in SQL Server 2000 database while running DBCC CHECKDB statement? Index is a data structure in SQL Server database, which improves the performance of database operations. SQL Server uses indexes for accessing data from the MDF (Master Database File) database. In case of corruption, SQL Server may not locate and access the data or even the database itself may get damaged. It leads to critical data loss situations and needs SQL Database Recovery to be fixed.

In a practical scenario, you may come across the below error messages when you run DBCC CHECKDB statement on a MDF database that is upgraded to MS SQL Server 2000 from an earlier version:

Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table '' (ID ). Missing or invalid key in index '' (ID ) for the row:
Server: Msg 8955, Level 16, State 1, Line 1 Data row (1:133:42) identified by (RID = (1:133:42) ) has index values ( = 0).
Server: Msg 8952, Level 16, State 1,
Line 1 Table error: Database '', index '.' (ID ) (index ID ). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:137:0) with values ( = 0) points to the data row identified by (RID = (1:133:42)).

After the above errors, you cannot check the integrity and consistency of the database and it remains in inconsistent state. In order to gain access of your database in such cases, you need to find out the cause of this behavior and perform SQL Server Recovery by fixing it.

Root of the issue

In earlier versions of SQL Server, like SQL Server 7.0, if sysindexes.status value is set to 0 for nonclustered index in table, nonclustered index also enables insertion of the NULL values. When you run DBCC CHECKDB statement on database of SQL Server 7.0, you do not encounter such problem. After upgrading to SQL Server 2000, DBCC CHECKDB statement displays the above error messages because the NULL values isn't allowed when sysindexes.status value isn't 2097152.

This problem may also occur if the MDF file is damaged due to virus infection, improper system shutdown, or other similar reasons.

To sort out such issues, MS SQL Recovery is essential. It is possible through powerful and advanced third party SQL Recovery software. They enable safe, easy, and quick recovery of your valuable data.

SQL Recovery restores all MDF file objects such as tables, reports, forms, triggers, stored procedures, and constraints. The software works well with MS SQL Server 2008, 2005, and 2000.
Posted by at No comments:
Labels: , , , ,

Tuesday, March 16, 2010

DBCC CHECKDB Reports Corruption in Microsoft SQL Server

Is DBCC CHECKDB statement giving you consistency errors while checking the integrity and consistency of SQL Server database? This behavior occurs due to corruption to MDF (Master Database File) of Microsoft SQL Server and renders all your valuable data inaccessible. It leads to critical data loss situations. In order to get your mission-critical data back in such cases, SQL Database Recovery through reliable applications, is required.

The consistency errors are reported by DBCC CHECKDB tool, if the below situations true:

SQL Server loads the data in a column, which has sql_variant data type.
Data is originated in another column, having sql_variant data type. Additionally data is placed on-the-wire by MS SQL Server.
Numeric values are stored in sql_variant column.

Following are a few instances of SQL statements, which can result into this behavior:

The INSERT..SELECT statement, which specifies remote server in FROM clause of SELECT statement.
A BULK INSERT or a bcp statement from the file, which was created by SELECT statement from the SQL Server.
The database load through Data Transformation Services.

At the same time, you may also receive error messages similar to the following ones:

Server: Msg 2537, Level 16, State 43, Line 1 Table error: Object ID 587149137, index ID 0, page (1:1325), row 0. Record check (innerLength <= innerColInfo.CbMaxLen () && innerPCol != NULL) failed. Values are 17 and 5.
Server: Msg 2537, Level 16, State 1, Line 1 Table error: Object ID 587149137, index ID 0, page (1:1325), row 0. Record check (Valid SqlVariant) failed. Values are 1 and 0.
DBCC results for 'myvar2'. There are 1 rows in 1 pages for object 'myvar2'. CHECKTABLE found 0 allocation errors and 2 consistency errors in table 'myvar2' (object ID 587149137). repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (pubs.dbo.myvar2 ).

Microsoft offers a hotfix to sort out this problem, which can be downloaded from Microsoft's website. To repair and restore the damaged Microsoft SQL Server database, third-party SQL Server Recovery software can help you.

The MS SQL Recovery applications employ advanced scanning algorithms to thoroughly scan entire database and restore it to working state. They come equipped with simple and self-descriptive graphical user interface and allow you to carry out SQL Recovery on your own.

SQL Recovery is the most efficient utility that ensures absolute recovery in all MDF corruption scenarios. It works well with Microsoft SQL Server 2008, 2005, and 2000. The software restores all database objects such as tables, reports, forms, stored procedures, triggers, and constraints.
Posted by at No comments:
Labels: , , , ,

Sunday, March 14, 2010

Causes of Error 823 in SQL Server and How to Fix it

Do you encounter Input/Output (I/O) errors while accessing a MS SQL Server database? Are you unable to run queries on or access data from MDF (Master Database File)? This behavior indicates system or hardware problems with SQL Server that corrupt the database and renders it inaccessible. It leads to critical data loss situations. In order to extract data from Microsoft SQL Server in such situations, you need to opt for SQL Recovery solutions.

Hardware and system problems in SQL Server are generally indicated by an error message, similar to the following one:

“Error 823
I/O error detected during at offset in file ''”

You come across this error message when SQL Server attempts to read data from and write data to the database files. Format of this error message can be different, depending upon the version of SQL Server.

Cause

You come across this error message, if any of the below conditions are true:
Operating system error.
I/O logical check failure.
MS SQL Server database corruption.

If any of the above situations occur, it becomes essential to perform SQL Server Recovery by resolving it, to retrieve inaccessible data.

Solution

Try out the below things to fix up this issue, as per the cause of the the problem:

Operating system error: The read Windows API (Application Programing Interface) call or the write API call is unsuccessful and MS SQL Server experiences operating system errors, which is related to Windows API call. Run operating system integrity checking tools. Following is the example of operating system error:

“2003-07-28 09:01:27.38 spid75 Error: 823, Severity: 24,
State: 2
2003-07-28 09:01:27.38 spid75 I/O error 1117 (The request could not be performed because of an I/O device error.) detected during read at offset 0x0000002d460000 in file 'e:\program files\Microsoft SQL Server\mssql\data\mydb.MDF'”
I/O check failure: If specified logical data checks are unsuccessful, you may encounter this problem. Run DBCC CHECKDB to solve this issue.
Database corruption: Restore the database from recent backup. If the backed is unusable, Recover SQL database through third-party applications.

The SQL Database Recovery software are powerful enough to handle most of the database corruption issues. The applications use high-end scanning methods to ensure absolute recovery. They are incorporated with rich graphical user interface to provide quick and easy recovery.

SQL Recovery is the most advanced and powerful utility that is able to effectively handle all database corruption scenarios. The software works well with Microsoft SQL Server 2008, 2005, and 2000. It restores all MDF file objects such as tables, reports, forms, constraints, stored procedures, triggers, data types, and more.

Article Source :- http://hubpages.com/hub/Causes-of-Error-823-in-SQL-Server-and-How-to-Fix-it
Posted by at No comments:
Labels: , , , ,

Tuesday, March 9, 2010

Database Corruption After Running Alter Table Command on SQL Server Table


Are you getting incorrect results when you run “alter table” T-SQL (Transact-SQL) command for changing a column to null that is not null? The problem is caused if table column is the clustered index is in MS SQL Server 2000. This behavior may corrupt the MS SQL Server database (MDF) and make all your valuable data inaccessible. In such circumstances, you need to opt for SQL Database Recovery solutions, if an updated backup is not in place.

Along with the incorrect results of alter table command, you may also come across the below database corruption symptoms:

You get the records, which have null columns. But, you want only the rows, which have columns that aren't null.
The MDF file is marked as suspect. Furthermore, the SQL Server database becomes unavailable. You see some runtime errors in the error log of SQL Server.
If you check the logical and physical integrity of the database through DBCC CHECKDB command, it gives you the below corruption errors:

“Server: Msg 8934, Level 16, State 2, Line 1
Table error: Object ID 1977058079, index ID 1. The high key value on page (1:77) (level 0) is not less than the low key value in the parent (0:1), slot 0 of the next page (1:82).
Server: Msg 8933, Level 16, State 1, Line 1
Table error: Object ID 1977058079, index ID 1. The low key value on page (1:78) (level 0) is not >= the key value in the parent (1:75) slot 2.”

This behavior renders your database inaccessible. In order to gain access of your valuable data, you need to find out the cause of this problem and perform SQL Recovery by sorting it out.

Cause

This issue occurs if underwritten conditions are true:

MS SQL Server can't synchronize column status between sysindexes system table and syscolumns system tables.
Column is part of clustered index key, which may be null.

Solution

You can fix it by running dbcc dbreindex command by using repair_rebuild option. However, this method can not Recover SQL database.

In such situations, MS SQL Recovery software come for your help. These are powerful third-party applications, which methodically scan entire database to retrieve inaccessible data from it. They are totally safe and easy to use.

SQL Recovery is the most advanced solution to handle all types of SQL Server database corruption issues. It recovers all database objects such as tables, reports, formats, stored procedures, constraints, triggers, and more. The software is designed for Microsoft SQL Server 2008, 2005, and 2000.
Posted by at No comments:
Labels: , , , ,

Friday, March 5, 2010

MS SQL Server Database Corruption May Cause Access Violation

Are you facing Access Violation error in MS SQL Server? Are you unable to access the database and its objects? Access Violation is a situation where application can not access the data because the data is either damaged or the application does not own the data. In both the cases, your database remains inaccessible and unusable. This behavior may lead to significant data loss and needs MS SQL Recovery to be fixed.

In a practical scenario, consider:
In MS SQL Server 2008, a query contains the following clauses:
Union all
Group by
Inner join

The database query uses parallel execution plan.
You execute the query.

In this case, you may come across an Access Violation. Additionally, you may encounter the below error message:

“Location: xbmp.cpp:2038
Expression: 0 != pxteBitmap
Msg 3624, Level 20, State 1, Line 2

A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.

Msg 0, Level 20, State 0, Line 0

A severe error occurred on the current command. The results, if any, should be discarded.”

After the above error, database can not be accessed. In order to gain access of your SQL Server database, you need to carry out SQL Server Recovery by fixing this behavior.

Cause

As stated in the error message, you may have encountered such situations due to application malfunction or database corruption. Database corruption may occur after virus infection, unexpected system shutdown, operating system malfunction, and other similar situations.

Resolution

Consider running DBCC CHECKDB command to get your database repaired. It is an inbuilt utility in SQL Server that checks integrity and consistency issues of MDF (Master Database File).

However, if this tool can not fix the problem, third-party SQL Database Recovery software are always there for your help. These are advanced tools, which methodically scan entire database and ensure absolute SQL Recovery in most of the database corruption situations.

SQL Recovery is the most efficient tool to ensure absolute recovery of your damaged database. The software works well with Microsoft SQL Server 2008, 2005, and 2000. It restores all database objects such as tables, reports, forms, queries, stored procedures, triggers, and constraints.

Article Source :- http://hubpages.com/hub/MS-SQL-Server-Database-Corruption-May-Cause-Access-Violation
Posted by at No comments:
Labels: , , , ,

Thursday, March 4, 2010

Tips to resolve “Extent E_ID in database ID DB_ID...”

GAM (Global Allocation Map), SGAM (Shared Global Allocation Map), and IAM (Index Allocation Map) pages are three very important building blocks of SQL Server metadata structure. A GAM page contains one bit for each extent, where each bit states if the extent is already allocated or is available for allocation. Similarly, SGAM page too consists of one bit for every extent, which states whether the extent is mixed or dedicated, and contains one or more allocated pages. An IAM page again has one bit per dedicated extent, which is assigned to the index for which the IAM is a part. A systematic combination of these bits assures that the database is perfectly fine and is in usable state. However, the combination becomes damaged in case the database gets logically or physically corrupted. To overcome such situations, the user needs to opt for SQL Database Recovery solutions.

Below is the error message explaining the above scenario:

“Extent E_ID in database ID DB_ID is marked allocated in the GAM, but no SGAM or IAM has allocated it.”

After the above error message pops up, the database records become inaccessible. The above error message occurs due to following reasons:

When the extent is dedicated and also mixed.
When the extent is dedicated and also unallocated.
When the extent is mixed and also unallocated.
When the extent is dedicated, mixed, and also unallocated.

Resolution:

To resolve the above error message and to access database records, user will need to perform below actions:

Check for physical corruption of database by viewing application logs, SQL Server log, and system logs. To fix any hardware-related issue, the user will need to change the damaged system component.
Restore the data from an updated backup.

Check for logical corruption in database by executing DBCC CHECKDB command. This will enable the user to determine the exact extent of corruption. To fix the logical corruption, the user will need to run the same command with a repair clause. If the logical corruption persists, then s/he needs to take help of advanced SQL Database Repair application. A SQL Recovery tool employs effective repairing techniques to resolve all logical corrupted databases.

SQL Recovery repairs and restores MS SQL Server 2008, 20005, and 2000 databases, post any logical corruption scenario. The read only SQL Repair utility is safe-to-use as it does not modify the original database while repairing. It supports Windows 7, Vista, 2008, XP, 2003, and 2000 operating systems.

Article Source :- http://www.articlesengine.com/Article/Tips-to-resolve--Extent-E-ID-in-database-ID-DB-ID----/518598/1
Posted by at No comments:
Labels: , , , ,

Wednesday, March 3, 2010

How to Resolve “The text, ntext, or image node...” Error

The B-tree metadata structure of a SQL Server database saves the table records in various nodes, which are linked to each other in a hierarchical order. These nodes are primarily of three types – root node, branch node, and leaf node. The root node includes the value of branch nodes, which further contains values of leaf nodes. However, there might be certain situations where the child node does not match with the parent node. This situation mainly occurs when your SQL Server database gets corrupted/damaged. In such cases, you receive an error message while accessing the records saved in the SQL Server table. To access the table records after SQL database damage, restore the data from an updated backup. However, if no backup is available or backup does not fulfill your requirement, then you need to repair the table using a SQL Database Recovery software.

The above scenario is explained using the below error message:

“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.”

The error message appears when there the child node does not match its parent node. This occurs when:

The timestamp of the parent node is different from the timestamp of the child node.
The child node consists of text data, which is greater than the size of parent node.

The above scenarios primarily occur when your SQL Server database gets logically or physically damaged. To overcome the above error message and to access the table records, you need to repair the database. To do so, below are the two ways:

A physically damaged database requires replacement of damaged system component.
A logically corrupted database can be repaired using an inbuilt repair command – DBCC CHECKDB. The statement should be executed with a correct repair clause. In case logical corruption persists after running the above repair command, then you need to search for an effective MS SQL Recovery application that can repair your database. To find a powerful SQL Database Repair tool, search the Internet.

SQL Recovery is one powerful tool that successfully repairs logically corrupted database created in SQL Server 2008, 20005, and 2000. The repaired database is in re-usable state and can be stored at required destination. The SQL Database Repair application supports Windows 7, Vista, 2008, XP, 2003, and 2000.
Posted by at No comments:
Labels: , , , ,

Tuesday, March 2, 2010

Storing SQL Server Database on Network Server May Cause Corruption

Microsoft usually urges that you should use a SAN (Storage Area Network) or locally attached hard drive to store MS SQL Server database (MDF) files as this configuration improves SQL Server reliability and performance. Use of network database (stored on network server or NAS [Network Attached Server]) is disabled by default in Microsoft SQL Server. In order to ensure complete data safety and to prevent need of SQL Database Recovery, you should not use SQL Server database on networked server.

Though, it is not recommended, but it is possible to configure MS SQL Server for storing the database on a NAS storage server or networked server. Data storage servers, that are employed to store MDF database, must meet the SQL Server needs for 'write-through guarantees' and 'data write ordering'.

If you try to create SQL Server database file on UNC or mapped network location results into any of the below error message:

5105 "Device Activation Error"

Or

5110 "File 'file_name' is on a network device not supported for database files."

The above behavior is quite expected. The trace flag 1807 let you to bypass the check process and enables you to configure MS SQL Server with the networked database files. Microsoft SQL Server and various other relational database management systems use the transaction log and associated recovery logic, that ensure database integrity and consistency in case of system failure or improper system shutdown.

These SQL Server Recovery protocols bank on the capability to write instantly on the hard drive media so that if any operating system I/O (Input/Output) write call returns to database manage, recovery system is assured that write operation is really complete or the completion of write process can be ensured. Any type of failure by any hardware or software components of this protocol may result in complete or partial data loss due to corruption of MDF file.

In such critical circumstances, you need to restore the damaged database from the most recent backup. However, if the backup is either not available or not updated, third-party MS SQL Recovery software is the only way to go.

The MS SQL Recovery applications are powerful enough to carry out in-depth scan of entire SQL Server database and extract all inaccessible database objects. With the read-only and simple graphical user interface, they are completely safe and easy to use.

SQL Recovery is the most prominent tool that enables absolute recovery in all cases of MDF corruption. It restores all database objects such as tables, reports, forms, modules, queries, constraints, stored procedures, and triggers. The software is compatible with MS SQL Server 2008, 2005, and 2000.
Posted by at No comments:
Labels: , , , ,

Monday, March 1, 2010

Fixing “Multiple IAM pages for object....” Error Message


MS SQL Server database data files are divided into numerous GAM (Global Allocation Map) intervals. Each GAM interval consists of at least 4GB space or 64,000 extents. The page interval allocates one or more pages to an index that contains an IAM (Index Allocation Map) page for that GAM interval. However, the problem occurs when the index contains more than one IAM page for a GAM interval. The above situation primarily occurs when the SQL Server database gets corrupted or damaged. To overcome such database corruption scenarios, an easy way followed by most of the database users is restoration from an updated backup. However, in case of unavailability of a valid backup, you need to use advanced MS SQL Recovery application.

Consider a practical case, where you attempt to access the records saved in one of your tables. Instead of viewing the table records, you receive the below error message:

“Table error: Multiple IAM pages for object ID O_ID, index ID I_ID contain allocations for the same interval. IAM pages P_ID1 and P_ID2.”

The same error message pops up every time you attempt to access the database table records. Additionally, the records saved in the database table become inaccessible after the above error message pops up.

Cause:

The reason for the occurrence of the above error message is that there are two IAM pages (P_ID1 and P_ID2) that cover the same GAM interval. This occurs either due to physical or logical corruption of the database.

Resolution:

To resolve the above error message and to access the database table records, you need to repair the database using below methods:
Change the damaged/corrupt system component to isolate the physical damage reasons.
Run DBCC CHECKDB command (with repair clause) to isolate all logical corruption scenarios.
If the problem persists, then you need to repair the database using an advanced SQL Database Recovery software. A SQL Repair application repairs corrupt database in all cases of logical corruption.

Stellar Phoenix SQL Recovery is a trust-worthy solution for resolving all sorts of corruptions in SQL database. The software brings the database in a re-usable state in three simple clicks. Compatible with SQL Server 2008, 2005, and 2000, the SQL Repair tool saves the repaired database at required location. It is designed for Windows 7, Vista, 2008, XP, 2003, and 2000.

Source Taken From :-
http://www.articlesengine.com/Article/Fixing--Multiple-IAM-pages-for-object------Error-Message/514071/1
Posted by at No comments:
Labels: , , , ,
Subscribe to: Posts (Atom)