Azure data studio emulates sql prompt5/31/2023 ![]() ![]() ![]() It had the name, email address, password and a few other columns. ![]() In the beginning there was the UserFile table (V8 or before). I’ll point our User because I know that off the top of my head and am in a hotel without source code in front of me. To your specific question on the caching. I would not like explaining to my boss how we cannot absorb new features due to making more complex integration’s that were against best practices of the vendor but if you think you can handle it, you are the domain expert for your company and IT group. If you enjoy constantly updating your processing and slowing your adoption of new releases, you are welcome to do so. Really a lot of this is around future proofing. Sure you can emulate the calculations in some scenarios (until the next feature enhancement which changes the math or the db structure). There are some fields that do not exist in the db and are calculated on the fly. The third item in the list mentioned - calculated fields. You can also use that group to lock down payroll which a lot of VPs get sensitive about for some reason. I ditto on the common sense MS / AD Auth access group approach. That is should we create a MS SQL user with read only access and give the credentials to all developers, create one user per developer, or something else? Are there any other best practices we should be following given that we plan to give developers read only access to MS SQL? In giving direct DB read only access are there any recommendations on how to set this up. Is anyone familiar or is there any documentation on this topic? As an example I can’t imagine data would remain in an object in RAM and not flushed to disk/db for more than a couple seconds. I get where these developers are coming from as I personally think it would be nice to be able to run a quick SQL query via Sequel Pro.Īssuming we’re not missing any other reasons to not give read only DB access, we’re curious to better understand how caching works in Epicor. I also understand there are other benefits to getting direct access to the DB such as having the ability to create views which I understand can have a pretty big performance improvement. Ownership trusts these engineers with access to all data with in Epicor and feels the benefits of giving them the access they desire so they can build reports to help the business is the best path forward. Some of these developers would like access to the DB so they can generate custom reports with tools they are familiar with and prefer. Please note we have a good number of system level software engineers(C and Assembly devs). Data may be stale (cached data may not have been flushed to the DB).Security is bypassed (anyone with MS SQL access has access to all tables).My understanding of the reasons not to allow read only access are We’ve decided to not allow write access to the MS SQL db, although based on our understanding of the risks it looks like we will allow read only access for developers. Thanks everyone so much for your feedback. ![]()
0 Comments
Leave a Reply. |