Combined or Separate DB files?

[RT483b]

Deciphered boundaries for this discussion: I don't consider online server storage any more secure than storing (Passwords, TOTP, & Passkeys) inside KeepassXC with a 16 char (or more) strong Password design in a computer. I don't store much on my phone because it travels and is exposed more.

This discussion is merely for input on Pros or Cons of having separate KeepassXC DB files each with a different Passwords for storing each of Passwords, TOTP, & Passkeys;
as opposed to just putting all 3 (Passwords, TOTP, & Passkeys) in a single KeePassXC DB.

1. My Main KeepassXC DB has quite a few delineated Groups with each it's own specific type entries. It's all organized by types of Groups and/or Entries.

2. For awhile now I've kept all my TOTP entries in a separate DB and open it only for sites that have TOTP. And that works fine since I keep all my TOTP entries in one Group with alphabetical sort. It's laid out kinda like a simple Aegis Authenticator list.

3. Now I'm considering having a 3rd separate DB for Passkeys with same one Group premise as the TOTP.

However I'm wondering is this really necessary, why not just put all 3 in the Main DB where they all are in their specific type Group and Entry. KeepassXC has strong password design capabilities and built in protection against brute force attacks.

Would like to hear what paradigm other's use, and what the trade offs or advantages they found with their setup.

[droidmonkey]

There is very little reason to split your database. A good reason to split it is if you have highly sensitive entries that you would not want to have on a mobile device or other computer, if you sync your db file. Place the highly sensitive entries in their own DB.