Showing posts with label sql server recovery. Show all posts
Showing posts with label sql server recovery. Show all posts

Tuesday, January 31, 2012

Three Stellar Phoenix SQL Recovery secrets that I bet you didn’t know


Stellar Phoenix SQL Recovery Software used systematic process to recover corrupt SQL Database and most of the new users don’t know about it. They simply thought that software recovered corrupt database, restoring database objects, put recovered data in to a new folder and then expect that database get recovered. But this is not all about the recovery process & the process doesn’t work that way. Yes it is true that these are the main functions of this software. But this software also has many advanced features that user may not be familiar with. Here are a few Software Recovery tips that I’d like to share with you guys:-


Save Queries of Severely Corrupted Objects: When database repairable objects preview shows in demo version then the user are sure to purchase the software but when the software won't shows any data in preview section it does not mean that the software is not able to recover the database, this is only first point which we should keep in our mind. The other points are that database gets severely damage. In this case may be other software also won't work. This software has feature to handle severely corruption: It permits database administrator to retrieve the query of the objects & save it in a Text file. With this advanced feature users don’t have to write long queries again. 


Give your database recovery process a fast start and do not need to wait until finish scanning process: This software has another advanced feature which allow user to select any specific objects to be recover from the list of recoverable SQL Data  without create any interruption in scanning process. So users have no need to wait till the end of the scanning process.


Database Recovery means a lot:  Stellar Phoenix understand the value of your database & have all efficient features to recover your corrupt SQL Server database. It offers easy steps to recover database such as full information about the software in help file, find option to search the database file if you forgot the location, recover almost all SQL Server components, recover both files mdf & ndf etc. 


I am sure the share information on SQL Recovery is very useful for you. In case you have found anything which I have forgot to mention in my post please let me know I will surely add it in my next post. 
»»  Read More...

Sunday, May 22, 2011

How to resolve error: “mdf is not a primary database file”

I want to share my personal experience on SQL Server Database. One day I was trying to set my SQL database online with command:

ALTER DATABASE mydb SET online

& suddenly I got an error message:

Msg 5171, Level 16, State 1, Line 1
E:\Data\mydb_log.ldf is not a primary database file.
Msg 5171, Level 16, State 2, Line 1
E:\Data\mydb.mdf is not a primary database file.
File activation failure. The physical file name "E:\Data\mydb.mdf" may be incorrect.
Msg 945, Level 14, State 2, Line 1
Database 'mydb' cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.

After that I do research on this error & I found this error occurs in many situations like :

1) When you are trying to attach your SQL database files with windows then also you get same error message. Mostly this error occurs in SQL Server 2005.

2) When you are trying to set your database online then also you get same error message.

Cause: 

The main cause of this error is that your mdf file get corrupt.

Solution: 

There is four solutions to resolve this error:

1. First you should check the database by this command “DBCC CheckDB”. It shows the details of the database then you can find the problem & easily resolve it.

2. You can tried to add the file using the command sp_attach_single_file_db. 

3. Try to restore database from a bak file.

4. It is possible that the database may have been corrupted when it was downloaded & “DBCC CheckDB” reflects damages in SQL server MDF file. You also don't have updated bak file. In this case you should try SQL Recovery Software. 

Note: If data get overwrite no one can repair it. 
  • When you find that your mdf file has been corrupt, don't perform any activity on the file. If there is 80% chances to resolve this error it will becomes 10%. because may be your data get overwrite from your activities & you will never get back your data. 
  • Before purchasing any SQL recovery software, first download its demo version & check the preview of your recovered database after that purchase it.
»»  Read More...