Subject | Re: [firebird-support] Re: Using the Embedded Server |
---|---|
Author | Woody (TMW) |
Post date | 2005-05-30T16:27:17Z |
From: "csiagent029" <csiagent029@...>
default system user and password so you can use that to create the owner you
need for your database. If the server is already installed, you will need to
prompt the install user for the SYSDBA password. You can try the default
first, just in case, but in most cases the password should have been changed
if the server has been running already.
In my case, I have my own, custom-built installer that I use so doing these
things isn't a problem. It's all built in. If you use other installers like
Wise, etc., they usually have options for scripts/exes to run during or
after install. Use that to set up the initial database stuff that you need.
Once the install program finishes, it can run an EXE that creates the user
needed, the new database, etc.. You can build a small app that does the
work for you and run that after the install. Exactly how you do things is up
to the actual installer that you end up using.
HTH
Woody (TMW)
> Thanks for your reply.If you install everything, such as when using embedded, then you know the
>
> And you got me thinking about stuff I hadn't considered really.
> The thing would be, how do you run a script to initialize the database
> at setup? Or on an existing firebird database for that matter?
> Do you use a particular installer for that?
> Thanks for any insight you can give me on this. It's the first time
> I'm trying to deploy an app that should install everything on its own.
> Before I've installed the apps myself for the most part.
>
default system user and password so you can use that to create the owner you
need for your database. If the server is already installed, you will need to
prompt the install user for the SYSDBA password. You can try the default
first, just in case, but in most cases the password should have been changed
if the server has been running already.
In my case, I have my own, custom-built installer that I use so doing these
things isn't a problem. It's all built in. If you use other installers like
Wise, etc., they usually have options for scripts/exes to run during or
after install. Use that to set up the initial database stuff that you need.
Once the install program finishes, it can run an EXE that creates the user
needed, the new database, etc.. You can build a small app that does the
work for you and run that after the install. Exactly how you do things is up
to the actual installer that you end up using.
HTH
Woody (TMW)