New answers tagged restore
2
You'll have to manually query for the rows and copy then in using either T-SQL or SSIS. There's no way to take the two databases and have SQL Server just merge them into one database.
If you are using identity vales on tables you'll need to be careful of duplicate values and assign new values to the rows that you are inserting. If you have other tables ...
2
Simple answer, no. The database being restored must match the source database.
this is not the fix you seek (waives hand dramatically)
0
Well you might have to go through another step or two: restore on another server, shrink, backup, copy and restore. If you restore in simple recovery mode (or switch to simple recovery mode which can be done with the db online), the log database will be (or can be shrunk to) as small as it can get. You can then switch to full recovery when the finance ...
6
No, there is no way. Restores really is meant to recreate the original database that was backed up. There are tools that allow you to query directly a backup w/o actually restoring it (Idera's SQL Virtual Database) but those are horrendously slow.
0
Well indeed, if the log is removed - blown away by the restore, and the changes were not yet applied then those changes are permanently lost.
The core data is still out there though right?
So you could consider a full load for suspect tables.
What is known about there changes suspect to be missing?
Can they be identified through some flag column or date ...
2
If you've ever taken a backup, and your recovery model is BULK LOGGED or FULL, then you might have some luck. Unfortunately if never took a backup before you had your problem, then you are probably bang out of luck (as Martin Smith pointed out in his comments below).
You can check whether you've ever taken a backup by looking at:
SELECT ...
0
You killed the restore, so your database is in recovery. Look here for estimating how long it will take to recover: http://timlaqua.com/2009/09/determining-how-long-a-database-will-be-in-recovery-sql-server-2008/
When restoring or backing up dbs, this article has a handy script which will estimate when the backup or restore will finish: ...
0
My standard backup regime for Oracle databases revolves around rman, flash recovery area and rsync. Basically as follows:
Configure your database in archive log mode, without it you will lose data. Not a question of if, but when.
Archived log files go to the flash recovery area.
Configure rman retention policy according to how far back in time you wish to ...
5
There should be no issue restoring differentials and fulls from SQL 2005 to SQL 2012. I would validate that your backup files are compatible. To do this, you'll want to use the RESTORE HEADERONLY command and compare the full backup's FirstLSN value with the differential's DifferentialBaseLSN:
restore headeronly
from disk='X:\BackupFiles\foo.bak'
If ...
0
Does anyone know why the differential backups from SQL Server 2005 will not restore properly on SQL Server 2012? And how can I fix this?
From BOL :
In SQL Server 2012, you can restore a user database from a database backup that was created by using SQL Server 2005 or a later version. However, backups of master, model and msdb that were created by using ...
0
If you did not take a log backup between the full yesterday and your restore today, then no, everything changed since yesterday is gone.
In a best case "accidently deleted data" scenario, the process is to take a log backup to capture the "tail"of the log, restore a full backup of the DB to an alternate location, restore log backups using STOPAT to get to ...
0
You should login to mysql like this
C:\> mysql -uroot -p <hit enter>
Enter password:
Next, select the database you want to load the data into
mysql> CREATE DATABASE IF NOT EXISTS mynewdb;
mysql> USE mynewdb
Then, run the script
mysql> source D:\backup\backup.sql
Give it a Try !!!
0
You should pass full path of .sql file like where it resides ex : "D:\file_name"
Try this one
mysql -u YourUser -pYourPassword DBName < D:\backupfile.sql
0
Summarizing the information linked to in the post above....
The command you have used is for a live backup but what you want is an incremental backup. The approach you want to use (per this blog) uses somewhat different switches. You want to use the -n -t -x switches, and the -o to specify a log file. So the command ends up something like:
dbbackup -n ...
Top 50 recent answers are included
