MDF File Recovery

Discussing ways to easily recover SQL Server 2000 suspect database

2012-01-24T23:10:00.000-08:00

MS SQL Server 2000 is widely used all over the world as the data storage component of several large websites. It is a cross-platform application that supports various advanced and user-friendly features, such as Microsoft search service, federated servers, indexed views, etc. It can help you achieve the desired performance levels required for running large web applications. However, an SQL database may occasionally become corrupt. The potential reasons responsible for this corruption are virus infection, hardware errors, abnormal system shutdown, etc. As a consequence, all valuable objects in the database become inaccessible. To overcome this problem, you need to go for SQL recovery through a reliable third-party utility.

Suppose, you use MS SQL Server 2000. While trying to access one of your databases, you may receive the following error message on your screen:

“96/11/18 10:48:32.60 kernel udopen: Operating System Error 32 (The process cannot access the file because it is being used by another process.) during the creation/opening of physical device,
C:\DATA\SQL\MSDB.DAT (or C:\DATA\SQL\MSDB.MDF)”

Cause: The above error occurs because you are trying to access a database that is marked as 'suspect'. There could be a number of reasons responsible for this, such as database corruption, missing device driver, database being moved to another location, etc.

This would render your SQL database inaccessible and lead to severe data loss. At this stage, you may use an updated backup to restore the database. However, if the backup is unavailable, you should follow the below mentioned resolution steps.

Resolution: You can try to resolve the issue by following any of the given methods:

Make sure that your system has all the necessary device driver files.
If your SQL database is corrupt, you need to follow the given procedure.

First, drop and recreate all indexes in your database.
Create a new database table and copy all records from the original table to this newly created table.
Now, update the statistics.
Run the following command:

'DBCC UPDATEUSAGE'.

Finally, run the 'sp_recompile' procedure

If the problem still persists, you should take help from a competent SQL server recovery tool. These third-party software are proficient in repairing corrupt SQL databases to recover valuable objects, including tables, views, indexes, constraints, triggers, stored procedures, etc. They allow you to take a sneak peek at the database objects prior to recovery.

How to troubleshoot SQL server Error 9002

2011-12-27T22:37:00.000-08:00

SQL server database mainly contains two files, one is data file & another is log file. Data file contains the information about data while log file contains the information about transactions in the database. In simple recovery model, log files are managed automatically but in case of bulk-logged & full recovery model database administrators are responsible to manage the size transaction log file. You can perform this by shrinking the transaction log file.

Sometimes, SQL server database generates an error message 9002 when it found insufficient log space. This error message will appear when SQL server database is online or in recovery mode. If database is online and struggling with log space problem then you can read the database but unable to do any update on it. If log fills during recovery then SQL server marks database in suspect mode.

Space Full

The log file for database '%.*ls' is full. Back up the transaction log for the database to free up some log space.

Work Around:As error message states, if the size of log file is full thenimmediately take the backup of database and issue some free space forthe log file. Now the point comes in your mind, how to perform this.To do this follow the below given steps:

Backup the transaction log.
Issue some disk space.
Move the log file to a disk drive (secondary storage media) with sufficient space.
Enlarge the log file.

These are thepossible user action required to perform the SQL server recovery. Detail description is given below:

Backup thetransaction log: If you are usingsimple recovery model then backup of transaction log is not possible.Take the backup of transaction log file, if you are using bulk-loggedor full recovery model.

Issue some diskspace: Regardless of recovery models,freeing the disk space allow recovery system to enlarge thetransaction log file automatically.

Move the log fileto a disk drive: If you are unable tofree some disk space to the transaction log file then move the logfiles to a disk drive with sufficient space.

Unable to Start MS SQL Server Database

2011-11-27T23:12:00.000-08:00

Database Users or administrators can start Microsoft SQL server database from the task bar. To start, go to the task bar, open sq server service manager and then click on the start button. Sometimes MS SQL server is not start through this method and give some error message like

2011-11-20 10:15:39.87 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)

Most possible reason for the above error message is “model is corrupt”. To resolve this, you can create a new copy of tempdb. This will fix the starting problem of SQL server database. If you still face the same problem then first of all make the backup of all MDF & LDF files.

How to Make Backup when Unable to Start SQL Server? As we have discussed, you are unable to start sql server then take a backup of data & log files by below steps:

Set SQL server service manual by Windows control panel.
Reboots the windows.
Copy all the data and log file to the another computer or any removable media.

Attention: Don't try any methods until you have backup.

Have Backup? If Yes then use another copy of sql server with same version and level to restore model database using model.mdf & model.ldf. After restore, detach model database from new sql server and copy the data & log files to replace problem server. It is little bit messy to recover SQL server but not hard. In simple words, we can say that you will have to perform three steps:

Restore-->Detach-->Copy (data & log files)

Doesn't Have Backup? If you don't have any backup of sql server database then it is recommended you to install a new copy of MS SQL server. When installation is complete the stop the service and copy the Model file to replace problem server.

Summary: SQL server database starting problem can be resolved by two method, one is restore-detach and another is new installation. Restore-detach method is hard in comparison of new installation method but it is effective.

Exploring the concept of Page Corruption in MS SQL Server databases

2011-11-01T04:05:00.000-07:00

No matter how reliable your database seems to be, you always have issues on the performance grounds. More interestingly, I found out that many performance issues relate to page corruption in SQL Server. It would be good to understand here what exactly is meant by ‘BAD_PAGE_PROCESS’. It usually occurs when the background suspect page logger stops running after every five seconds because of a large number of suspect pages. If you want to checkout suspect pages, run the following T-SQL command:

“select * from msdb.dbo.suspect_pages”

I took the help of DBCC CHECKDB on a corrupt SQL database to find out the actual issue and whether it is able to resolve it. Ran the following command:

“DBCC CHECKDB () WITH ALL_ERRORMSGS, NO_INFOMSGS”

Got errors similar to this one:

“Table error: Allocation page (1:1002912) has invalid PFS_PAGE page header values. Type is 0. Check type, alloc unit ID and page ID on the page.”

The PFS pages can neither be deleted nor reconstructed as there is no easy way to examine which pages are allocated or not.

Now, I tried to view the contents of the page by using the ‘DBCC PAGE’ command as follows:

“dbcc traceon(3604)

dbcc page(,1,1002854,0)”

After looking at the content of the page, I found that there was some corruption in the next page pointers. This seemed to be a bit weird as initially the next page pointer was like:

“m_nextPage = (1: 1002855)”

When I decided to look at the next page and ran:

“dbcc traceon(3604)

dbcc page('GBLDataWarehouse',1,1002855,0)

go”

It was now pointing to page 0:

“m_nextPage = (0:0)” & “m_prevPage = (0:0)”

Finally, used a recent backup to restore the database and got it up and running once again. But again, it was wise to see where the issue occurred.

Transaction Log File & Recovery Models

2011-10-10T03:44:00.000-07:00

SQL Server transaction log file is used to store recent database transactions. When you modify or alter any entity in SQL server database then it will be result in a write action in the transaction log file. Generally we do several activity on the SQL server database like add, delete, rename, update, insert and many more and this will also be the result of write action in the transaction log file but a read action on the SQL server database does not change the transaction log file.

Does recovery models affect transaction log?

The answer is NO. Recovery models (simple, full & bulk-logged) do not affect what has written into the transaction log but it effects the time period of entries that present in the transaction log, detail description is as follows:

Simple Recovery Model: In this recovery model, transaction log entries are keeping for the database integrity not for the database recovery purpose. When we run checkpoint operation on the transaction log files then all the inactive entries are deleted and space is ready for reuse. It is also the best way to manage the size of transaction log file but you can prefer another way also to manage size of transaction log file.
Full Recovery Model: In this recovery model, entries are key for the both integrity as well as for database recovery purpose. All the entries are remains present in the transaction log file until a log backup does not perform on the file. Sometimes it difficult to manage the size of transaction log files through this recovery model.
Bulk-logged Recovery Model: It is almost same as full recovery model but in this recovery model bulk operations are minimally logged.

How to Monitor Size of Transaction log file?

You can monitor the size of transaction log file by DBCC SQLPERF command. When will you run this command then it returns information about amount of log space used currently and it also indicates when transaction log is in need to truncate. Log truncation frees the used disk space but does not reduce the size of physical transaction log file. To reduce transaction log file size, you will have to shrink the log file.

How to shrink transaction log file in full recovery model?

You can shrink the transaction log file manually by the using of DBCC SHRINKFILE command. This command may be differ for the different SQL server database.

How to Fix Error “Unable to attach database” In SQL server?

2011-09-20T22:46:00.000-07:00

Last Tuesday, we have faced a scary situation when my friend's hard drive has crashed and he has not maintain any backup for the database then he has used data recovery services offered by stellar data recovery and retrieve his database and log files. After retrieving database and log files, he came to me and ask how to fix error 5173 and 824.

After retrieving database and log files from the crashed server, he had tried to attach the SQL server database but got error messages 5173 & 824 and unable to access his database. He can't recover SQL database from backup because i have mentioned above he has not maintain any backup.

How to Fix: We have followed below steps to fix the errors.

We have created a database with same name and same SQL data files (MDF & NDF).
Make the file size identical as original SQL server database
Stop the SQL server database services.
Rename the old MDF to new one and copy the old MDF to new MDF location
Delete the LDF files.
Start SQL server database services
Our database has gone in suspect mode.
Update the sysdatabases to update to Emergency mode. This will not use LOG files in start up Sp_configure “allow updates”, 1
go
Reconfigure with override
go
Update sysdatabases set status = 32768 where name = “corruptDBName”
go
Sp_configure “allow updates”, 0
go
Reconfigure with override
go
Now restart SQL server database.
Our database is in emergency mode.
Run DBCC CHECKDB on our database with repair_allow_data_loss, that will rebuild the log files and full repair.
Again restart SQL server database and now our database is online.

How to Move SQL server user Database?

2011-08-23T03:22:00.000-07:00

Microsoft SQL server has two types of database, one is system database and another is user database. A system database is used by the SQL server for its own maintenance and management while a user database is used by the database administrator for storing user data. In this article, we will discuss about to “How to move SQL server user database within same instance”.

A database administrator can move data and log files of user database to a new location by specifying the new location in a filename clause of ALTER database statement. To move a SQL server user database follow the below steps:

Set the database off-line through this command

ALTER DATABASE database_name SET OFFLINE;

Move the files to a designation location

Run this command for each move file.

ALTER DATABASE database_name MODIFY FILE ( NAME = logical_name, FILENAME = ' new_path\os_file_name' );

Now set the database online through this command

ALTER DATABASE database_name SET ONLINE;

Verify the changes

SELECT name, physical_name AS CurrentLocation, state_desc

FROM sys.master_files

WHERE database_id = DB_ID(N'');

Note: The above method is applied to moving database within the same instance of SQL server database. To move database from one instance to another, you can try backup and restore method.

Example: Suppose we have a log file sqlserverdatabase and want to move in to a new location.

Use master;

SELECT name, physical_name AS CurrentLocation, state_desc

FROM sys.master_files

WHERE database_id = DB_ID(N'sqlserverdatabase')

AND type_desc = N'LOG';

ALTER DATABASE sqlserverdatabase SET OFFLINE;

ALTER DATABASE sqlserverdatabase MODIFY FILE ( NAME = sqlserverdatabase_log, FILENAME = 'C:\NewLoc\sqlserverdatabase_Log.ldf');

ALTER DATABASE sqlserverdatabase SET ONLINE;

