|
|
You're in the
sql server programming
group:restore database issue
sql server programming:
I have 2 databases in use. One is Dev, the other is Test.
I created a backup of Dev, dev.bak. When I executed the statement: restore database Test from disk = 'D:\BackupLoc\dev.bak' with replace I got a message that said: "Processed XXX pages for database 'Test', file 'Dev' on etc RESTORE DATABASE successfully processed xxx pages... No error occurred, and it looked like the process worked. But nothing happened to Test. I could see the old stored procedures and old data. Does it matter that the schema for Test was substantially different than Dev? I then used the GUI to replace using the same file (Tasks -> Restore -> Database). That worked Then I modified some data in Test, re-ran the exact same restore database script and it worked this time. I could see that Test had Dev's data. Why would that happen? My goal is to dump Test and replace it with Dev. Why would it work the 2nd time around, after I used the GUI to replace it. Thanks.
Tim
Hmm, WITH REPLACE means fisrt drop database and the restore. Are you sure? create database test go use test create table t ( c int) go insert into t values (1) go backup database test to disk ='c:\temp\test.bak' go --now insert one more row into t table insert into t values (2) select * from t --two rows --Now restore backup ( we should see only one row) use master restore database test from disk ='c:\temp\test.bak' with replace use test select * from t --ONLY one row GO drop database test [quoted text, click to view] "Tim Zych" <tzy---ch@NOSp@mE@RTHLINKDOTNET> wrote in message news:u5ESkZa$HHA.1208@TK2MSFTNGP05.phx.gbl... >I have 2 databases in use. One is Dev, the other is Test. > > I created a backup of Dev, dev.bak. > > When I executed the statement: > > restore database Test from disk = 'D:\BackupLoc\dev.bak' with replace > > I got a message that said: > > "Processed XXX pages for database 'Test', file 'Dev' on etc > RESTORE DATABASE successfully processed xxx pages... > > No error occurred, and it looked like the process worked. > > But nothing happened to Test. I could see the old stored procedures and > old data. Does it matter that the schema for Test was substantially > different than Dev? > > I then used the GUI to replace using the same file (Tasks -> Restore -> > Database). That worked > > Then I modified some data in Test, re-ran the exact same restore database > script and it worked this time. I could see that Test had Dev's data. > > Why would that happen? > > My goal is to dump Test and replace it with Dev. Why would it work the 2nd > time around, after I used the GUI to replace it. > > Thanks. > > > >
My guess is that you have several backups on that file and you restored an old backup. Use RESTORE
HEADERONLY to investigate the backup file. -- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi [quoted text, click to view] "Tim Zych" <tzy---ch@NOSp@mE@RTHLINKDOTNET> wrote in message
news:u5ESkZa$HHA.1208@TK2MSFTNGP05.phx.gbl... >I have 2 databases in use. One is Dev, the other is Test. > > I created a backup of Dev, dev.bak. > > When I executed the statement: > > restore database Test from disk = 'D:\BackupLoc\dev.bak' with replace > > I got a message that said: > > "Processed XXX pages for database 'Test', file 'Dev' on etc > RESTORE DATABASE successfully processed xxx pages... > > No error occurred, and it looked like the process worked. > > But nothing happened to Test. I could see the old stored procedures and old data. Does it matter > that the schema for Test was substantially different than Dev? > > I then used the GUI to replace using the same file (Tasks -> Restore -> Database). That worked > > Then I modified some data in Test, re-ran the exact same restore database script and it worked > this time. I could see that Test had Dev's data. > > Why would that happen? > > My goal is to dump Test and replace it with Dev. Why would it work the 2nd time around, after I > used the GUI to replace it. > > Thanks. > > > >
[quoted text, click to view]
> But nothing happened to Test. I could see the old stored procedures and > old data. Does it matter that the schema for Test was substantially > different than Dev? Schema doesn't matter. BACKUP/RESTORE process physical files so the target is exactly like the original database. My guess is that your first backup file contained multiple backups and the first backup (oldest) was restored by default instead of the intended last (latest) backup. If INIT isn't specified on the BACKUP command and the backup file already exists, the new backup is appended to the end of the file instead of overwriting. You can ensure the backup file contains only a single backup by specifying the INIT on the BACKUP command like the example below. This will overwrite the target backup file if it exists. BACKUP DATABASE DEV TO DISK = 'D:\BackupLoc\dev.bak' WITH INIT, STATS=10 -- Hope this helps. Dan Guzman SQL Server MVP [quoted text, click to view] "Tim Zych" <tzy---ch@NOSp@mE@RTHLINKDOTNET> wrote in message
news:u5ESkZa$HHA.1208@TK2MSFTNGP05.phx.gbl... >I have 2 databases in use. One is Dev, the other is Test. > > I created a backup of Dev, dev.bak. > > When I executed the statement: > > restore database Test from disk = 'D:\BackupLoc\dev.bak' with replace > > I got a message that said: > > "Processed XXX pages for database 'Test', file 'Dev' on etc > RESTORE DATABASE successfully processed xxx pages... > > No error occurred, and it looked like the process worked. > > But nothing happened to Test. I could see the old stored procedures and > old data. Does it matter that the schema for Test was substantially > different than Dev? > > I then used the GUI to replace using the same file (Tasks -> Restore -> > Database). That worked > > Then I modified some data in Test, re-ran the exact same restore database > script and it worked this time. I could see that Test had Dev's data. > > Why would that happen? > > My goal is to dump Test and replace it with Dev. Why would it work the 2nd > time around, after I used the GUI to replace it. > > Thanks. > > > >
100% positive. I ran it from master as you are doing. I tried this 2 nights
in a row and got the same result, until the 2nd night when I used the GUI and then the sql command. It's working now though. [quoted text, click to view] "Uri Dimant" <urid@iscar.co.il> wrote in message news:%23l0PU4a$HHA.536@TK2MSFTNGP06.phx.gbl... > Tim > Hmm, WITH REPLACE means fisrt drop database and the restore. Are you sure? > > create database test > go > use test > create table t ( c int) > go > insert into t values (1) > go > backup database test to disk ='c:\temp\test.bak' > go > --now insert one more row into t table > insert into t values (2) > select * from t --two rows > --Now restore backup ( we should see only one row) > use master > restore database test from disk ='c:\temp\test.bak' with replace > use test > select * from t --ONLY one row > GO > drop database test > > > > > > "Tim Zych" <tzy---ch@NOSp@mE@RTHLINKDOTNET> wrote in message > news:u5ESkZa$HHA.1208@TK2MSFTNGP05.phx.gbl... >>I have 2 databases in use. One is Dev, the other is Test. >> >> I created a backup of Dev, dev.bak. >> >> When I executed the statement: >> >> restore database Test from disk = 'D:\BackupLoc\dev.bak' with replace >> >> I got a message that said: >> >> "Processed XXX pages for database 'Test', file 'Dev' on etc >> RESTORE DATABASE successfully processed xxx pages... >> >> No error occurred, and it looked like the process worked. >> >> But nothing happened to Test. I could see the old stored procedures and >> old data. Does it matter that the schema for Test was substantially >> different than Dev? >> >> I then used the GUI to replace using the same file (Tasks -> Restore -> >> Database). That worked >> >> Then I modified some data in Test, re-ran the exact same restore database >> script and it worked this time. I could see that Test had Dev's data. >> >> Why would that happen? >> >> My goal is to dump Test and replace it with Dev. Why would it work the >> 2nd time around, after I used the GUI to replace it. >> >> Thanks. >> >> >> >> > >
You're right. that was it.
Thanks for your input along with Uri and Dan too. Tim "Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote in message news:55DF2B68-D316-4C30-9044-49A01C879B0C@microsoft.com... [quoted text, click to view] > My guess is that you have several backups on that file and you restored an > old backup. Use RESTORE HEADERONLY to investigate the backup file. > > -- > Tibor Karaszi, SQL Server MVP > http://www.karaszi.com/sqlserver/default.asp > http://sqlblog.com/blogs/tibor_karaszi > > > "Tim Zych" <tzy---ch@NOSp@mE@RTHLINKDOTNET> wrote in message > news:u5ESkZa$HHA.1208@TK2MSFTNGP05.phx.gbl... >>I have 2 databases in use. One is Dev, the other is Test. >> >> I created a backup of Dev, dev.bak. >> >> When I executed the statement: >> >> restore database Test from disk = 'D:\BackupLoc\dev.bak' with replace >> >> I got a message that said: >> >> "Processed XXX pages for database 'Test', file 'Dev' on etc >> RESTORE DATABASE successfully processed xxx pages... >> >> No error occurred, and it looked like the process worked. >> >> But nothing happened to Test. I could see the old stored procedures and >> old data. Does it matter that the schema for Test was substantially >> different than Dev? >> >> I then used the GUI to replace using the same file (Tasks -> Restore -> >> Database). That worked >> >> Then I modified some data in Test, re-ran the exact same restore database >> script and it worked this time. I could see that Test had Dev's data. >> >> Why would that happen? >> >> My goal is to dump Test and replace it with Dev. Why would it work the >> 2nd time around, after I used the GUI to replace it. >> >> Thanks. >> >> >> >> >
Don't see what you're looking for? Try a search.
|
January 2003
March 2003
April 2003
May 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
April 2008
August 2008
| home · blog · groups | Questions? Comments? Contact the dn |