How to transfer SQL database from one server to another??

I have found an interesting topic in the morning that discussed about “how to backup the database from one server to another ?”. We all want our database will always safe and corruption free. In this modern tech era every databases are very pron to the corruption. As database administrator our main task is maintain the our database safe and high availability for the users. A SQL server database got corrupted or damaged by the several reasons like metadata structure corruption, virus attack, human errors, hardware related issues and many more. In the case of corruption we can restore our database from the secondary server thats why we want to transfer our SQL database from one server to another. But it is very expensive because we will have to maintain the both servers. Most of the companies or organizations prefer their database safe rather that expenses. Microsoft provides several options from transferring SQL database from one server to another server, which are given below:

• Log Shipping
• Database Mirroring
• Snapshot Replication

Log Shipping: In this method you can not perform any operation on the database that is on secondary server. If you want your secondary database to be accessible then you will have to backup, copy the SQL server database on the network and restore from there.

Database Mirroring: In this methods also you can not perform any operation on the secondary server. It just create the copy of your SQL server database. You can use the second database in any corruption on the primary database.

Snapshot replication: If you want to transfer your database from one server to another server on the regular basis then this method is very helpful and effective. This method does not slow the SQL server performance.

At last you can also use database copy tool for the transferring SQL server database from one server to another server.

Note: The main motive behind this transferring operation is recover MS SQL database if any corruption happens at the primary database.

»»  Read More...

How to Resolve Error Message 2522 In SQL Server Database

An index is a data structure that reduced the accessing time on a database table and increased the storage space. A record in the table can be easily retried by the using of index. It is created by the using of one or more column of the database table. Both table and index of database table required nearly same space to store. Sometime the index of database table gets corrupted by inserting the wrong value that results, the database will be inaccessible. For fixing this problem a database administrator should use an advanced third party SQL Recovery application.

Consider a practical scenario wherein, you are inserting some value to access the record and got an error message:

“Unable to process index I_NAME of table O_NAME because filegroup F_NAME is invalid”

Root Cause of the Problem:

The root cause of above problem is that one of the file group IDs saved in meta data for indexes do not exist, thats the index cannot be checked.

Way to Resolve: For resolving the above error message, you have to follow the given below steps:

Check Hardware failure: Run hardware diagnostics and correct the problem if any. After fixing the problem, if you have persistent SQL server database corruption then try to swap out different hardware and fix the problem.

Restore From Backup: If the above problem is not hardware related and you are still unable to access the database then restore the corrupted SQL database from clean and updated backup.

Run DBCC CKECKDB Command: If you have no any clean backup then run DBCC CHECKDB command without repair clause to check the extent of corruption. Again run the DBCC CHECKDB command with proper repair clause and isolate the problem.

After trying all the above steps and database corruption is persistent then you should try a third party SQL Server Recovery software to isolate the problem. These third party SQL recovery application are very effective for repair the indexes of SQL server databa

Add caption
se.

Note: Always try demo version of any software before complete download.

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.

»»  Read More...

How to resolve error 2812 in MS SQL server 2000

Stored procedure is used for the accessing data in the RDBMs like SQL server. It can accept or return value if required. You can store a group of statements in SQL server database by the using stored procedure. As discussed above, stored procedure returns value. Sometimes when you want to get some value by executing stored procedure and got an error message that means you have entered a value that does not exist that make sql server database unable to access. A database administrator should use a third party sql server recovery software to fix the problem.

Consider a practical scenario wherein, you attempt to execute a stored procedure that does not exist and got an error message:

“Could not find stored procedure '%.*ls'”

Cause of Error: The cause of above error message is that you have entered a value which is not exist or you have not fully qualify the stored procedure name.

Way to resolve: if you do not know, who is the the owner of procedure then run this command without any parameter to specify the owner:
sp_help
Run the below command to know list of procedure in the database and owner of all procedure:
USE master
GO
SELECT name,owner = USER_NAME(uid)
FROM sysobjects
WHERE type = 'P'
GO
if the procedure does not appear in the output of above query then, the procedure is either does not exist or in the another database. You can avoid the above error by fully qualifying the stored procedure name with sql server database name.

Sometimes, the name of stored procedure exist in the database but does not return any value that means there is a corruption in the stored procedure of sql server database. A database administrator can resolve this problem by restoring the database from updated backup. If backup is not updated then should use an advanced third party sql recovery application to resolve the problem.

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.

»»  Read More...

How to Resolve Error 5171 in Microsoft SQL Server Database

