@Hally - good question and one of the areas that we are researching with our Cloud Ops DBAs and MS.
Current proposal is that we will be removing the Read-Only attribute from the DB and managing the Read-Only aspect via User Permissions.
@Hally - good question and one of the areas that we are researching with our Cloud Ops DBAs and MS.
Current proposal is that we will be removing the Read-Only attribute from the DB and managing the Read-Only aspect via User Permissions.
I think there is an Epicor idea on this
Thanks @Rich, another one HA is great, but Enterprise Ed is $$$$$$, and if you want to use the Use Non Primary DB option for BAQs you need read only replicas, which is only a feature of Enterprise. Is there any investigations going behind the scenes for some other option, I appreciate you could argue this is one of the uses for External BAQs, and use some other replication option.
It also would be good to see some more technical documentation primers specifically around these features particularly from a Kinetic perspectiveā¦ Unfortunately not all of us have broad knowledge to have a good handle on the less spoken about technologies that support the platform,. Four I can think of immediately, HA, NLB, ARR and Docker/Kube. Nothing in depth, but more a diagrammatic overview/primer and a series of links. Happy to be told different and I have just missed these on Epicwebā¦
Does it need to be backed up for us to restore, since it doesnāt contain user info? Or can it be re-created in EAC with the āUpdate Common Databaseā function? Or creating a new database of whatever version you need?
Good questions @askulte
Iām unaware of how to trigger a re-create action, unless youāre upgrading a major version. Near as I can tell, each patch Iāve applied to 2024.1 expects the common DB to be there because the only action you can perform is āUpgrade Common Databaseā.
Iām old school DBA - if the database is āproductionā itās treated equally, no matter itās function. We have a utility db, a kinetic db, a reporting db, temp dbs, and now a common db. To me, they are all equal, so equal treatment and respect for mishaps. Now, I dontā backup everything on the same schedule - thatās based on usage or anticipated change volume. E.g. the reporting dbs and the common db are simple backups in my weekly backups, while my utility db is a simple back up daily.The kinetic db is a full daily, with translog backups every 2 hours.
To each their own. You could just backup the common db after every upgrade/patch and keep it on a seperate disk to protect it.
@MikeGross you can get it created by making a demo database for that version and it will create it if missing.
I heard @josecgomez and @jgiese.wci had alot of fun with SQL Enterprise and ICECommon this week.