SELECT name, physical_name AS CurrentLocation, state_desc

FROM sys.master_files

WHERE database_id = DB_ID(N'sqlserverdatabase');

AND type_desc = N'LOG';

Restore SQL server Database in case of Corruption

2011-08-19T02:34:00.000-07:00

MS SQL server database offers a high performance backup and restore facility to its database users for maintaining the backup of SQL server database and restore in case of corruption. SQL server database may be corrupt due to severely reasons like media failure, user errors, power failure, metadata structure corruption, virus attack and many more. High performance backup and restore facility enables database administrator to handle all above corruption issues in SQL server database. A well planed backup and restore strategy helps database administrator to protect their data in case of above mentioned failures. The point comes to describe backup.

Backup: A copied data that can be used in restoring the corrupted data is called backup.

How to make a backup of SQL server database? : A database administration can take a backup of SQL server database with the help of SQL server management studio. Below image is the screen-shot to make a backup in SQL server database.

Restore SQL server Database in case of Corruption?: A database administrator can restore corrupt SQL server database with the help of good backup but he/she will be also able to restore corrupt SQL database without any backup. In this article we will discuss about both two methods for restoring corrupt SQL server database.

Restore with Good Backup: A database administrator can use “backup & restore” method, if he has maintained a good backup for his database. Two machines are required in this method. One is source machine where corrupt database reside and another is designation machine where corrupted database will be restored.

Note: Make sure following point before restoring the database

The designation machine has sufficient space to restore.
Directory structure on designation machine is must to exist.
Don't have same file name on the designation machine.

Restore without Backup: A database administrator is still able to restore corrupt SQL server data files without any good backup. In this situation, you should take help from any Microsoft gold certified SQL server recovery software. Stellar Phoenix SQL recovery software is a Microsoft gold certified partner that repairs corrupt SQL server data files and its objects. It is the most recommended software by the database expert to repair corrupt SQL server database.

How to fix Error “Open Failed” in SQL server

2011-07-27T00:12:00.000-07:00

When you are trying to start the services of SQL server database and found the database is unavailable. At this situation you are unable to do any operation on the SQL server database like insert, delete, rename, update, and many more or even unable to open the SQL server database. You can open and see SQL server error log to know the reasons for the problem. After knowing the reason, you can take appropriate method to recover sql server database. When you open the error log got an error message. The error message is:

"FCB::Open failed: Could not open file for file number . OS error: 5(access denied)"

Possible Cause: There are tons of reasons for the above problem but we will discuss here about hardware failure problem and account access problem.

Hardware Failure Problem: Whenever you will get the above error message. It is recommended you to check the hardware component of your system first before try any other action. If you found any faulty hardware component then replace it with new one and fix the problem.

Account Access Problem: The account in which SQL server is running does not has permission to access the folder that contains data and log files.

Follow Steps to Fix: You can fix the above error message by following the below steps:

Click on the Start button of your system
Go to the programs and select SQL server
Click on the folder that contains one the database files
Right click on the folder
Select sharing and security
Now, select security button
Click on the Add button
A text box will be appear
Write qualified user-name of the service account in the text box
Check the allow column to ensure full control
Repeat these all steps for all other database and log folder.
Shutdown the SQL server database
Now, restart the SQL server database from configuration manager.

How to repair MS SQL server 2005 Database?

2011-06-21T23:28:00.000-07:00

In this article, I have described about how to repair a corrupt “MS SQL server 2005 (compact edition) database” with the help of engine object repair methods.

MS SQL server 2005 compact edition database has several files and all these files are divided into four kilobytes unit each, these files are known as pages. SQL server compact edition database stores a checksum for all pages. If a page is corrupted or damaged then checksum of the page does not match with stored checksum. There are so many reasons for the corruption in the database file like Meta data structure corruption, virus attack, sudden system download, hardware failure and many more. If you have verified that there is a corruption in the database file then you can repair sql server database file by the engine object repair method.

You can verify corruption is the database file by calling system.data.sqlserverce.sqlceengine command. If this command returns a true value then there is no corruption in the database file and if this command returns a false value then there may be some corruption in the database file. The syntax for verifying the corruption is given below:

Syntax for verify

if (false == engine.Verify()) {...}

If a database file has been corrupted then you can recover database file by engine object repair methods. This method scans and fixes the corrupt database file. Engine object repair method provides two repair methods:

1) repairoption.deletecorruptedrows
2) repairoption.recovercorruptedrows

Repairoption.Deletecorruptedrows: This method discards all the corrupted pages and recovers the database files but you may lose some data if corrupt database file contains the database schema.

Syntax for this method
engine.Repair(null, RepairOption.DeleteCorruptedRows);

Pros: Guaranteed that recovered database is free from logical corruption.
Cons: You may lose some data, if you will use this method.

Repairoption.recovercorruptedrows: This method tries to read more data from corrupted database files and recover more data as can possible.

Syntax for this method
engine.Repair(null, RepairOption.RecoverCorruptedRows);

Pros: Recover more data in comparison with repairoption.deletecorruptedrows.
Cons: Does not guarantee that recovered database is free from logical corruption.

Analyzing DBCC CHECKDB failure in severe corruption cases and MDF Database Recovery

2011-05-27T02:02:00.000-07:00

The DBCC CHECKDB utility is used more often than not by almost all SQL database users. This eminent utility makes use of an internal database snapshot to obtain transactional consistency of the database. It uses this information to check and repair SQL database following a three stage process. In the first stage, it performs an allocation check. Then it checks all the critical system tables for consistency errors in the second stage. In the final stage, a consistency check of the whole database is performed. Sometimes due to severe corruption, the process cannot be completed. If the CHECKDB utility fails to repair corruption, you should go for SQL recovery through a reliable third-party software.

For instance, you use MS SQL Server 2000. While running CHECKDB on one of your important database files, you notice that the process terminates unexpectedly giving you the following error message:

“Database 'DBNAME' consistency errors in sysobjects, sysindexes, syscolumns, or systypes prevent further CHECKNAME processing.”

Cause:
The CHECKDB utility encountered some errors in the second stage that it cannot repair. So, it simply aborts the process before reaching the third stage and throws the above specified error message. The completion of the second stage is necessary for executing the third stage.

This could have happened due to metadata corruption in the database system tables. Corruption may make all the components in your database inaccessible. You may use a backup to restore all the lost or inaccessible data. If the backup is missing, you should follow the below mentioned resolution steps to perform MDF file recovery.

Resolution:

Try the following methods to resolve the problem-

Check the SQL Server error log and the Windows application and system log to determine the cause of the problem. If hardware failure caused the problem, run the hardware diagnostics tool.
Run DBCC CHECKDB with proper repair clause to fix corruption.

If the problem still persists, you should take help of a SQL database recovery software. These software are capable of recovering the damaged SQL database components in their original form restoring all their properties and relationships with other components. They retrieve tables, views, queries, indexes, stored procedures, keys, constraints etc. from the corrupt database.

How to Recover Database When MDF file get corrupted ????

2011-04-12T03:07:00.000-07:00

The data loss from the database is a very panic situation that occurs without any warning message. It can corrupt or damage our data stored on our hard drives or on any storage media. The database may be corrupted due to hardware failure, application failure, improper system shutdown, media read errors, software failure, power failure, virus attack and many other reasons. In such case you need to use an advanced database recovery software to recover and repair corrupted database. In case of MDF file corruption, you may face any of the given below error messages:-

“Windows could not start the SQL Server”
“MDF is not a primary database file”
“Server can’t find the requested database table”
“Database Can’t Be Accessed”
“The file *.mdf is missing and needs to restore”
“The execution of a full-text query failed”.

Solution: To repair and restore corrupted .mdf file by any of the above error message follow given below steps:

Fix Hardware Issue: To fix the error message check your hardware setup if found any problem with the hardware then repair or replace it by new one and fix the problem.

Run DBCC CheckDB Command: If the problem is not related to hardware then run dbcc checkdb command without any clause and then run again dbcc checkdb command with the proper repair clause.

Restore from Backup: After running the dbcc checkdb command and you still getting an error message then restore database from the latest and updated backup. If you have no any backup then you should try an advanced mdf recovery utility to repair and restore corrupted .mdf file.

Reliable mdf repair utility for risk-free recovery of your SQL server database

2011-02-10T03:34:00.000-08:00

If you are using a Microsoft SQL database for storing your valuable business transactions and financial information, then, any instance of database corruption can be a huge blow to your business. The damage to the database can result in the complete inaccessibility of the data stored n it. In such cases, you can run ‘DBCC CHECKDB’ from the command-line, which can repair and fix the MS SQL database errors. If with higher degree of corruption, the database DBCC CHECKDB fails to resolve the problem, you can always run an reliable SQL repair utility to accomplish the job safely.

Following are some of the error messages, which you may encounter, while trying to fix them with DBCC CHECKDB command:

“Server: Msg 8905, Level 16, State 1, Line 0
Extent (1:6945928) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 0
Extent (1:6945936) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 0
Extent (1:6945944) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.

The command fails to resolve the issues and further flashes the below messages:

Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.”

Cause:
The MS SQL Server database has been severely damaged and DBCC CHECKDB is unable to repair the same.

The best possible way to get the database and the data back is to restore it from a valid backup. If you have not taken any backup recently or there are any unresolved problem in restoring it from the backup server, then, you have to look for any good mdf repair utility.

These SQL recovery software are meant to repair the corrupt SQL database and recover the tables, schema, triggers, containers etc with their originality being intact.

Stellar Phoenix SQL Recovery is a trusted utility to safely repair SQL database and recover your data without any alteration to the database. This efficient utility is capable of repairing the MS SQL Server 2008, 20005, 2000 databases and is completely compatible with Windows 7, Vista, 2008, XP, 2003 and 2000 operating systems.

Use Advanced SQL Recovery Tool to Repair MDF Files

2011-02-06T22:07:00.000-08:00

If you are regularly using Microsoft SQL 2008, then you might have faced several situations wherein you are unable to mount a SQL Server database. Such cases are sometimes cause very serious problem such as database corruption or complete inaccessibility of the SQL database thereby making your database very insecure. These corruption scenarios can arise due to various reasons such as automatic system shutdown when the database is running, power failure, virus infections, hardware issues, human errors etc. In such cases, you should find the cause of database corruption and try to repair SQL. If you are unable to repair SQL(.MDF) file, then you should use an advanced MDF file repair software to perform SQL database recovery.

Consider a Practical scenario wherein you try to open a SQL database while using MS SQL Server 2008. However, database does not open. An error message appear as a result, which is:

"Database '%.*ls' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server error log for details."

Cause:

The root cause of above error message is that the database could not be mounted because some resources or files are missing.

Resolution:

To resolve above error message, you should repair MDF file. To do this, you need to perform the given below methods:

Check Error log: Firstly, You should check error log to get the details about resources such as disk space, memory, permission failure, etc that may have caused the above problem.

Confirm the location of SQL Database files: You should check the location of MDF or LDF files and verify whether Database Engine account has required credentials to access these SQL Database files.

Restart Database: Finally, you should restart the SQL Server database with the help of ALTER DATABASE query. This query sets the SQL Server database to online.

Above described methods should be able to set the SQL database up. However, if you still are unable to mount the database then you should use a SQL repair tool to repair SQL Server database. Such MDF database repair software are read-only in nature.

Stellar Phoenix SQL Database Recovery software is an SQL database repair tool that repairs MDF file and NDF file alike. Specifically designed for MSSQL Server 2000, 2005, 2008 and 7.0. This MDF file repair tool restores various database objects such as collations, tables, stored procedures, triggers, defaults and many more. In addition, this repair mdf software preserves the relationship among the database tables.

