@Pradyuman - When you are talking about country specific data in the data schema, I believe you are also taking about case data and supporting transactional data (assignment, attachments, emails etc).

So, having this data split into 2 separate data schema wouldn't be possible because the underlying classes and tables would be the same (e.g. pc_assign_Worklist / workbasket, pc_link_attachment etc), so they can reside only in 1 schema. If you want to segregate those classes per country, then that would mean modifying out of the box code and behaviour, which is not recommended.

So, in this case the better option would be to have country / region specific instances so that the respective application can be hosted in that instance and data confidentiality can be maintained.