An expert who has achieved level 3 by getting 1000 points
An expert that got 10 achievements.
An expert that got 5 achievements.
An expert who has achieved Level 3.
Re: how get sql data backup
There are several other software also available for SQL Recovery, I would also like to mention here one of them. By this effective application, you can instantly repair damaged MDF file with in few clicks. You can get more details along with a free trial from here :- SQL Database MDF Recovery
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
An MDF file isn't a backup file isn't the main data file (or master data file depending on who you ask) hence the file extension MDF. You can attach the MDF to the database by right clicking on the databases folder in Enterprise Manager (SQL 2000) or Management Studio (SQL 2005) then selecting all tasks and then Attach Database.
When you do this you will get an error about the log file missing. This shouldn't matter as SQL Server will simply create a new log file for you.
This will only work if the SQL Server was stopped when you copied the MDF file from the old SQL Server. If you copied the file while the SQL Server was running this file probably will not attach either and you will need to get a valid backup of the database.
Download help tool for sql database - SQL Server Restore Toolbox. http://www.sqlserver.restoretools.com/
You can read up more on SQL Server here. http://www.filerepairforum.com/forum/microsoft/microsoft-aa/sql-server/498-creating-a-new-database-using-an-mdf-file?_=1416149856104/
Microsoft Windows Server 2003, Web Edition
Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
Microsoft Windows Server 2003, Enterprise x64 Edition
Microsoft Windows Small Business Server 2003 Premium Edition
This problem occurs when the following conditions are true:
You back up data from a volume that contains a Microsoft SQL Server database.
The recovery model of the SQL Server database is configured to use an option that is different from Simple.
Submit a request here to get a hotfix from Microsoft ( Its free and no product key will be asked )
I suggest you use the Enterprise manager (gui tool to manage SQL).
Restoring a single table is not an option.
You can however restore a file or filegroup.
Make sure to backup before you start and NOT to restore database to its original name or original file location, to avoid acidents.
Normally you will have databases with only 2 files: the data at its Primary file group, and log file.
You may wish to create a new file group and move tables to the new group by recreating them there and exporting data from old table to new table. Then recreate indexes. This may prove to be complex as all tables and indexes have unique names and can't coexist with exact duplicate of them.
oh yea..... did I say backup?
well just in case backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup
but dont overwrite that backup
Well there is more than one or two answers 4 that.
you should first check if you are at simple recovery mode. If not (now this will sound strange) right click the database, click tasks/backup and make a LOG backup.
Now right click databases and click Restore Database.
You should choose a new database name (for restore practice) .
You will probably have your last backups at the bottom of the screen...if not click add and choose you latest data backup.
click the log backup and the data backup should be checked , too. on options tab make sure the database is left ready to use.