Hi Karthick,

>Embedded Server :
> In case of embed I hope it will suit for smaller applications.
>(If I am wrong kindly correct me). But in case of larger applications
>i.e. when the application need to handle millions of record. I am not
>sure of the the scalability of embedded database process. Is there is
>any specific things to be handled in such a case.
>
>

It's exactly the same for small and big applications.
One of my clients have a database with almost 1Gb, they use to have more
than 50 concurrent conections. This situation on the main server. But
sometimes time pick up a backup of the database, and copy it to a
laptop, so they can work at home. I'm using embedded server on laptops.

> Do you prescribe me to use not to use embedded DB in such a case?
> Or my aplication process memory to be increased ? If so What is the
>memory to be alloted for normal embedded database alone?
> Is there is some other tips kindly provide me?
>
>

Use embedded in the same way that having a server, with just one
connection. See the limitations of embedded server on the readme file.

>When Separate Database server is packaged:
>
> Since we package the DB server along with our application. We need
>to start the dbserver when the db gets started and stop it when our
>application gets stopped. Similar to "fbmgr" in linux is there is any
>equivalent tool in windows, to stop the firebird server in windows.
>
>

Don't do this. Tou should always think that could be more applications
using the server. Your client can buy a different product that uses
Firebird as well and you will be stoping something that is needed by
someone else.

Artur