Thank you @49885604 for your articles and reply.
Let's say that a 40-50GB database would certainly have impacts on the disk space of the IssuingCA, also causing impacts in terms of resources to the machine. In case of virtual machine we could increase disk size, memory and virtual CPU.
In the event of a database disaster and restore, it may take a long time to import 50GB of database into a new IssuingCA. Correct?
What about the possibility of splitting the enrollment of certificates across multiple IssuingCAs? By defining which specific templates do enrollment from one IssuingCA while others from another server!
Is there a specific best practice about that? Related also to the database increasing!
Kind regards,
Alessio.