Re: Restore Database
From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 08/17/04
- Next message: Goober: "Problem running a SQL job"
- Previous message: casgo: "schedule job failed: SQLSERVERAGENT Event Id 208"
- In reply to: mat: "Re: Restore Database"
- Next in thread: Wayne Snyder: "Re: Restore Database"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 17 Aug 2004 15:01:50 +0200
Ahh, OK. Glad you found it. As you probably notice, we tend to ask for exact output and the command
executed. This is just to spot things like this. It is easy to forget that a backup set (especially
when backing up to disk) can have several files in it, something that Wayne picked up on... :-)
-- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ "mat" <anonymous@discussions.microsoft.com> wrote in message news:78b901c48453$dcc6e1f0$a401280a@phx.gbl... > Thanks Tibor, the problem has ironed its self our. THe DBA > who refered the question to me assured me that he was > selecting the correct backups within the back up set, alas > he wasn't...thanks for your help > > Mat > >-----Original Message----- > >I see. I'm afraid that we can't be of much help here if > you don't post the output from these > >statements and the exact restore command you try to > execute. Basically, we don't have anything to go > >on. > > > >You might want to open a case with MS support if you feel > that you have constructed the statement > >correctly and that SQL Server behaves in some erratic way. > > > >-- > >Tibor Karaszi, SQL Server MVP > >http://www.karaszi.com/sqlserver/default.asp > >http://www.solidqualitylearning.com/ > > > > > >"mat" <anonymous@discussions.microsoft.com> wrote in > message > >news:751601c4844c$e2127d60$a501280a@phx.gbl... > >> Cheers > >> We have already done that and they match > >> >-----Original Message----- > >> >Thanks. It seems that the logical filenames for the > >> database doesn't match the filenames you > >> >specified in the RESTORE command. I suggest you use > >> RESTORE HEADERONLY and RESTORE FILELISTONLY to > >> >verify the logical filenames etc, and based on that > >> construct your RESTORE command. > >> > > >> >-- > >> >Tibor Karaszi, SQL Server MVP > >> >http://www.karaszi.com/sqlserver/default.asp > >> >http://www.solidqualitylearning.com/ > >> > > >> > > >> ><anonymous@discussions.microsoft.com> wrote in message > >> >news:782b01c48449$d25b3bd0$a401280a@phx.gbl... > >> >> restore database x > >> >> FROM TAPE = '\\.\tape0' > >> >> with > >> >> MOVE datafile TO location, > >> >> MOVE logfile TO location, > >> >> nounload > >> >> > >> >> > >> >> >-----Original Message----- > >> >> >Can you post the RESTORE command you are executing? > >> >> > > >> >> >-- > >> >> >Tibor Karaszi, SQL Server MVP > >> >> >http://www.karaszi.com/sqlserver/default.asp > >> >> >http://www.solidqualitylearning.com/ > >> >> > > >> >> > > >> >> >"Mat" <anonymous@discussions.microsoft.com> wrote in > >> >> message > >> >> >news:041501c48447$0b4719d0$a301280a@phx.gbl... > >> >> >> I'm trying to restore a data base to a different > >> server > >> >> >> and ame getting this error message > >> >> >> > >> >> >> 'Logical file x is not part of database x' > >> >> >> can any one explain > >> >> >> > >> >> >> Cheers > >> >> > > >> >> > > >> >> >. > >> >> > > >> > > >> > > >> >. > >> > > > > > > >. > >
- Next message: Goober: "Problem running a SQL job"
- Previous message: casgo: "schedule job failed: SQLSERVERAGENT Event Id 208"
- In reply to: mat: "Re: Restore Database"
- Next in thread: Wayne Snyder: "Re: Restore Database"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