Binary Tree Corruption cause Data Loss in SQL Server

2011-01-28T00:31:00.000-08:00

Microsoft SQL Server database supports binary tree indexes for fast query. The pages of Binary tree index are known as index nodes, the top node of binary tree is known as root node. However, the middle nodes are known as branch nodes and bottom nodes are known as leaf nodes. If table indexes get damaged, SQL Server database shows an error message and you unable to access your SQL database. To resolve such situations, you should use your most latest backup and restore the lost data. Sometimes, backup fails to restore the database and thus, you need to use SQL database recovery software.

You are working on SQL Server database wherein, You might get below error message:

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.

Root Cause of Problem:

The above error message appears when SQL Server database find a break in logical page chain at any level of Binary tree. It can happen at any level of binary tree including root, middle and leaf nodes.

Resolution:

For solving the above error message, you should follow the given below steps:

Run the hardware diagnostics as above problem could occur due to hardware problems. Fix the hardware problems, if any.
If the problem persists still then restore the corrupted SQL Server database from a latest and clean backup.
In case of unavailability of valid SQL server backup, you could run DBCC CHECKDB command to find the amount of corruption and note the repair clause. Again run DBCC CHECKDB command with suggested repair clause.
If database still unaccessible, you should use an advanced SQL database recovery tool.

These SQL database recovery tools are advanced tools that can effectively repair and restore corrupted SQL databases. Such tools are equipped with rich GUI, to-the-point documentation. You can freely use these software for repairing and restoring corrupted or damaged SQL Server database in any case of SQL database corruption.

The most trusted SQL Database recovery tool by the many database administrator is Stellar Phoenix SQL Recovery tool. It is a complete repair software for damaged or corrupted SQL Server databases. This software supports mdf recovery for SQL Server 2008, 2005 and 2000. It is available with advanced graphical user interface and restores all database objects like tables, triggers, user defined data types, stored procedures, collation views, rules and many more. The software is compatible with Windows Vista, XP, 2003, 2000, NT and 7.0.

Recover SQL Server Database from Corrupted Table

2011-01-20T20:14:00.000-08:00

Sometimes when you want to update or delete SQL server database table and got an error message that shows your SQL server database table has been corrupted. This may happen by the several reasons some of them are improper system shutdown, virus attack, hardware failure, power failure and many more. At this situation you will be unable to access your SQL server database table. For fixing this problem you should use an advanced SQL server recovery software that will repair and restore your damaged SQL server database table.

Consider a practical scenario wherein, you may encounter the given below error messages while your are trying to update, delete or open an SQL server database table:

“Error: 644, Severity: 21, State: 5
Could not find the index entry for RID '1613b1000000100' in index page (1:189), index ID 7, database 'TestDB'..
Error: 8646, Severity: 21, State: 1
The index entry for row ID was not found in index ID 7, of table 2009058193, in database 'test644'.”

Particularly the above error message occur on the non-clustered index of Microsoft SQL server database but sometimes this problem also occurs with the clustered SQL server database database.

Resolution: For restoring corrupt SQL server database table, you have four option which are given below:

Fix Hardware Issue: Check the hardware of the system if you find any faulty hardware then replace it with the new one.
Restore from Backup: Restore it from the latest backup, if backup is clean and updated.
Run DBCC CHECKDB: Run this command to fix the problem.
Re-built Indexes: If possible then rebuilt indexes of table but it is not the better idea.

After performing three above steps and you are still unable to fix the problem then the best idea is to buy an advanced third party SQL recovery software to fix the problem.

Stellar Phoenix SQL Database Recovery is an MDF recovery software that is able to repair MDF as well as NDF files from all instances of corruption. It repairs corrupted MDF, NDF files created in SQL Server 2000, 2005, and 2008. This MDF file repair tool is capable of recovering various database components such as tables, stored procedures, views, collations, queries, triggers, etc. It is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

Disadvantages and Benefits by Using Stored Procedure

2011-01-13T03:31:00.000-08:00

Stored procedure is a subroutine which is used for the accessing a relational database management system. It is also used for the storing the batch of statements in SQL server. Stored procedures are also known as StoPro, proc, SP, sproc or StoredProc and actually stored in the database data dictionary. Stored Procedure can returns or accepts value if needed. There are two way by whihch we can store a batch of statements in SQL Database, one is function and another is stored procedure.

Differences between function and stored procedure are given below:

Function must return a value but it is not necesary in the case of stored procedure.
Function has IN parameter only while stored procedure has OUT or IN Parameter.
Stored procedure can return no value or return multiple value by using OUT parameter.
Function could used SELECT Parameter while stored procedure cann't used SELECT Parameter.

Syntax for stored procedure is given below:

CREATE PROC[EDURE] urProcedureName
[<@InputParameter> Datatype default] [, 1..n] ]
[<@OutputParameter> Datatype OUT[PUT]][, 1..n] ]
[WITH { RECOMPILE | ENCRYPTION | RECOMPILE , ENCRYPTION } ]
AS
[BEGIN ]
[SqlStatements;][1..n]
[END]
GO

Benefits & disadvantages of stored procedure: Some of the benefits and disadvantages of stored procedure are given below.

Benefits:
Reduced network usage between client and server
Improved security
Enhanced hardware and software capablities
Reduced development cost and increased reliability
Centralized security, administration, and maintenance for common routines

Disadvantages: Stored procedure is vendor specefic language, if you want to change vendor's database then you have to rewrite your stored procedure language.

How to Resolve a "High Key Value on Page" Error Message

2010-12-08T03:11:00.000-08:00

The technique used in locating and placing data in SQL Server Database is known as B-tree. A B-tree contains a tree-level page that maintains and stores a key value for each child page. In case, the child page is leaf-level page, then all records stored on the tree-level page should contain key values equal to or greater than the key value stored in parent page. However, in case the child page is tree-level page, then all records stored on the tree-level page should contain key value that is equal to the value stored in parent page. Corruption in B-tree results in changing the values of tree-level values, further resulting in the inaccessibility of database records. The best way to surmount any B-tree corruption scenario is by restoring the data from an updated backup. But, in case of absence of an updated backup, you will need to opt for an advanced sql database repair application that can repair your database and provide access to all inaccessible database components.

Consider a scenario, where you receive the underneath error message when you attempt to mount your database:

- Table error: Object ID O_ID, index ID I_ID. The high key value on page P_ID1 (level LEVEL) is not less than the low key value in the parent P_ID2, slot S_ID of the next page P_ID3.
- Records saved in your database becomes inaccessible after the above error message appears.

Root Cause:

The main reason responsible for the occurrence of the above error message is corruption of metadata structure (B-tree values). Corruption can occur due to logical or physical damages.

How to Resolve:

For complete resolution of error message caused either due to logical or physical corruption, follow the below steps:
- In case of physical damage, swap the damaged system component with a new one.
- In case of logical corruption, run DBCC CHECKDB command (with correct repair clause).

While changing the hardware component completely resolves physical damage issues, DBCC CHECKDB command does not assure complete repair in all logical corruption scenarios. For such situations, you will need to use a powerful SQL Repair tool. These sql database repair utilities use effective scanning algorithms to systematically scan and repair the corrupted database.

SQL Recovery is a user-friendly software that safely repairs created in SQL Server 2008, 2005, and 2000. Built with interactive user-interface, the sql repair software recovers almost all database components, such as, tables, stored procedures, views, etc.

Adishree Singh work as a freelancer and researcher repair sql & repair sql database software.

Article Source: http://EzineArticles.com/?expert=Adishree_Singh

How to Resolve "B-Tree Chain Linkage Mismatch" Error Message

2010-11-22T03:04:00.000-08:00

The fast results of SQL queries is a result of b-tree indexes used by a SQL Server. A single B-tree consists of number of index nodes, root nodes, branch nodes, and leaf nodes that enable you to systematically store your data.

Corruption in any of the nodes (specially index nodes) can result into inaccessibility of records stored in the database. In most of these situations, you encounter an error message stating the exact cause. To surpass the above database inaccessibility circumstances, you will need to use restore the data stored from an updated backup. However, in absence of an updated backup or backup falls short to restore the required data, then you will need to search for advanced third-party sql repair application.

Consider a practical scenario, where you receive the below error message when you attempt view the records saved in your SQL Server database:

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.

After the above error message appears, the data stored in the database becomes inaccessible. Moreover, you receive the same error message each time you attempt to access the database.

Cause

The root cause for the occurrence of the above error message is the break in the logical page chain at any level (root or leaf) of B-tree. This scenario can occur due to various logical or physical factors.

Resolution

For absolute resolution of the above error message caused due to either logical or physical reasons, you will need to follow the below measures:

View full resolve methods by clicking here

http://ezinearticles.com/?How-to-Resolve-B-Tree-Chain-Linkage-Mismatch-Error-Message&id=3331494

MDF Recovery to Handle Assertion Failure in SQL Server 2008 and 2005

2010-11-11T02:19:00.000-08:00

Are you facing assertion failure errors, while executing queries on MS SQL Server 2008 or 2005 databases? Does the query execution process fail halfway and you encounter errors? You may face the assertion failure problems due to either software bug or Master Database File (MDF) corruption. In both the cases, you can not access the database and come across data loss situations. In order to extract data in these circumstances, restore the database from backup. However, if the backup is unavailable, Master Database File Recovery becomes essential.

For example, the process may fail when you execute a distributed query, which uses linked server in MS SQL Server 2008 or in MS SQL Server 2005. Furthermore, you come across the below error message:

"OLE DB provider "SQLNCLI" for linked server "Linked Server" returned message "No transaction is active.".

Msg 3624, Level 20, State 1, Line 1

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."

When an assertion measures to false value at run-time, 'assertion failure' may occur. It generally causes the execution process to abort. Assertion failure depicts attention to a location at which the logical database inconsistency is detected.

Assertion Failure renders MDF database inaccessible. In order to access your valuable data in the database, you need to identify the cause of this behavior and perform MDF File Recovery by fixing it.

Cause:

As stated in the above error message, this problem is caused by database corruption or application bug.

Resolution:

If the problem is caused by application bug or malfunction, you need to reinstall the SQL Server. In case of database corruption, repair and restore the damaged MDF file using MDF Recovery software.

The applications use high-end scanning methods to thoroughly scan the database and Recover MDF file in an absolute manner. They preserve the integrity of your data with read-only and non-destructive conduct.

Stellar SQL Database Recovery is the most comprehensive utility the repairs and restores damaged MDF file in all cases of corruption. It works well with Microsoft SQL Server 2008, 2005, and 2000. The software recovers all SQL Server database objects, tables, reports, forms, macros, constraints, triggers, and stored procedures.

Tips to resolve the error message “Possible bad chain linkage...”

2010-11-01T05:09:00.000-07:00

Allocation of MS SQL Server table data can be done either in B-tree or in heap structure. Data retrieval from a heap structure is slow as compared to retrieval from B-tree structure, which is very fast. B-tree structures minimize the navigation of your record, thereby resulting in fast retrieval of your data. B-tree structures use leaf nodes as storage components to save table records. Records saved in MS SQL Server table become inaccessible if these leaf nodes are missing, damaged, or not pointing to the correct parent node. In most of these situations, a database user encounters an error message. To overcome such error messages and to access table records, users can restore data from an updated backup. However, if no backup is available, then the user needs to opt for SQL Repair solutions.

