project group

[Ismael L. Donis Garcia]

I have a bunch of small projects to do. for a maximum of 100 users, on average 20 to 50 users.

 

Although the projects are independent, I have thought that their tables are in the same database.

 

What do you recommend I do in the same database or in independent databases?

 

I also wanted to start them in version 5 of firebird since it is close to being stable.

 

What page size would you recommend for version 5 with UTF-8 character set?

 

Thanks in advance.

--
Ismael

[Dimitry Sibiryakov]

Ismael L. Donis Garcia wrote 22.05.2023 16:21:
> Although the projects are independent, I have thought that their tables are in
> the same database.
> What do you recommend I do in the same database or in independent databases?

If you ever need consolidated data from more than one user - single database.
If they are completely unrelated - different databases for security reasons.

> What page size would you recommend for version 5 with UTF-8 character set?

It doesn't matter much. Default is a good start.

--
WBR, SD.

[Steve Naidamast]

In my experience it is always a good practice to keep things separate in project development.  For example, when one form may do the job of two, I still opt for two separate forms.

The same with databases.

If you have multiple projects on your plate whereby the data for each may be the same, this is only for your current situation.  If one project user wants updates that forces changes to the database, such changes may also

impact the way the data is stored for one or more other projects.

Either way, you could potentially have more work as a result of changes down the road.  More work for taking care of multiple databases, or more work to ensure that a single database continues to meet the necessities of all

of the projects seamlessly.  The latter however, often causes more issues.

As a result, while you may find it more work to manage multiple databases, a change for a single project becomes far easier to implement since there is no concern as to any impact on other projects.

Steve Naidamast

Sr. Software Engineer

[Karol Bieniaszewski]

One simple advice, to other mentioned already.

Take into account that one database can be easly split into multiple databases but multiple databases are hard to join into one.

Especially database objects naming convention. If you name some table, stored procedure, trigger … in one database and you have same name in second, it can be hard to join tchem both into one.

 

Regards,

Karol Bieniaszewski

--
You received this message because you are subscribed to the Google Groups "firebird-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebird-suppo...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/firebird-support/32449451A8BD48179BA701D651AB158C%40natio.co.cu.