Optimizedb

>From: SusanF713@aol.com
>Subject: Optimizedb
>Date: 25 Feb 1995 00:46:55 -0500

>Thank you to everyone who tried to help me with my 
>optimizedb questions.

>Yes, I did read the manual before I posted the 
>question concerning locking the database.  The 
>manual was not exactly clear on whether or not it 
>would be a problem to optimize the database while
>users were accessing it -- this is why I posted the
>question.

>I think it makes more sense, and it probably would
>be more effective, to optimize it while noone else 
>was accessing it.  This why I wanted to know how
>to lock the database.  This is before I knew about
>Michael Leo's specific problem concerning optimizing 
>while the database is being accessed.

>At this point, I still do not know how to lock the database
>during optimization - I find it hard to believe it is
>impossible to do.

>- Susan
>susanf713@aol.com

Maybe you know this already, but I read this in my DBA Guide page 13-8 and 
learned something new :)

While optimizedb is running, Ingres takes an exclusive lock brief period on 
the user table being optimized. Whenever possible, tables on which statistics 
are created are not locked while statistics are gathered. This means that 
updates to the optimized table are not disabled for long periods. However it 
is recommended that you run optimizedb during "off hour" times.

 
     _____________
    /    ____     \
  /     |           \      Roger Fahlström  UDAC 
 |  ____ \    ____   | E-mail: roger.fahlstrom@udac.se 
 |     /  |   \ __   |
  \ _/   /      \   /
    \   |______   /
      \         /
        \     /
          \ /
Ingres Q & A
To William's Home Page
Email William