To elaborate the above scenario, consider a realistic situation, wherein, you encounter the below error message while trying to access table records:

“Table error: Object ID O_ID, index ID I_ID. The next pointer of P_ID1 refers to page P_ID2. Neither P_ID2 nor its parent were encountered. Possible bad chain linkage.”

The error message does not allow you to view records saved in the table.

Note: This is a severity level 16 error message.

The above error message appears when a page (P_ID2) referenced by page (P_ID1) goes missing. Such situations arise when your SQL Sever database is logically or physically damaged.

To surmount the above error message, you first need to identify the exact cause of database corruption and then act accordingly. Below mentioned steps help you in identifying and repairing the SQL database corruption:

* To identify a hardware problem, you need to check the system, the application, and logs of SQL Server. After the damaged hardware is detected, you will need to swap it with a new component.

* In case, the problem persists even after replacing the hardware component, then your database is logically corrupted. To overcome logical corruption, you need to run DBCC CHECKDB command with a repair clause. In case the above command has no effect on your corrupted database, then you need to repair the database using an advanced third-party MDF Recovery utility. A SQL Repair application ensures complete repair after any kinds of logical corruption.

SQL Database Recovery repairs database created in MS SQL Server 2008, 20005, and 2000 and restores it at required location. It is a read only utility and repairs without modifying the original database. The SQL Repair software can be installed on Windows 7, Vista, 2008, XP, 2003, and 2000.

How to Protect Your Microsoft SQL Server Database

2010-09-28T02:51:00.000-07:00

When the server or database system of MS SQL Server 2008 or 2005 crash, it’s very difficult to recover the original data backup with MS SQL code, but its not impossible. MS SQL Server database unlike other databases such as FoxPro can copy data files; the former must have a backup strategy in order to secure data backup recovery. So take an appropriate backup & recovery operation to recover corrupted data, the data of MS SQL Server 2008 and 2005 can be safely protected.

Restore vs. Recovery

Restore and recovery are two different concepts, but in the database recovery process is also closely linked together. The difference between restore and recovery is given below:

Restore is equivalent to rebuild the part or whole of the database from a backup. It can not change the state of database, such as offline and online.

Recovery of database means it restore the database from offline to online state for users to use.

In Microsoft SQL Server database “Recovery” the database will no longer be able to operate the “Restore”.

A good backup and recovery plan for Microsoft SQL Server should cover the following steps:

1. Need data protection.
2. Daily / weekly / monthly backup plan.
3. Documented verify and the results of the test.
4. Documented the recovery process.

From Microsoft SQL Server 2005, MS SQL Server provides a lot of smart backup methods to recover damaged SQL server database. The main purpose of backup SQL Server database is to reduce the data loss, which asking for zero data loss, and need shorter interval of time to backup the data.

If you are facing data loss problem of SQL server database due to any reasons and not maintain your backup then you have to need smart third party SQL server recovery software to recover SQL database.

Stellar Phoenix Database Recovery software for SQL database is the best option to recover corrupted SQL database. It repairs and restores the database after almost all corruptions issues. It supports recovery of databases created in Microsoft SQL 7.0, 2000, 2005 and 2008. It repairs and restores MDF as well as NDF files of SQL server database.

Source: http://hubpages.com/hub/How-to-Protect-Your-Microsoft-SQL-Server-Database

Online Backup of Your Data

2010-09-24T05:19:00.000-07:00

Do you have backup copy of your data? I think many of people probably do not as it should. This data loss situation can ruin your business, and cause untold suffering to the loss of your valuable pictures and personal information. How do I know what data loss is? A few years ago, I suffered a complete failure of my hard disk unrecoverable on one of my personal computer. Fortunately, I have not nearly so “technical knowledge” at the time, and have most of my essential data “up” secured to the paper.

The loss of data, suffered from me, that hard drive failure is still very painful. I spent around month trying everything to recover data but not got my data. I replace lost, but still missing a number of very important data that I can not reproduce. I had several digital photos of my friends and family members, documents, licenses, software etc. that have been forever. After the rebuilding of my life back in months, I promised myself I would never support me for such thing again in life.

My backup of data routine has undergone several revisions over the years to the point that I felt very happy with my current situation. I had problem with lost data and my data backup this time saved me from the loss. Currently I have three redundant backup systems, including dedicated file servers for very large systems, external hard drive for complex picture and fire walls locked automatically. All these provide a pleasant feeling of security.

There are two mainly two reasons for the data loss one is physically data loss problems and another is logically data loss problems. The data loss due to environmental effect like fire, water, temperature is called physically data loss and the data loss due to the some internal errors in the software (programs) is called logically data loss.

In these modern age there are so many companies working towards to handle these data loss problems. I personally know stellar data recovery which is proving services for both data loss problem logical as well as physical data loss problems. Stellar data recovery has around 17 years experience in this field. It provides software for the logically corrupted data and has labs for the physically corrupted data.

Recently my SQL database gets damaged by the virus attack and I have tell already I maintain my backup regularly but I was unable to recover my SQL database with the help of backup then I have used stellar phoenix SQL database recovery software to restore my database.

Resource: http://hubpages.com/hub/Online-Backup-of-Your-Data

Memory allocation issues in MS SQL Server 2000 database results in Error 8902

2010-08-20T21:22:00.000-07:00

In MS SQL Server, the system errors related with memory allocation often prove to be fatal for the database. Such problems can be caused by several reasons such as database corruption, which, in turn, can be the outcome of various other reasons. These reasons include virus infections, abrupt or unplanned system shutdown especially when the database is open, database header corruption, etc. You should try to find out the exact reason for such behavior and try to address the situation. If nothing works out, then I would suggest you to use a third-party MDF recovery software to recover SQL database.

Let us take a look at one of the system error that appears while you are working on an MS SQL Server 2000 database:

"Memory allocation error during DBCC processing."

Cause:

Such memory allocation error occurs when there is no memory for the non-clustered index coverage checks.

Resolution:

Such system errors relating to memory allocation should be dealt by performing the following MDF recovery methods. Please note that you should perform these methods only in the given order:

Recovering the hardware corruption problems
Restoring from database backup
Running DBCC CHECKDB utility

For more resolution details visit this link: http://www.americanchronicle.com/articles/view/177453

I have a database marked as suspect or damaged log file (SQL Server 2005 only)

2010-07-15T04:54:00.000-07:00

If you have an mdf file that was not properly detached from SQL Server 2005 (possibly due to a hard drive crash), the first (best!) option is to restore the database from a valid backup. If that is not an option, then the database is most likely in need of repair.

If the database is in an un-attached state:

1. Make sure you have a copy of gendata.mdf (or eshadata.mdf)
2. Run the following SQL Statement in SQL Server Management Studio to attach the database and force SQL Server 2005 to create a new log file:

CREATE DATABASE gendata ON (NAME = 'gendata', FILENAME = 'c:\Program Files\Esha Research\data\gendata.mdf') FOR ATTACH_REBUILD_LOG;

Replace the above names with the appropriate names!

Once the database is attached, it is recommended to attempt to backup the database. If the backup is successful, great (keep going still). If not, continue on anyway.

The following SQL Statements are meant to address the 'suspect' aspect of the database.

* ALTER DATABASE gendata SET EMERGENCY
* ALTER DATABASE gendata SET SINGLE_USER
* DBCC CHECKDB(gendata, REPAIR_ALLOW_DATA_LOSS)
* ALTER DATABASE gendata SET MULTI_USER
* ALTER DATABASE gendata SET ONLINE

You should now have a working database.

Ref: http://www.esha.com/kb/questions/118/

How to rectify Error 7995 in SQL Server 2008 database

2010-07-07T05:24:00.000-07:00

The system catalogs in SQL Server databases are used to store various types of information such as number and names of tables and views in the database among many others. This information is collectively referred as metadata. However, sometimes this metadata may get corrupt due to various reasons such as virus infections, hardware issues, power outages, etc. In such cases, you should use the in-place methods to rectify the problem. However, if you are not able to recover SQL database, then you should use a third-party Repair SQL database software to do the needful.

Consider a scenario wherein you encounter the following error message while using the DBCC CHECKNAME tool on an SQL Server 2008 database:

"Database 'DBNAME': consistency errors in system catalogs prevent further DBCC CHECKNAME processing."

Cause:

There could be the following causes for this error. They are:

The system base tables are storing the metadata for all the objects in the database.

The system base tables are corrupt.

Resolution:

To resolve this erroneous situation, you need to recover SQL database. To do this, you should either of the following methods, in the given order:

For More Information Click This: http://www.americanchronicle.com/articles/view/167160

Fix the repair level on the DBCC statement error

2010-06-17T05:06:00.000-07:00

DBCC CHECKDB is a command that is mainly used to check the logical and physical integrity of MS SQL database. The command can be executed with three different parameters repair_allow_data loss, repair_fast, and repair_rebuild to repair an MS SQL database. While the command ensures absolute repair of logically damaged MS SQL database in most cases, there might be certain situations when this command fails to perform complete repair. Such situations occur when the corruption level of database is too high and beyond the limits of the command. However, a valid backup acts as a boon in such scenarios and allows the user to access the database. But if in case the user has not maintained any database backup, then the only way to repair the database is by using an effective third-party MDF Repair software.

To elaborate the above scenario, consider a practical case where your MS SQL database gets corrupted due to metadata structure damage. Now, when you execute the DBCC CHECKDB command (with repair_fast parameter) to repair your database, you encounter the below error message:

"DBCC results for 'sysindexes'.
The repair level on the DBCC statement caused this repair to be bypassed.
The system cannot self repair this error.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
There are 1953 rows in 127 pages for object 'sysindexes'.
CHECKDB found 0 allocation errors and 6 consistency errors in table 'sysindexes' (object ID 2).
DBCC results for 'syscolumns'.
There are 10093 rows in 218 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 32 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'. "

The database remains in the corrupted state since the DBCC CHECKDB command is unable to repair the database.

Cause:

The database is severely corrupted and might require rebuilding of indexes or de-allocating of all the corrupt pages.

Resolution:

To overcome corruption of your database, the user needs to repair the database by running DBCC CHECKDB command with repair_allow_data loss parameter. While doing so might resolve the error message, it will also result into deletion of data from your database. To avoid any loss of data, you should opt for a commercial MDF File Repair application. Such MDF Recovery tools do not overwrite or modify the original database during the repair process.

SQL Recovery is an efficient, yet fast MDF File Repair tool that repairs databases created in MS SQL Server 2008, 20005, and 2000. The non-destructive tool retrieves almost all objects of SQL database. It supports Windows 7, Vista, 2008, XP, 2003, and 2000 operating systems.

Fixing "Repairing this error..." Error Message

2010-06-14T22:10:00.000-07:00

MS SQL database corruption can result in serious damages, one of them being complete inaccessibility of all the records saved in database. To surpass any such corruption situation, a user can run DBCC CHECKDB command with a suitable repair clause. This command repairs the database in most situations by resolving all the physical and logical integrity issues. However, if the repair command displays an error message during repair, then it means that the database is beyond the repairing capabilities of DBCC CHECKDB command. In such cases, a database user can restore the database from an up-to-date backup and continue with his/her work. However, if the user has not maintained any database backup, then s/he needs to repair the database using a commercial MDF Database Recovery application.

Consider a practical case, where you encounter the below error message when you try to repair your corrupted MS SQL Server database using DBCC CHECKDB command:

"Server: Msg 8905, Level 16, State 1, Line 0 Extent (1:6945928) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it. Server: Msg 8905, Level 16, State 1, Line 0 Extent (1:6945936) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it. Server: Msg 8905, Level 16, State 1, Line 0 Extent (1:6945944) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it. . . . ....