Most of the companies use Microsoft SQL server database for storing their database where database administrator handle all the issue for maintaining the database by the use appropriate SQL server commands. Microsoft SQL server database may be corrupted by Improper system shutdown, hardware failure, SQL Server malfunctioning, virus infection, hardware failure and many more. Once SQL server database gets damaged, the data stored in the SQL Server become inaccessible. In such scenarios, use latest and updated backup, if backup is not updated, then database administrator needs to used a third party MS SQL database recovery software to repair mdf file.

Consider a situation, wherein a database administrator is working on SQL Server database and creating a report. While doing this, the Windows automatically restarts due to power failure. When database administrator restart the system, the SQL server database becomes inaccessible. When the database administrator tries to attach MDF manually, he encounters the given 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 situations, most the database expert recommend to attach a single file. However, when the database administrator uses sp_attach_single_db Stored Procedures, the database administrator encounters the given below 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 problem generally occurs when the Master database file header gets damaged/corrupted or some invalid value is inserted in the master database header file. All of these situations became, inaccessibility of the SQL server database. To accessibility of the SQL server database, the database administrator needs to recover mdf by using the updated backup. But sometime database administrator has not created any backup of its SQL server database, then he needs to perform MDF file repair. To do so, database administrator needs to use an effective and efficient SQL recovery application.

Most of the database experts recommend Stellar Phoenix SQL Recovery software to repair the corrupted mdf file. This software uses an advanced scanning algorithm to repair and recover corrupted mdf file. It is compatible with SQL server 2008, 2005, 2000, and 7.0

Related article is available here: How to restore MSSQL error 5171 

»»  Read More...

How to overcome Error 8921 in MS SQL Server 2000 database

In MS SQL Server, the CHECKTABLE command is used to check the integrity of the database tables. To do this, it uses several parameters to perform different types of checks. However, if the table is corrupt then this command may not work and exit abruptly. Such database corruption may cause because of several issues including virus infections, hardware malfunctioning, etc. These cases can well be solved using appropriate corrective measures failing which you should use a third-party MS SQL repair software to do the needful.

Consider a scenario in which you are running the CHECKTABLE tool on a database in MS SQL Server 2000. However, the tool fails to execute and exits abruptly showing the following error message.

"CHECKTABLE terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors."

Cause:

The reason behind the failing of CHECKTABLE is that the internal query that DBCC uses to acquire parallelism and scalability due to some miscellaneous reason such as database corruption.

Resolution:

The database corruption can be handled using the following MDF repair methods:


Address hardware corruption issues: You should check if the issues is not being caused due to hardware malfunctioning. You can use the following measures to find out and resolve such issues:

Running hardware diagnostics and fixing any errors that occur while doing so.
Checking Windows application log and MS SQL Server Error log to see whether some error has appeared because of hardware corruption. Try to correct the problem, if possible.
Swapping the hardware components to try and isolate the exact reason of database corruption.
Reinstalling the operating system after formatting the hard disks.


Restore from backup: If the hardware components are perfectly in place, then you should check the state of the database backup. If the backup is clean and updated, then you can restore the database from the backup.

Run DBCC CHECKDB: If the backup solution is not possible, then run DBCC CHECKDB with the appropriate repair clause to repair MDF file.

If the aforementioned methods are unable to resolve the issue, then you should use a third-party MDF file repair software. These database repair tools are extremely safe to use that do not damage the existing while performing SQL repair.

The best SQL database recovery tool that repairs SQL database in most occasions is Stellar Phoenix SQL Data Recovery in MS SQL Server 2008, 2005, 2000, and 7.0. Able to recover various SQL objects including collations, NDF files, tables, stored procedures, triggers, etc, this .MDF repair software is compatible with Windows 7, Server 2008, Vista, Server 2003, XP, and 2000.

Resource taken from here: http://goarticles.com/article/How-to-overcome-Error-8921-in-MS-SQL-Server-2000-database/3838582

»»  Read More...

Repairing Error 8926 to Fix Table Corruption Issues in MS SQL Server 2000 Database

Are you getting a table related error in MS SQL Server 2000? In all probability, it may have happened because of incorrect page definitions on the database. Such database corruption can be caused because of several reasons such as abrupt or improper system shutdown when the database is open, virus infections, etc. You should repair MDF file using any suitable method failing which you should use a third-party SQL repair software to repair SQL database.

Let us take a practical example in which you are getting the following error message while working on an MS SQL Server 2000 database:

"Table error: Cross object linkage: Parent page P_ID1, slot S_ID1 in object ID O_ID1, index ID I_ID1, and page P_ID2, slot S_ID2 in object ID O_ID2, index ID I_ID2, next refer to page P_ID3 but are not in the same object."

Cause:

The issue occurs as the next page pointer of P_ID2 and P_ID1 page point to P_ID3 in a different object.

Resolution:

