Manual… what a disaster.
Somehow your reaction makes me more convinced it was manual haha
3 Likes
Past tense isn’t warranted yet. Different reasons though. I suspect one of them is an artifact of this one plus a legacy process though.
Hate to rain on everyone’s parade, but even if you are public cloud, you are still probably on a shared DB. I had that confirmed in at my last company where we went straight to public cloud with install for a new site implementation.
Can’t say for other types like gov, but if you look in your licensing and see MT checked off, you are on a shared DB. Below is my current Public Cloud
Don’t ask me any questions as I don’t know the answer, I’m just saying what the Epicor employee told me.
3 Likes
From my understanding, the database is run in multi tenant mode, however in public cloud you are the only tenant in the DB apart from a management company.
If you were truly in a shared Db you would not be able to use the features of the Cloud management portal and regen / restore your own Db’s
4 Likes
That could be true! Like I said, I did not really understand what I was told.
Thanks for chiming in.
5 year
Continuing with what @BenWheeldon said, while there are multiple companies in a SQL Server, each company has its own instance. Each instance has its own credentials that are used by their associated application server. There should be no path from one company to another who share the same server.
In Epicor Multi-Tenant SaaS, there are multiple companies in one INSTANCE, and they are separated only by the CompanyID within the database. There are paths to getting to other company data in this configuration.
2 Likes
Welcome to my world, that is how i am having to move my sites from E9 to Kinetic as the data in E9 was so bad the Sirus tool was a non starter 
3 Likes
More like this.
edit:
and this is support when trying to recreate a layer issue.
14 Likes
hello Robert
Can I ask why you made the decision to go back to Prem? We are discussing going to SaaS. Thanks
Been there when a company I was working for went from E9 to E10.1. Basically was a new implementation with BAQ exports and DMT imports. We got rid of a bunch of crap customizations that were no longer needed and improved others that would of been harder to pull off if we’d just upgraded (mainly UD fields from the old Number01 type) and code flow/order.
2 Likes
Here’s hoping that project hasn’t started yet…
6 Likes