and then the following:

Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first. Repairing this error requires other errors to be corrected first."

The database remains corrupted after the above error message appears.

Cause:

The root cause for the above error message is severe corruption of SQL Server database.

Resolution:

To repair a logically corrupted database when the DBCC CHECKDB command fails to repair, the user needs to use a third-party mdf database recovery software. MDF Repair tools perform complete repair using advanced scanning methods.

SQL Recovery Software is a superb MDF database repair application that repairs MS SQL Server 2008, 20005, and 2000 databases in just three mouse clicks. The MDF Repair tool can be installed on Windows 7, Vista, 2008, XP, 2003, and 2000 operating systems.

Fixing “The repair level on the DBCC statement...” Error

2010-06-11T00:15:00.000-07:00

To elaborate the above scenario, consider a practical case where your MS SQL database gets corrupted due to metadata structure damage. Now, when you execute the DBCC CHECKDB command (with repair_fast parameter) to repair your database, you encounter the below error message:

“DBCC results for 'sysindexes'.

The repair level on the DBCC statement caused this repair to be bypassed.

The system cannot self repair this error.

The repair level on the DBCC statement caused this repair to be bypassed.

There are 1953 rows in 127 pages for object 'sysindexes'.

CHECKDB found 0 allocation errors and 6 consistency errors in table 'sysindexes' (object ID 2).

DBCC results for 'syscolumns'.

There are 10093 rows in 218 pages for object 'syscolumns'.

DBCC results for 'systypes'.

There are 32 rows in 1 pages for object 'systypes'.

DBCC results for 'syscomments'. ”

The database remains in the corrupted state since the DBCC CHECKDB command is unable to repair the database.

Cause:

The database is severely corrupted and might require rebuilding of indexes or de-allocating of all the corrupt pages.

Resolution:

To overcome corruption of your database, the user needs to repair the database by running DBCC CHECKDB command with repair_allow_data loss parameter. While doing so might resolve the error message, it will also result into deletion of data from your database. To avoid any loss of data, you should opt for a commercial MDF File Repair application. Such MDF Database Recovery tools do not overwrite or modify the original database during the repair process.

Stellar Phoenix SQL Recovery is an efficient, yet fast MDF File Repair tool that repairs databases created in MS SQL Server 2008, 20005, and 2000. The non-destructive tool retrieves almost all objects of SQL database. It supports Windows 7, Vista, 2008, XP, 2003, and 2000 operating systems.

Resource Link: http://www.programmersheaven.com/user/williumdavid/blog/4887-Fixing-The-repair-level-on-the-DBCC-statement-Error/

Resolving Error 5171 in SQL Database

2010-04-28T21:47:00.000-07:00

SQL Server database corruption can occur due to SQL Server malfunctioning, improper system shutdown, virus infection, hardware failure and many more. Once SQL database gets corrupted, SQL server database become inaccessible. In such situations, use your backup, if there is no backup, the user needs to sql recovery software to repair mdf file. Consider a practical scenario, where a user is working on SQL Server 2005 and creating a report. While doing so, the Windows restarts due to power failure. When users restart the system, the SQL database becomes inaccessible. When the user tries to attach the MDF manually, he encounters the below error message:

“An exception occurred while executing a Transact-SQL statement or batch. _db.mdf is not a primary database file. (Microsoft SQL Server, Error: 5171).” Or

“C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\MYDATABASE.mdf is not a primary database file. (Microsoft SQL Server, Error: 5171)” In such circumstances, the database administrators recommend to attach a single file. However, when the user uses sp_attach_single_db Stored Procedures, the user encounters the following error message:

“Server: Msg 5172, Level 16, State 15, Line 1 The header for file path……\.mdf is not a valid database file header. The PageAudit property is incorrect.”

The above issue occurs when the MDF file header gets corrupted or some invalid information is inserted in the header file. All these situations result, inaccessibility of the SQL database. To ensure accessibility of the SQL database, the user needs to recover mdf by using the latest backup. But sometime user has not created any backup of its database or mdf file, then he needs to perform MDF repair. To do so, user needs to use efficient and effective SQL MDF repair application.

Fixing Fatal Table Error in SQL Server Database

2010-02-17T01:18:00.000-08:00

Corruption in MS SQL Server table is mainly caused when the metadata structure of the database gets damaged. Few major causes of metadata structure corruption are improper shutdown of system/database, application malfunction, and malicious software like virus. The data saved in the corrupted table cannot be accessed. For accessing the table records, the database user needs to restore the table from a valid database backup. But if in case, the valid backup does not the desired table, then the user needs to use advanced MDF File Recovery application that can comprehensively repair the table and allow the user to access its records.

To illustrate the above case, consider a scenario where you receive the underneath error message while trying to view a specific table records:

“Table error: Object ID O_ID, index ID I_ID, column 'COLUMN'. The column ID COL_ID is not valid for this table. The valid range is from 1 to MAX_COL_ID.”

The above message appears every time you try to access the table. Additionally, the error message makes the records stored in the table inaccessible.

Cause:

The above error message primarily appears when the metadata for the table consists of a column ID, which is greater than the largest Column ID used in that table. This occurs when the metadata structure is corrupted. The above table error message can occur either due to physical or logical corruption.

Resolution:

Follow the below steps for resolving the table error message and accessing the table records:

To repair the database damaged due to physical damage, you will need to change the damaged component with a new one.
Running DBCC CHECKDB command with appropriate repair clause allows you to repair a logically corrupted database.

However, if the DBCC CHECKDB command fails to resolve your issue, then you will need to download MDF File Recovery application from the Internet. MDF File Recovery software displays all the repairable database component records and allows you to restore the component on your desired location. The repair process is easy to understand as the software comes with an interactive user-documentation.

SQL Recovery Software, a world-wide used master database file recovery software, can recover all SQL database components after any logical corruption scenario. Compatible with SQL Server 2008, 20005, and 2000, the software supports almost all Windows operating systems, including
7, Vista, XP, 2003, 2000 and NT.

Resource Link: http://blogs.siliconindia.com/accessrecovery/Fixing_Fatal_Table_Error_in_SQL_Server_Database-bid-xIz9qt2E76717919.html

Can't Drop a SQL Server Table

2009-12-30T23:20:00.000-08:00

SQL Server database is a collection of tables with typed columns. If due to any cause SQL Server tables get corrupt, you can use DBCC CHECKDB command to examine the extent of corruption. A SQL table gets corrupt due to unexpected shutdown, application bugs, virus attack, network faults and similar other reasons. A corrupt SQL table shows corruption errors or behaves abruptly. However, to restore lost information, you should use your recent backup, if available and valid. In case of no backup or invalid backup state, commercial repair mdf applications can help to repair and restore the damaged database.

One of the typical symptoms that a corrupt SQL Server table shows is that you cannot drop it using DROP TABLE command.

Cause

You cannot drop a corrupt SQL Server table if allocation extent/page is cross-linked or damaged. As a result, SQL Server takes it as some data from other tables in the same extent/pages that belong to the affected object. In such cases, if it allows you to drop the table, it might delete data from other tables.

Solution

To correct the aforementioned behavior, try following these methods:

You can create a new SQL Server database and try copying all objects from affected database. To do so, you can use BCP or Transfer Manager. You then need to dump or rename the databases.
If database is of large size, you can update sysobjects and thus rename the table. After this, create a new database table, leaving the earlier one. Updating sysobjects can corrupt the database more.
If above measures don't give required results, use your recent database backup to restore.
In case of backup unavailability or backup errors, you should use third-party mdf file repair applications.

MDF Repair software are advanced tools that can examine your damaged SQL databases and repair them. Such software come equipped with informative documentation, enhanced repair options, non-destructive design, instinctive repair features and intuitive interface. MDF Recovery software perform powerful scan of damaged database, while maintaining its integrity. These are versatile tools that you can use in any logical case of database corruption.

How to repair MDF files not detached from SQL Server 2000

2009-12-16T01:12:00.000-08:00

If you have an mdf file that was not properly detached from SQL Server 2000 (possibly due to a hard drive crash), the first (best) option is to restore the database from a valid backup. If that is not an option, then you may need to repair mdf before you are able to attach the database.

If you are using SQL Server 2000, the following are instructions on how to repair the mdf file. Replace the filenames with your filename!

1. Make sure you have a copy of eshadata.MDF (or gendata.mdf)
2. Create a new database called fake (default file locations)
3. Stop SQL Service
4. Delete the fake_Data.MDF and copy eshadata.MDF (or gendata.mdf) to where fake_Data.MDF used to be and rename the file to fake_Data.MDF
5. Start SQL Service
6. Database fake will appear as suspect in EM
7. Open Query Analyser and in master database run the following :

sp_configure 'allow updates',1
go
reconfigure with override
go
update sysdatabases set
status=-32768 where dbid=DB_ID('fake')
go
sp_configure 'allow updates',0
go
reconfigure with override
go

This will put the database in emergency recovery mode
8. Stop SQL Service
9. Delete the fake_Log.LDF file
10. Restart SQL Service
11. In QA run the following (with correct path for log)

dbcc rebuild_log('fake','h:\fake_log.ldf')
go
dbcc checkdb('fake') -- to check for errors
go

12. Now we need to rename the files, run the following (make sure there are no connections to it) in Query Analyser (At this stage you can actually access the database so you could use DTS or bcp to move the data to another database .)

use master
go

sp_helpdb 'fake'
go

/* Make a note of the names of the files , you will need them in the next bit of the script to replace datafilename and logfilename - it might be that they have the right names */

sp_renamedb 'fake','eshadata'
go

alter database eshadata
MODIFY FILE(NAME='fake', NEWNAME = 'eshadata')
go

alter database eshadata
MODIFY FILE(NAME='fake_log', NEWNAME = 'eshadata_log')
go

dbcc checkdb('eshadata')
go

sp_dboption 'eshadata','dbo use only','false'
go

use eshadata
go

sp_updatestats
go

13. You should now have a working database. However the log file will be small so it will be worth increasing its size. Unfortunately your files will be called fake_Data.MDF and fake_Log.LDF but you can get round this by detaching the database properly and then renaming the files and reattaching it.
Run the following in QA

sp_detach_db eshadata

--now rename the files then reattach

sp_attach_db 'eshadata','h:\eshadata.mdf','h:\eshadata_log.ldf'

Resource Link: http://www.esha.com/kb/questions/12/

Character Data Corruption In Sql Server And Mdf Recovery

2009-12-02T20:47:00.000-08:00

In MS SQL Server, you use SSMS (SQL Server Management Studio) to query character data from the SQL Server database which uses a non-Unicode data type. For instance, the SQL Server uses the char, varchar or the text data type.

The code page of client computer differ form database code page.

In such circumstances, the character data may be represented inaccurately. For example, you may face any of the subsequent issues:

The characters are represented as the question mark. You might come across this issue if you have inserted or updated character data as non-Unicode data type prior to querying character data. The characters are represented as corrupted. The characters of code page A are stored in non-Unicode column of code page B. Furthermore, the characters are not translated.

In such circumstances, the MDF file becomes inaccessible due to corruption and might lead to the data loss.

This situation occurs as the characters of code page are stored in non-Unicode column of page B. In addition, the characters are not translated properly.

In SQL Server, when you use string literal of non-Unicode data type, the string literal is changed by using the default code page of the database which is derived from collation of the database. Storing the character data of code page in a column of B code page may result into database corruption and data loss.

