Reply to thread

Message: <blockquote data-quote="HAneo" data-source="post: 27197886" data-attributes="member: 17432">For large ERP systems, we use client Side lightweight DB like SQL Express. let's say you need to get a product by its ID when creating an Invoice. you can get it from loaded Products on the client-side instead of requesting data from a server with an unknown condition. and save the Invoice data on the client-side. as well as for ERP you need a write a Journal as well.  implement proper Day end process and Sync data back and forth.Scenarios:1. in case of full data lost you have journals and can manually upload the data to the system2. If day end fails client-side DB's has the individual data. so you can run the Day End once again at night or in the morning where network traffic is minimum 3. in this way you only need the connection for a few minutes from server to client 4. do not use SQL replications cus ultimately you will end up in the mud. instead of that think about what data need to be sent from client to server and server to client at the end of the day and create a program yourself for sync 5. instead of getting a PC,  try SOme Free Mysql DB on the cloud. you only need an Extra DB for this task yes? SO if your systems already using MSSQL create an adaptor Program to Transform MSSQL to MySQL(USe dapper or IBatis (<a href="https://ibatis.apache.org/docs/dotnet/datamapper/" target="_blank">iBatis Apache </a>) )and you need to implement proper DR Plans. in this case keep 2 MySQL instances in sync with each other. if one fails you can point the Clients to another DB and execute DR plans (which means recovering the original DB)</blockquote>

Verification: Payakata winadi keeyak tibeda?

Top Bottom