RESTORE DATABASE restores everything associated with the database. This
includes all catalog tables which store statistics and information about
bound plans. Data in tables will be in exactly the same relative
physical location as it was when the backup was made.
If you have a database of the same name on the instance; you must
specify REPLACE EXISTING" to overlay it. It doesn't matter if the
existing database is empty or contains data.
RESTORE's REDIRECT option allows you to move data to a different
location or disk drive during the restore. I've frequently used this
when restoring a database to a different system where the disk
configuration didn't match.
Phil Sherman
Thank you Phil for your answer.
When we restore db we take care to make sure the underlying directory
structures are same so a redirect is avoided wherever possible.
having rule out hardware differences, we sometime get complaint queries
are slower after restore, and runstats on all user tables followed by
rebind pkgs usually takes care of the problem, even thought the source
db had been refreshly runstat'd. I wonder if anyone else has same
experience?
Thank You in Advance, --SHG.
> RESTORE DATABASE restores everything associated with the database. This
> includes all catalog tables which store statistics and information about
[quoted text clipped - 28 lines]
> >
> > Look forward to your answers. Thank You. -SG
selma - 29 Jul 2005 22:41 GMT
B.U.M.P
Please forgive me for using old college technique to bring up my post!
I still would like to hear from others who experienced loss of
performance after backup, even to identical systems. Does the restored
db suppose to retain the same state of tune ( stats, data
fragmenetation) as the original, given identical system specs. I mean
we should not have to to runstat or even the extreme makeover of reorg
tables follow each restore ?
By the way,
The new yahoo group bulletin include a lot more text and reduces the no
of posts visible on a page to just a handful. Often people lose
interest and not bother with clicking on "Older Topics" buttons. So
many recent posts get little visibility in my opinion, and sort of
defeat the purpose of a community forum. I have no problem with the old
format where they just list the headings. People learned to be creative
in supplying meaningful headings. Then you will see like 20 recent
topics on a page.
If you agree :), you can click on HELP and find 'Contact Us' button to
let your opinion know to Yahoo Groups.
Thank you.
Selma
Phil Sherman - 31 Jul 2005 13:53 GMT
If you need to do RUNSTATS and REBIND after a restore to repair
performance then I'd pull a copy of the statistics before & after
runstats and compare them. You've something strange going on. I'd also
figure out if its the same queries that have the performance issue and
do before & after explains to look at access paths.
Your hardware configurations may not be identical. The systems may have
different real memory or even different disc configurations! I've seen
cases where one system had a C: drive that was RAID5 while the backup
had RAID1. The database only saw a C: drive. CPU speeds may also be
different.
Phil Sherman
> Thank you Phil for your answer.
>
[quoted text clipped - 41 lines]
>>>
>>>Look forward to your answers. Thank You. -SG
selma - 31 Jul 2005 16:56 GMT
Thanks again. I have to wait until next restore to capture this.
Selma
> If you need to do RUNSTATS and REBIND after a restore to repair
> performance then I'd pull a copy of the statistics before & after
[quoted text clipped - 55 lines]
> >>>
> >>>Look forward to your answers. Thank You. -SG