To stop the database corruption, you may try the following:

Use a Unicode data type in place of non-Unicode data type
Use appropriate collation for SQL database
Use binary or varbinary data type
Use a various tool for storing and accessing data and disable data Translate parameter

These fixes will stop the database corruption but won’t be able to repair the corrupted database. To do so, you need to use MDF recovery software.

“windows Could Not Start The Sql Server” Sql Error

2009-11-30T08:50:00.000-08:00

Sometime you face problem that "Windows could not start the SQL Server ([myinstancename]) on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 10022."

This error message may get generated while dealing with the SQL Server. In this situation, try to bypass Configuration Manager by attempting to start the SQL Server from the Windows Services applet.

You can also start the SQL Server through command prompt. If you get the following error message after running the command then probably you are in big trouble:

“Your SQL Server installation is either corrupt or has been tampered with (Error getting instance ID from name.). Please uninstall and then re-run setup to correct this problem”

Sometime, reinstalling the application may not help, but it affects your database and may corrupt it. The MDF may already be lying in the corrupted state as the installation of SQL Server is damaged. This is the condition when you need to repair MDF file.

You can go through the registry editing way, which is another threat to the SQL database. However, if you expert enough to effectually deal with the registry then locate the following:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

The permission problem may be residing there, so correct it. If this doesn’t help either, then after uninstalling the application, remove all the SQL entries from the registry, if any. Then install the application again. This will clear all the installation related problems of SQL Server.

And for curing the database corruption issues, you require MDF recovery which is feasible through SQL recovery software. This software do MDF repair with the use of efficient scanning algorithms for all the objects of database. Applicable for all the corruption scenarios, this MDF recovery software perform the safe job.

Repair Software For Damaged MDF Files

2009-11-19T02:00:00.000-08:00

All Database Files of Sql server is saved with the extension of .mdf. MDF File contains all your precious data and information. If mdf file get corrupt than you lost your precious data. If you are facing problems while opening your database files and you come across with the following error messages than your Database is said to be corrupt and damaged.

1. MDF is not a primary database file.
2. Windows could not start the Server.
3. Database file is missing and needs to restore.
4. Server can't find the requested database table.

To recover data from corrupted database you need to download the software which can easily repairs your entire degraded Database. You need to 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. If the problem still persist than you need to have mdf recovery software which recovers the stored procedures, rules, constraints, triggers. There is software which is used for the recovery of all damaged Database. This particular software is an excellent and efficient recovery tool for all the users of MS Sql Server.

Main Features of Repair Software.

1. Safe and Complete recovery and repair for corrupted MDF file.
2. Simple user interface.
3. Recovers user defined data types, rules, defaults, indexes and the included database constraints.
4. Also repairs and restores the corrupted tables, views, saved procedures and triggers.
5. Support SQL Server 2000 & 2005.
6. Create script after recovery to save file.

The MDF Repair Software supports repairing of corrupt or damaged data created using SQL Server 2000 and 2005. The Recovery Software fixes errors like unrecognized database format, enter database password, as with this error you do not get the permission to open your files. The Repair Software saves your time and recovers your data easily.

SQL Error: ‘The system cannot self repair this error’

2009-10-08T02:51:00.000-07:00

MS SQL Server database is a set of tables that comprise stored procedures, views, constraints, indexes and transaction log files. Database storage space is basically divided into several pages, which serves as the basic unit of all I/O operation in SQL Server. Each of these pages is assigned 96-byte header that are responsible for holding all meta data information of the page. All the data are stored in MDF files. But sometimes, SQL Server log giving some sort of errors. It indicates that your SQL database is affected and requires restoring from backup. But in case of unavailability of backup, you should use MDF Repair tools, which use powerful file repair algorithms to fix SQL database corruption.

Sometime when you try to access your SQL database, you might receive the similar error message:

Msg 2540, Level 10
The system cannot self repair this error.

It means that your SQL Server has encountered an error that could not be automatically repaired by its check code. Such errors include:

Metadata corruption
Corruption of PFS (page free space)pages
One or more system files corruption
PFS pages holds allocation status of each database page. They record information like whether the page has been allocated for storage or not, the amount of fee space available on each page etc.

Such issues might arise due to hardware issues. To fix 2540 error follow these steps:-

Diagnose your system for hardware issues
Check, all system files are healthy. Reinstall the system, if required.
Restore the database from the recent backup, if present and is valid. If no clean backup is available, run DBCC with repair option. But it can cause data loss as the process deletes the corrupted pages. For safe MDF Recovery, use third-party tools of SQL database recovery.

MDF Reccovery software are appropriate tools to scan and repair damaged SQL Server databases. Using powerful and safe scanning algorithms, they avail effective database recovery.

Repair Corrupted MDF Files With MS SQL Database Repair Software!

2009-09-21T23:52:00.000-07:00

MS SQL is an RDBMS(relational database management system). It is very widely used throughout the world for data managements. This is a Microsoft product that has proved that it is reliable, consistent and fast than other softwares. The MS SQL Database Files uses .MDF file format. If these files get corrupted or lost then you will not be able to access the related data from the database and SQL will give you vulnerable results.

There are various reasons that can corrupt the SQL Server Database file (.mdf) corruption. Some of them are:

1. Abnormal termination of server computer.
2. Defects and problems in Server, especially in the Hard Drives, disk controllers, main memory, cache or in Raid Controllers
3. Incorrect String to multi-client database with user(s)
4. Trying to access or copy the file while the server is running
5. Disk space does not free when database is working
6. Exceeded the size restriction of database file

Due to these reasons database objects like Tables, Views, Stored Procedures, Triggers and other elements of database will get corrupted. In such situation you need to use any professional mdf recovery software. MDF Repair is one of these kinds.

MDF Repair is a database recovery tool that is used to repair damaged primary keys, unique keys, candidate keys, Indexes, Foreign Keys and all other elements of SQL Server. It creates a database rebuilding batch file that helps recreating the SQL Database and then the user can use it. The software is loaded with rich and powerful searching engines that is fast and gives accurate recovery results. It can handle almost all kind of major corruptions that may occur in the .MDF files.

MDF Corruption Due To Unexpected Growing of Transaction Log File

2009-09-14T22:19:00.000-07:00

In MS SQL Server, database contains one data file and transaction log file. Microsoft SQL Server stores data physically into data file. The transaction log file holds the details of all the alterations that you perform on the SQL Server database and also the details of all the transactions which are performed in every alteration because transactional integrity is considered as a fundamental and intrinsic feature of the Microsoft SQL Server, logging the details of the alterations and transaction can not be turned off in the SQL Server.

The log files of Microsoft SQL server is logically divided into several smaller segments, which are known as virtual log files. The SQL Server transaction log growth can be governed by user or can be constructed to use the entire disk space available. Any alteration that MS SQL Server makes to the size of transaction log file, like truncating the transaction log file or increasing the number of transaction log files, are done in units of the virtual log file.

If the transaction log file, which communicates to the SQL Server database, is filled and you have set the selection for the transaction log file to cultivate automatically, then it grows in units of the virtual log files.

Sometime, the transaction log file might become extremely large and you might run out of the hard disk space. When the transaction log file increases until the log file uses the entire available disk space and can not enlarge any more, you can not perform any alteration operation on the database. Furthermore, the SQL Server database becomes inconsistent and gets damaged. Thus, it becomes very important to repair the damaged SQL Server database as soon as possible.

The SQL recovery is possible with the help of third party applications known as MDF recovery software. MDF recovery software are the fully automated SQL repair software which are able to repair mdf file in all possible cases of corruption. MDF recovery software are the fully programmed tools which performs thorough scan of the corrupted MDF file and carry out a complete MDF recovery.

MDF Header File Corruption and SQL Recovery

2009-09-07T21:51:00.000-07:00

The header file is the collection of relevant information, whose corruption make the file inaccessible. Even for the MDF file, which is the prime storage area of data for SQL Server, the header corruption can happen with regard of many reasons ranging from virus attack to application faults. The condition is peculiar and hard to digest for the database administrator.

However, in such situation, you may get error messages like the following:

“The file header is corrupted and is not a valid database file”
Or
“Msg 5172, Level 16, State 15, Line 1

The header for file 'D:\DbName\DbFileName.mdf' is not a valid database file header. The property is incorrect.”

Generally these error messages occur when the user tries to attach the MDF file to SQL Server.

In this situation you can try out attaching the file by some other methods, instead of trying it directly. Create the similar database and then exchange the corrupt files after shutting down the SQL service. After this, you can try to extract all the valuable information from the database by putting it into the emergency mode.

If you didn’t get the desired results as you are expecting then look for the SQL repair solutions to get the valuable information back. This is quite good if you have the proper backup of the database as this would be the SQL recovery cure without the assistance of external help. However, who don’t have the backup, MDF recovery tools are here to help you out.

These MDF repair software have power to scan the corrupted database with much efficiency and efficient scanning algorithms.

MS SQL Database Error

2009-08-30T21:45:00.000-07:00

Database plays a very important role for any Business System. MS SQL Database is one of the database where we can store all our important data. Most of the business organization lies on MS SQL Database Server for storing there valuable and important data by considering its reliability, highest level of security, and scalability. Because of its large memory capacity we can store voluminous amount of data in MS SQL Database. We can store our data in this database and can see or retrieve it in the future depending upon our need or use.

Many times when we try to access our data from database it display an error message and you are not able to get access to the database. It happens because the database has gone corrupt or damaged because of virus attack, improper system shutdown, malfunction error and so on.

Some of the commonly displayed error messages are:

Database corruption error
Table handler giving error
Cannot locate the database
Database is corrupt
Cannot open the desired database
File has crashed
Table error

In this situation, use your backup to restore your data. In case, you don’t have any backup or no clean backup is available, scan the damaged SQL Server database using commercial MDF Repair products. These software repairs your corrupt database by using certain sophisticated algorithm and flowchart. It first locates the corrupt database files and then repair them. After doing the repair work, you can once again get access to your files and folders in MS SQL database like the way you used to do it earlier.

Error 3414 in SQL Server

2009-08-25T04:49:00.000-07:00

MS SQL server is used to create web-based and enterprise database systems. The primary languages it uses are ANSI-SQL and T-SQL. The main unit of storage in SQL Server is database, which is basically a collection of tables. These databases might get corrupt due to several reasons, varying from unexpected shutdown to application, faults or virus infection and so on. Thus, it's always recommended to ensure that you have a valid and updated backup of your database. Otherwise during database corruption, MDF Recovery applications can restore the original database.

Sometime you might receive an error message with your SQL Server database that is similar to the following:

Error 3414, Severity Level 10

Database '%.*s' (dbid %d): Recovery failed. Check the SQL Server errorlog for further information as to the cause.

This is the SQL Server startup error. As specified in the error message, it occurs when SQL Server fails to recover listed database from suspect state. You cannot continue working with the database until the cause of error message is fixed. The database remains in suspect state.

You should consider following these steps to recover from such situations:

· First examine SQL Server log for error that might have occurred before error 3414 could occur. This should be performed at first occurrence of error 3414. It could occur due to faulty controller, disk problems, misbehaving antivirus application and other such issues.

· If you don’t find any information regarding the responsible issues, restore from the last clean backup you have.

· In case, you don’t have any backup or no clean backup is available, scan the damaged SQL Server database using commercial MDF Repair products.

MDF Recovery software are the tools that could diagnose a damaged SQL Server database and perform safe and effective repair. Besides standard file repair applications, these software give you automated recovery features, file repair power in all cases of database corruption.