To overcome such situation, there is a need to repair SQL database. For this purpose, you can try out the following MDF file repair methods, ideally in the given order:

Fixing the hardware-related problems: Lot many times, these issues evolve because of problems in the hardware parts. Such issues can be fixed to perform SQL repair using the following measures:

Running hardware diagnostics and try to resolve the issues, if any. Checking the error logs and analyzing if the error has occurred because corruption in the hardware components.

Installing the operating system after formatting the hard disk.

Restoring from the updated backup: If the problem does not solve, then check the status of the backup. Restore the database with the backup, if it is updated and clean.

Executing DBCC CHECKDB: If the previous method does not work, then run the DBCC CHECKDB tool with the recommended repair clause to repair MDF file.

In case you are still getting the same error, then there is an urgent need to use a professional SQL repair software. The best feature of these MDF repair tools is that they repair SQL file without damaging the original SQL database.

The best.MDF repair software that should be used in this case is Stellar SQL Database Recovery, which is compatible with Windows 7, Server 2008, Vista, Server 2003, XP, and 2000. With the ability to repair MDF files created in MS SQL Server 7.0, 2000, 2005, and 2008, this MS SQL repair software repairs various SQL objects including collations, defaults, NDF files, stored procedures, tables, triggers, etc.

»»  Read More...

How to recover MDF file when you encounter Error 8910 in MS SQL Server 2000

Are you getting error messages repeatedly while working on a particular database in MS SQL Server 2000? If yes, then you should check the exact cause of these messages as there may be chances of database corruption. The database corruption can happen due to various reasons including virus infections, malfunctioning of the hardware components, abrupt or unplanned system shutdown while the database is open, etc, which could even make the database inaccessibile. In such cases, you should look for MDF file recovery using appropriate corrective methods, failing which you must use a third-party MS SQL Server recovery software to do the needful.

Let us consider a situation in which you are getting the following error message while working on an MS SQL Server 2000 database:

"Page P_ID in database ID DB_ID is allocated to both object ID O_ID1, index ID I_ID1, and object ID O_ID2, index ID I_ID2."


Cause:

The most prominent reason behind this error is that the index definitions in the IAM pages have damaged.

Resolution:

To perform MDF recovery of the damaged SQL database, you should perform either of the following methods, ideally in the given sequence:

Address hardware related issues: It may be possible that the error is occurring due to hardware corruption, which can be resolved using the following measures:

Fixing the issues that appear after running hardware diagnostics.
Swapping the hardware components to isolate the exact reason and fixing it.
Checking the Windows application log and the SQL Server error log to find out whether the error has occurred due to hardware malfunctioning.
Checking if the hard disk has write-caching enabled. If yes, then contact the hardware vendor to replace the hard disk.

Restore from database: You should check the state of the database backup. If it is updated and clean, then you should restore the database with its backup.

Run DBCC CHECKDB: If the backup is not clean, then you should run the DBCC CHECKDB tool with the suggested repair clause to recover MDF file.

If these aforementioned methods are unable to address the situation, then you would need to take the services of a third-party master database file recovery software. With the use of read-only recovery mechanisms, these SQL recovery tools ensure that no type of data is lost or damaged during the recovery.

In such cases, I would recommend you to use Stellar Phoenix SQL Data Recovery, which recovers SQL databases created in MS SQL Server 7.0, 2000, 2005, and 2008. Performing .MDF recovery by recovering databases components including NDF files, stored procedures, tables, defaults, triggers, etc, this SQL database recovery software is compatible with Windows 7, Server 2008, Vista, Server 2003, XP, and 2000.

»»  Read More...

Repair & Restore SQL Server Database from Suspect Mode

Sometimes when you try to connect to your SQL database server, you may get your SQL database in suspect mode. At that point your database server would not allow you to access and perform any operation on it. Your database will accessible only when the database will be repaired. For fixing the problem you will have to use advanced SQL database recovery tool.

SQL server database can go in suspect mode for many reasons; some of them are given below:

Improper shutdown of the database server
Corruption of the database files
Unavailable device files
Unavailable database files
Database resource used by operating system
SQL Server incorrectly asserts free data page space when a row is inserted


You can know the exact reason for the SQL database suspect mode. You will have to use given below query for knowing the exact reason.

“DBCC CHECKDB (’YourDatabasename’) WITH NO_INFOMSGS, ALL_ERRORMSGS”

After running the above query you will able to know the exact reason of the database suspect mode.

To fix the suspect mode and restore the database, run following queries in Query Analyzer of SQL server database,

“EXEC sp_resetstatus ‘yourDatabasename’;
ALTER DATABASE yourDatabasename SET EMERGENCY
DBCC checkdb(’yourDatabasename’)
ALTER DATABASE yourDatabasename SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC CheckDB (’yourDatabasename’, REPAIR_ALLOW_DATA_LOSS)
ALTER DATABASE yourDatabasename SET MULTI_USER”

