The licence goes into the property table and also a file on the file system. You should not be looking at the database though, to work on anything - if you're thinking of moving things around, your licence will need to change anyway.
Yes, the xml backup is defaulted to twice a day. If you've got a production system or just a large system, the xml backup is not the best solution and you should move to using the database backup (paired with a copy of the attachments separately)
There's no point, you can't just jam the developer or newly generated licence into the database and config, you need to trigger the code that evaluates it too.
Use the REST API licence validator to check the licence first, then you'll be able to add it.
We’re excited to introduce external collaboration for Confluence, now available in early access. It is available to preview for Confluence Cloud Premium and Enterprise customers. (If you're not on ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events