Error 8934 in SQL Server

2009-08-11T00:21:00.000-07:00

SQL Server DBCC CHECKDB command is the database check command that is used to scan the database and its objects for examining their physical and logical integrity. If you face error after running this command, it implies database corruption. In such situations, you need to restore from backup. However, if no backup is present, you should use MDF Repair applications.

Run alter table command on database to change a column that is not null to null. You encounter erroneous results or the database becomes unavailable, marking error 644 in SQL Server error log. After this, when you run DBCC CHECKDB command to check database consistency, the following corruption error is displayed:

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>= key value in the parent (1:75) slot 2.

The above issues are observed is specific to SQL Server 2000 columns is a clustered index key.

Cause

· Column status synchronization issues between sysindexes system table and syscolumns system table
· Column is a clustered index key that is null

SQL Server fails to perform correct modification and results corruption.

Solution

To fix these errors, try these steps:

· Run DBCC DBREINDEX or DBCC CHECKTABLE command with REPAIR_REBUILD option
· Try running ALTER TABLE command to change the column from not null to null
· Check database consistency using DBCC CHECKDB command. If it reports corruption, use REPAIR_ALLOW_DATA_LOSS option. But it causes data loss, so it is safe to use commercial MDF Recovery applications. These are read-only applications that scan damaged SQL databases and restore them with original content and view. These software provides self-descriptive interface and restores all database objects including tables, user defined data types and functions, triggers, stored procedures, views, rules etc. These MDF Repair software is compatible with Windows Vista, XP, 2003, 2000, and NT.

MDF Restoration fails Due to File Version Conflict

2009-08-03T03:49:00.000-07:00

MS SQL Sever does not permit to repair from a backup which was created on SQL Server file version that is different from one on which you are trying to restore. When you try to repair, in such situations you may get the following error message:

“Server: Msg 3168, Level 16, State 1, Line 1
The backup of the system database on device d:\temp\master.bak cannot be restored because it was created by a different version of the server (134217904) than this server (134217920).
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.”

After this error message, the process get stop.

Reasons of the trouble

This problem may arise if the database schema of the system has been changed. This change leads to the file system conflict for the SQL Server. Thus, the database schema causes inconsistency. This process is resulted due to the file version mismatch. After this error message, you can not repair your damaged database from backup and may get in serious trouble. It is the worst situation for database administrator or an organization.

Resolution

To work on this problem, you need to install the same file version of SQL Server as it is in the backup system. This will evade the file version mismatch and finally database inconsistency and file version conflict like problems. Though, it works in most of the cases, but upgrading or degrading the file version of any application could make the circumstances worse. Your MDF file may get damaged further and may become completely permanent. In such cases, you need to use third party SQL recovery software to carry out MDF recovery.

SQL recovery software is a user-friendly application, which is specifically designed to repair and restore the damaged or corrupted MDF files. mdf recovery software is applicable to each case of MDF corruption. Use powerful and trustworthy SQL recovery software to make sure that the recovery should be perfect and safe.

Stellar Phoenix SQL Database Recovery software is the best and highly developed SQL recovery software, able to handle every MDF corruption problems. With easy user interface, it is very simple to achieve mdf repair with this SQL repair software.

Database Inconsistency and Invalid File Header Problems in Mdf

2009-07-19T21:40:00.000-07:00

RAID servers are considered as the most trusted and dependable storage medium. But sometimes, they may also lose all the hard drives, which hold important data, backups and other files.

Most of the organizations use RAID for storing their important SQL Server databases. When they fail, you may lose all of your data.

In such situations, you can save your data by restoring the database from your backup. But sometime, when you try to restore backups, you may receive the following error message:

“Msg 3270, Level 0, Sev 16.

An internal consistency error occurred. Contact Technical Support for assistance.”

In this case, when you attempt to detach the database using sp_detach_db stored procedure and then attempt to attach the database again with the help of sp_attach_db stored procedure, you may get the flowing error message:

“Server: Msg 5172, Level 16, State 15, Line 1.

The header for file ‘d:\pubs.mdf' is not a valid database file header. The PageAudit property is incorrect.”

After this error message, the restoration process gets halted and you are not able to access anything from your SQL Server database.

Grounds of the trouble

As affirmed in the above error messages, the problem is either due to inconsistent state of the database or due to invalid header entry for the database. In both of these cases, the database may get corrupted and you are not able to access even a single data from it.

In such situations, you need to perform SQL recovery to repair the damaged database and retrieve all of your data from it. SQL recovery can be carried out using the SQL Database recovery software.

SQL Database recovery software are easy to use, which allow you to have quick and trouble-free MDF repair in each and every case of MDF corruption. To ensure complete and successful SQL repair, always use effective SQL database recovery software like Stellar Phoenix SQL Database Recovery software.

Master Database Corruption Of SQL

2009-07-13T21:49:00.000-07:00

The installation of MS SQL Server is composed of several databases, each which hold its own importance. Master database, TEMPDB, Model database, these are few of them. But the most important one is Master database.

The Master database is the one which is responsible for carrying information like pointers to the other databases, login accounts and so on. This comprises of the system catalogs to maintain the data like system wide configuration settings, disk space, other database existence information, file allocations and other similar and so is the most important part of the SQL Server installation. Without this file, the starting up of the server is practically impossible. The file extension of this file is mdf.

In few of the cases for users, this becomes hard to resist that the master database is corrupt. The improper backup of the same add to the grief of the user and create the need of SQL recovery. There are number of reasons for the database corruption like improper shutdown of system, virus attack etc. and strangely, some of the reports also state that the bulk use of DELETE from a table makes it corrupt.

If the master database is corrupt, then surely others also do have the problems and thus the need of MDF recovery comes to an immediate. However you can try out to rebuild it with rebuild.exe and restore it.

But, if in any case, this procedure doesn’t work properly, then you need to use the third party MDF Repair software. Also in complete success scene of rebuilding the master database, the other databases may be lying in the corrupted state for which again these SQL recovery software are needed.

These software have the magnificent ability to run the scanning mechanism to repair and restore the MDF file. The software uses the powerful scanning algorithms to give the stupendous results. They can benefit you with complete MDF recovery in each and every instance of corruption with the instinctive user interface.

You can have safe SQL recovery with their read-only nature. These MDF recovery utilities are applicable for all the objects of database. With the interactive user interface, this SQL recovery tool eases the users. You can use it for SQL Server 2000.

Software For Recovering Damaged Mdf Files

2009-07-06T22:43:00.000-07:00

Database plays a very important role for any Business System. Most of the business organization lies on MS SQL Database Server for storing there valuable and important data by considering its reliability, highest level of security, and scalability. Sometimes when you try to open SQL database file, you face various error messages which mean that your SQL Database file (.mdf) has got corrupted. There may be great chances of losing some part or whole important document. Data loss situation and Corruption occur due to virus attacks, unexpected system shutdown, media corruption, application corruption and any other reasons. This arise the need of MS SQL Database Recovery to save the important data from corrupted mdf file.

The mdf Repair Software is a perfect tool to recovers, repair and restore corrupted and damaged mdf file including deleted records, partly damaged records which get saved in separate batch files. The software thoroughly scans the whole database for the recovery of deleted database file and creates script files after SQL recovery. The mdf repair is easy to use database repair software with advance searching algorithms. It is very safe and simple to use this software. You will not feel any problem at the time when you use this software. After recovery it displayed all the repaired files in tree like structure. It also creates the scripts files which shows where the recovered files are saved. Whatever the reasons for the corruption of your SQL database, it doesn’t affect software in recovery process. It is efficient is recovery of corruption issues.

Some of the features of SQL recovery tool are—

Supports SQL Server 2000 and SQL Server 2005.
It can repairs large sized SQL database successfully.
Repairs and restores database constraints and indexes.
Repair damaged tables, views, stored procedures, and triggers.
Quick and complete repair and recovery of MS SQL database from MS SQL Server.
Also recover and repair predefined defaults, rules, default values, user data types and checks.

Mdf Repair tool is a great tool for recovering the damaged files database.

SQL Server startup error - “Error – 3414”

2009-06-24T23:45:00.000-07:00

MS SQL server is the most well-liked application used to create web-based and enterprise database systems. The primary languages it uses are ANSI-SQL and T-SQL. The main storage unit in SQL Server is database, which is mainly a collection of tables. These databases might get corrupt due to several reasons as unexpected shutdown to application, unexpected system shutdown and virus infection. Thus, it is always suggested to ensure that you have a valid and updated backup of your SQL Server database. In other cases when you don’t find backup as valid or existent while database corruption, then you need the MDF Recovery applications that can restore the original database.

You might receive an error message with your SQL Server database that is similar to the following:

Error 3414, Severity Level 10

Database '%.*s' (dbid %d): Recovery failed. Check the SQL Server errorlog for further information as to the cause.

This is the SQL Server startup error.

Cause

As specified in the error message, it occurs when SQL Server fails to recover listed database from suspect state. You cannot continue working with the database until the cause of error message is fixed. The database remains in suspect state.

Resolution

You should consider following these steps to recover data from such situations:

You need to first observe SQL Server log for error that might have occurred before error 3414 could occur. This should be performed at first occurrence of error 3414. It could occur due to damaged controller, antivirus application, disk problems and other such issues.
If you don’t find any information regarding the responsible issues, restore from the last clean backup you have.
In case, you don’t have any backup or no clean backup is available, scan the damaged SQL Server database using commercial MDF Repair products.

MDF Recovery software analyze damaged SQL Server database and perform harmless and successful repair. Besides standard file repair applications, these software give you automated recovery features, file repair power in all cases of database corruption, read-only design, to-the-point documentation, graphically rich user interface and other advanced features.

Can’t Drop a SQL Server Table

2009-06-17T23:35:00.000-07:00

SQL Server database is a collection of tables with typed columns. If due to any reason database tables get corrupt, you can use DBCC CHECKDB command to observe the amount of corruption. A SQL table gets corrupt due to unexpected shutdown, application bugs, virus attack, network faults and similar other reasons. However, to restore lost data, use your recent backup, if available and valid. In case of no backup or invalid backup, commercial MDF Repair applications can help you to repair and restore the damaged database.

One of the typical symptoms that a corrupt SQL Server table shows is that you cannot drop it using DROP TABLE command.

Cause

You cannot drop a corrupt SQL Server table if allocation page is cross-linked. As a result, SQL Server takes it as some data from other tables in the same extent that belong to the affected object. In such cases, if it allows you to drop the table, it might delete data from other tables.

Solution

To correct the abovementioned behavior, try following these methods:

Create a new SQL Server database and try copying all objects from affected database. To do so, use BCP or Transfer Manager. You then need to dump or rename the databases.
If database is large in size, you can update sysobjects and thus rename the table. After this, create a new database table, leaving the earlier one. Updating sysobjects can corrupt the database more.
If above measures don’t give required results, use your recent database backup to restore.
In case of backup unavailability or backup errors, use third-party MDF Recovery applications.

MDF Repair software are advanced tools that can examine your damaged SQL databases and repair them. Such software’s are well prepared with informative documentation, enhanced repair options, non-destructive design, and automatic repair feature. MDF Recovery software perform powerful scan of damaged SQL Server database, while maintaining its integrity. These are flexible tools that you can use in any logical case of database corruption.

Repair and Recover MDF File

2009-06-10T21:50:00.000-07:00

The SQL server Database Files is saved with the extension name of .mdf file (Master Database File). If you initiate that your database files are not accessing and moreover you are unable to open your mdf files than your files are found to be damaged or corrupted. In case of MDF corruption, you may face any of the given error messages:-

