Robert,

IB/Firebird has a database shutdown function, which prevents all users
except for SYSDBA from connecting to the database. This does not
shutdown the database engine - thus allowing for Backup and other
maintenance operations to take place without any user activity taking
place.

This was the "shutdown' that Jason was referring to.


Sean
-----Original Message-----
From: Robert F. Tulloch [mailto:tultalk@...]
Sent: Tuesday, January 02, 2001 2:11 PM
To: ib-support@egroups.com
Subject: Re: [ib-support] Locking DB

Hi:

Thanks.

> > How can the locking (exclusive use) be done?
>
> Do a database shutdown. Then, restart it when done.
>
> But, if you are only doing a backup, you don't actually need to lock

down

> the database.

Perhaps these is some confusion here. I shut down (disconnect all
IBDatabases) and
then do my stuff, restore etc. While I am doing this I don't want anyone
to be able to
start my app and connect. I am doing this stuff from either console or
another
instance of my app. As far as I can see, there is nothing that would
prevent another
user from connecting. In restore to a different dir then copy over the
production DB.
I want to prevent anyone from connecting while I am copying it. PLus I
don't want
anyone connecting while I am doing a backup. That way it is fixed and
there is no
ambiguity as to when it was done vs who was using it at the time.

What I am looking for is to shutdown then use the DB exclusively.


Best
regards

To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com