At finally you have done it. But sometimes after the running of above queries in query analyzer you are still unable to perform any operation on the database. This means your database has got badly corrupted. At that situation you will have to use third party SQL server recovery software to repair the database.


Stellar Phoenix SQL database recovery tool is the advanced repair and restore tool that support MS SQL server 2008, 2005, 2000 and 7.0. It can also repair the NDF files of the database. It is comfortable with windows 7, XP, Vista, 2003, 2000 and NT.

»»  Read More...

How to Resolve 'Error 823' While Accessing SQL Database?

Are you getting 'Error 823' while accessing an SQL Server database or modifying the database? Are you getting various database inconsistency errors while querying SQL Server database? Well, the problem may take place if your SQL Server database is either inconsistent or damaged. In such critical situations, you must have a complete backup to restore data from it. However, the situations may become worse if there is no current backup in place. At this point of time, you have to opt for SQL recovery tools to get your valuable data recovered.

You may come across the below errors in Windows Application Event Log or MS SQL Server ERRORLOG while performing any operation on MDF (Master Database File) of SQL Server:

"2010-03-06 22:41:19.55 spid58 Error: 823, Severity: 24, State: 2. 2010-03-06 22:41:19.55 spid58 The operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x000000a72c0000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2008\MSSQL\DATA\my_db.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level 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."

2009-12-09 04:53:49.170 spid25s Error: 823, Severity: 24, State: 2. 2009-12-09 04:53:49.170 spid25s The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x00000000132000 in file 'D:\tempdb\tempdb_data.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level 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.

Cause:

The Error 823 may occur due to either SQL Server database corruption or I/O errors in the database. The error usually indicates that that there are some inconsistency in file system or the database file is corrupt.

Resolution:

To recover SQL server database, use any of the below methods:

Run Chkdsk to find file system inconsistency issues and resolve it.

Use DBCC CHECKDB utility to try repairing the damaged database.

If the above methods can not perform MS SQL recovery, You need to use third party applications to repair and restore the damaged database. The MDF Repair software performs safe, quick, easy, and absolute recovery in all MDF corruption situations.

For More Information Visit: http://ezinearticles.com/?How-to-Resolve-Error-823-While-Accessing-SQL-Database&id=4396378

»»  Read More...

Rectifying Error 2579 in SQL Server 2000

The most basic unit of storage in an MS SQL Server database is a page, which accounts for 8 KB of size. And 8 such pages consist an extent thereby making 16 extents in 1 MB. An extent is used to allocate spaces for tables and indexes. The well-being of the database structure is absolutely essential for the database. However, at times problem arises in the structure of the database because of various reasons such as virus infection, power surges, human error, hardware failure, etc. In such cases, you should use appropriate measures to rectify the situation. However, if you are unable to do so then you should use a third-party SQL server recovery software to recover SQL database.

Consider a scenario wherein you encounter the following error message while working on an MS SQL Server 2000 database table.

“Table error: Extent P_ID object ID O_ID, index ID I_ID is beyond the range of this database.”

Cause:

The cause of this error message is that an extent has been allocated in an Index Allocation Map (IAM) page for the referenced index ID. In the error message, P_ID is the ID of the corrupted page in the table. The pageinfile of the extent is greater than the expected size of the file specified in the database, which has caused the error.

Resolution:

To resolve this error message, you can perform the following methods, preferably in the given order:

Look for hardware issues: Run hardware diagnostics to resolve any issues. Also, check the error logs to check whether the issue has occurred because of any faulty hardware. You can also swap the hardware components to zero in on the problem. You can also consider switching to a new hardware system altogether.

Restore from backup: Restore the database from its backup if it is updated and clean.

Run DBCC CHECKDB: Finally, you can run the DBCC CHECKDB command, first, without any repair clause to know the corruption level. Then, run the command again with the suggested repair clause. However, you should refrain from using this method if you are not sure about the aftereffects of using the repair clause on the database.

However, if you are unable to address the situation even after using the mentioned methods then you should use a third-party SQL Server recovery software to recover SQL database. These read-only tools are able to perform SQL database recovery using fast yet sophisticated scanning algorithms without damaging the original data.

Stellar Phoenix SQL Database Recovery is an MS SQL recovery tool that enables you to recover corrupted databases created in SQL Server 2000, 2005, and 2008. It is able to perform mdf repair of various database components such as tables, triggers, views, rules, stored procedures, etc. This SQL Server recovery tool is also capable of recovering database constraints and relationships among tables. It is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

»»  Read More...