RE: [firebird-support] Using Firebird SuperClassic and Embedded (SC) v2.5 on same server
LS External applications use a normal users, our internal LS applications use SYSDBA. We want to even control our own LS applications from accessing the database Single shutdown mode allows only one connection (from SYSDBA or OWNER), so if you are able to assure that your maintenance app will put the DB in Single Shutdown mode and be the first one to connect to it just after that, you would be safe. Thanks for the reminder. There are other reasons why we want to have both instances installed. I am looking for *details about the gotchas* (I think I recall a post about an environment variables for the lock manager), not about the alternate approaches. Sean
Re: [firebird-support] Using Firebird SuperClassic and Embedded (SC) v2.5 on same server
LS Although we deploy standard server installs, there are times when LS we need to ensure that no external connections (ODBC) can connect LS to local databases while we perform database maintenance. Can't you just put the database in single shutdown mode before doing the maintenance? PS: I'm assuming your normal user doesn't connect to the database as SYSDBA/OWNER. LS Deploy standard server installs, but also deploy embedded DLL LS into application folder for our maintenance tool. LS So, our deployment approach would be: LS - stop the Firebird server LS - perform the maintenance using DB tool, LS - restart Firebird, LS Questions: LS - is the above possible? LS - If so, are there any gotchas that I need to be aware of? Other apps using an embedded engine would also be able to connect to the database during the maintenance. Not a problem if you are sure that no such apps exists, but you know Murphy... []s Carlos Firebird Performance in Detail - http://videos.firebirddevelopersday.com www.firebirdnews.org - www.FireBase.com.br
RE: [firebird-support] Using Firebird SuperClassic and Embedded (SC) v2.5 on same server
Carlos, LS Although we deploy standard server installs, there are times when we LS need to ensure that no external connections (ODBC) can connect to LS local databases while we perform database maintenance. Can't you just put the database in single shutdown mode before doing the maintenance? PS: I'm assuming your normal user doesn't connect to the database as SYSDBA/OWNER. External applications use a normal users, our internal applications use SYSDBA. We want to even control our own applications from accessing the database (our apps are services, so a remote admin could naively start the service, when we are doing maintenance) LS Deploy standard server installs, but also deploy embedded DLL into LS application folder for our maintenance tool. LS So, our deployment approach would be: LS - stop the Firebird server LS - perform the maintenance using DB tool, LS - restart Firebird, LS Questions: LS - is the above possible? LS - If so, are there any gotchas that I need to be aware of? Other apps using an embedded engine would also be able to connect to the database during the maintenance. Not a problem if you are sure that no such apps exists, but you know Murphy... True. We have pretty strict control of the client systems which our application is installed on, so the possibility of this issue (for us) is less than 0.1% Sean
RE: [firebird-support] Using Firebird SuperClassic and Embedded (SC) v2.5 on same server
At 09:25 a.m. 14/03/2013, Leyne, Sean wrote: External applications use a normal users, our internal applications use SYSDBA. We want to even control our own applications from accessing the database (our apps are services, so a remote admin could naively start the service, when we are doing maintenance) They couldn't if the database was in exclusive shutdown. Helen
Re: [firebird-support] Using Firebird SuperClassic and Embedded (SC) v2.5 on same server
LS External applications use a normal users, our internal LS applications use SYSDBA. We want to even control our own LS applications from accessing the database Single shutdown mode allows only one connection (from SYSDBA or OWNER), so if you are able to assure that your maintenance app will put the DB in Single Shutdown mode and be the first one to connect to it just after that, you would be safe. []s Carlos Firebird Performance in Detail - http://videos.firebirddevelopersday.com www.firebirdnews.org - www.FireBase.com.br