1. “Windows could not start the SQL Server”

2. “MDF is not a primary database file”

3. “Server can’t find the requested database table”

4. “Database Can’t Be Accessed”

5. “The file *.mdf is missing and needs to restore”

6. “The execution of a full-text query failed”.

If these error messages appear than its mean that mdf file is corrupted, then you need mdf repair to repair your corrupt and damaged file. SQL database file gets corrupted due to unexpected system shutdown, unable to boot, invalid database file headers, internal program errors, accidental deletion of data and files, Virus attacks etc. Stellar Phoenix SQL Database Recovery software uses well-known algorithm which performs a deep and broad scan of the damaged mdf file so as to retrieve each and every outline of data. MDF repair software repairs corrupted mdf file and recover table, views, stored procedures, rules and triggers from MS SQL Server effectively. There are many mdf Repair Software which scans your damage mdf files.

An efficient SQL repair and recovery tool not only repair and recovers corrupt or damaged .mdf files but also repairs the entire data base without creating any bound regarding the size of the database. No matter whether the user is technically sound or not, proper guidelines and support is provided by such service providers. The mdf Repair Software is a powerful software tool that recover your data as much as possible, so to minimize the loss in file corruption and for making your organizational or personal operations productive.

Data Corruption in SQL Server and MDF Recovery

2009-06-03T23:26:00.000-07:00

In MS SQL Server, you use SQL Server Management Studio (SSMS) to query character data from the database which uses non-Unicode data type. For example, the SQL Server uses the char, varchar or the text data type.

The code page of client computer differs from code page of database. In such situation, the character data may be represented incorrectly. For instance, you may face any of the following issues:

The characters are represented as the question mark. You may come across this matter if you have updated character data as non-Unicode data type earlier to querying character data.

The characters are represented as corrupted. The characters of code page X are stored in code page Y in non-Unicode column. Furthermore, the characters are not translated.

In such circumstances, the MDF file gets corrupted and they are not accessible and might lead to data loss.

Reasons of the trouble:

This breakdown occurs as characters of code page are stored in non-Unicode column of page B. In addition, the characters are not translated properly.

When using the string literal of non-Unicode data type in SQL Server, the string literal is changed by using the default code page of the database. Storing the character data of code page in a column of Y code page might result into database corruption and data loss.

Resolution:

To prevent database corruption and work around this issue, you may try the following:

Use binary or varbinary data type
Use appropriate collation for SQL database
Use a Unicode data type in place of non-Unicode data type
Use a diverse tool for storing and accessing data and disable data Translate parameter

These fixes will stop the database corruption but won’t be able to repair the corrupted database. To repair the corrupted database you need to use SQL recovery software.

Stellar Phoenix SQL database recovery software is the wonderful MDF repair software that uses the most powerful scanning mechanism for SQL repair. The user interface of this SQL recovery software is enormously interactive and effortless and doesn’t need any sound technical knowledge to carry out MDF recovery.

Logical Inconsistency Corrupt MDF File

2009-05-28T22:00:00.000-07:00

Logical inconsistency in database can lead to SQL Server database corruption. It normally affects your valuable and precious data by making it inaccessible and results as data loss. All database applications related to back-end and front-end roles of the SQL Server database get halted.

Sometime, when you try to open your SQL Server database (MDF file), you might encounter the following error message:

“Error: 824, Severity: 24, State: 2.

SQL Server detect a logical consistency-based I/O error: incorrect pageid (expected 1:1863; actual 0:96). It occurred during a read of page (1:1863) in database ID 4 at offset 0×00000000e8e000 in file ‘F: MSSQL.1MSSQLDATAMSDBData.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.”

After this error message, when you run DBCC CHECKDB command to check and fix your database inconsistency problems, you might come across additional error message stating:

“Msg 945, Level 14, State 2, Line 1

Database ‘magirisilica_s24′ cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server error log for details.”

This action of SQL Server causes data inaccessibility and data loss. To overcome this problem, you need to know the cause of this problem.

Root of this issue

You might meet data detachment and database contradiction problem due to MDF file corruption. Such corruption could be the result of issues like hardware problems, file system errors, application malfunction and improper system shutdown.

Resolution

To sort out this problem, you need to opt for MDF recovery. It is the process of systematically scanning the damaged MDF file and extracting best possible amount of data from it.

It can be performed with the help of SQL Database Recovery software. These are highly automated tools that arrange efficient scanning methods to retrieve your data from damaged database file.

Error During Upgrading From MSSQL 2000 to MSSQL 2005

2009-05-20T21:56:00.000-07:00

MS SQL Server is not an application that Microsoft updates very often. Thus when they release any update, it has the high possibility to be momentous. As such, there are several changes that you should understand and know before upgrading from MSSQL 2000 to MSSQL 2005.

Upgrading from MSSQL 2000 to MSSQL 2005 isn’t a project to be taken lightly. An upgrade of such scale takes some careful preparation. The SQL Server Upgrade Advisor helps you in analyzing the system and creates a report identifying the issues which requires being addressed pre and post upgrading.

Data, agent jobs, Data Transformation Services packages, failover clustering setup, replication setup, full text search objects, Analysis Services objects, Reporting Services configuration, Notification Services configuration and so on would have to be migrated.

Before beginning the upgrade process, check whether the needed software and hardware are available. Read backward compatibility notes and make required changes to the scripts and application. The Upgrade Advisor tool should be run and all the issues highlighted for solving should be addressed.

Once all above things have been done, the SQL Server 2005 setup has to be started and the instance installed. Subsequently, move user database to instance by using the backup and restore or detach and attach functionalities of MSSQL 2005. Then register the server, repopulate the full text catalogs, update statistics and then run Surface Area Configuration tool.

After successfully upgrading from MSSQL 2000 to MSSQL 2005, you will be able to use all of the advanced features of SQL Server 2005 and the database created on SQL Server 2000. It is very easy to configure MSSQL 2005 and use it.

Unluckily, sometimes when you attempt to upgrade, the upgrade fails with some sort of error messages and may leave your MDF file in corrupted state. In such situations, if you haven’t made proper backup, you may fall in big trouble and the situation may lead your business to destruction.

In such situations, the only thing which can save you and your business is MDF recovery. MDF recovery is the way to repair and restore the damaged database and extract data from it. It is a very easy process and works in all situations of MDF corruption.

MDF recovery is possible with the help of third party applications known as SQL recovery software. Good quality MDF recovery software, like Stellar Phoenix SQL Database Recovery, can make the situation completely in your support and can restore all of the MDF database objects.

Recover Data When MDF file get corrupted

2009-04-28T01:01:00.000-07:00

The data loss is a panic situation that generally occurs without any warning or information. It can damage or corrupt our database stored on our hard drives. The database may be corrupted due to application failure, media read errors, improper system shutdown and virus attack and many other reasons. In such case you need to use the database recovery software to recover and repair the corrupted database. In case of MDF corruption, you may face any of the given error messages:-

1. “Windows could not start the SQL Server”
2. “MDF is not a primary database file”
3. “Server can’t find the requested database table”
4. “Database Can’t Be Accessed”
5. “The file *.mdf is missing and needs to restore”
6. “The execution of a full-text query failed”.

The loss of MDF file means loss of database and its means loss of critical information. To recover the database you need to use the MDF Recovery software. An efficient SQL repair and recovery tool not only repair and recovers corrupt or damaged .mdf files but also repairs the entire data base without creating any perimeter regarding the size of the database. The mdf Repair Software recover your data as much as possible, so to minimize the loss in file corruption and for making your organizational or personal operations productive.

For More Information Regarding Software Visit:

http://www.repairmdf.com/
http://www.repair-mssql-database.com/

MDF Corruption Due To Errors in SQL Query Analyzer

2009-04-13T04:54:00.000-07:00

SQL Server Query Analyzer is the most significant object of the SQL Server. It is the main interface for perform SQL queries against the MDF file. You could make use of SQL Query Analyzer for creating and running SQL scripts or you could create scripts and save them for later use.SQL Server Query Analyzer is the most significant object of the SQL Server. It is the main interface for perform SQL queries against the MDF file. You could make use of SQL Query Analyzer for creating and running SQL scripts or you could create scripts and save them for later use.

It is the most significant tool for running ad hoc queries and executing SQL statements. But, at times when you try to setup Query Analyzer or try to implement any statement through this tool, you may receive the following error message:

“Select * from table1
server: msg 823, level 24, state 2, line 1
I/O error (bad page ID) detected during read at offset 0x00000007b7e000 in file dbname.mdf”

In such circumstances, the database administrators recommend to set the database in single user mode and try DBCC CHECKDB by repair_allow_data_loss option. But as you do this, you may get another error message stating:

“Msg 8966, level 16, state 1, line 1
could not read and latch page (1:15807) with latch type SH. sysindexes failed.”

When you apply DBCC CHECKTABLE on the sysindexes table with similar options, you may also find an error message similar to the following:

“Msg 8966, level 16, state 1, line 1
table error: object id 0, indexed 0, page ID (1:15807) the page id in the page header are corrupt= (0:0)”

Reason
These problems may arise if the sysindex or sysindexkeys of the sql server database are damaged or corrupted. The sysindex is the main object of the database and contains information on keys or columns in an index. The sysindex holds information of columns and rows of database table. Because of the corruption in these objects, the mdf file also gets corrupt and become totally in accessible. It could lead to the terrible data loss. But you don’t have to panic because this situation has a cure through the mdf recovery.

MDF recovery can be solved out by using the great and powerful SQL recovery software like Stellar Phoenix SQL Database. It is the most powerful MDF repair software which carries out crucial SQL repair quickly and without any trouble. You can use this MDF repair software in all problems of data loss. Stellar Phoenix SQL recovery software can carry out mdf repair for all of the database objects including tables, reports, forms, macros, triggers, stored procedures, defaults and many alike. This vigorous SQL repair software is useful with MS SQL Server 2000 and 2005.

“Select * from table1
server: msg 823, level 24, state 2, line 1

I/O error (bad page ID) detected during read at offset 0x00000007b7e000 in file dbname.mdf”

In such circumstances, the database administrators recommend to set the database in single user mode and try DBCC CHECKDB by repair_allow_data_loss option. But as you do this, you may get another error message stating:

“Msg 8966, level 16, state 1, line 1
could not read and latch page (1:15807) with latch type SH. sysindexes failed.”

When you apply DBCC CHECKTABLE on the sysindexes table with similar options, you may also find an error message similar to the following:

“Msg 8966, level 16, state 1, line 1
table error: object id 0, indexed 0, page ID (1:15807) the page id in the page header are corrupt= (0:0)”

Reason

These problems may arise if the sysindex or sysindexkeys of the sql server database are damaged or corrupted. The sysindex is the main object of the database and contains information on keys or columns in an index. The sysindex holds information of columns and rows of database table. Because of the corruption in these objects, the mdf file also gets corrupt and become totally in accessible. It could lead to the terrible data loss. But you don’t have to panic because this situation has a cure through the mdf recovery.

MDF recovery can be solved out by using the great and powerful SQL recovery software like Stellar Phoenix SQL Database. It is the most powerful MDF repair software which carries out crucial SQL repair quickly and without any trouble. You can use this MDF repair software in all problems of data loss. Stellar Phoenix SQL recovery software can carry out mdf repair for all of the database objects including tables, reports, forms, macros, triggers, stored procedures, defaults and many alike. This vigorous SQL repair software is useful with MS SQL Server 2000 and 2005.