"For example - don't distribute database itself but let customers to access data via the Net"
You seem to be stubborn and begging the question. Are you telling me that Firebird was never designed to distribute a database locally?
You seem to misunderstand our application. Our application connects to 2 databases: one locally, and one remotely.

Also, we can use the SYSDBA user for users to access our database, but this is not best-practice. Best-practice doesn't mean "bad idea", it actually depends on the application.
In our software application the software uses SYSDBA and has full access to the database, however, when the user logs on (using the software) it knows his/her permissions, and he cannot do something in the database if he does not have such permissions.

Now, was it really necessary for me to explain and describe my exact application for you to help me?
If you wanted to help, you could answer the question without the above information. Here it is again:
"When deploying a database file to a new computer for deployment of an application, what is the easiest way to re-set up a certain username and password, example "SYSDBA" and "p@ssword" ?

--- In firebird-support@yahoogroups.com, Dimitry Sibiryakov <sd@...> wrote:
>
> > In our scenario, we want to restrict access to the database using a password on the SYSDBA user.
>
> Forget it. SYSDBA is (obviously) local database administrator. You
> must not use this accout for your database.
>
> > Can you give please me some advice?
>
> Review your strategy of data protection.
> For example - don't distribute database itself but let customers to
> access data via the Net, keeping the database at your site under your
> control.
>
> SY, SD.
>