Debriefing

Naturally, the base has been centralized. After some time in the database has collected information on thousands of devices, the performance has fallen sharply and became resemble a turn-based strategy. Further use of this product has become impossible. I had to do "debriefing". Credit: Pinterest-2011. The base itself was implemented as a dbf files.

Essentially, customers are not treated to the database server data and worked with the base as with regular files that increasing the size of the latter resulted in a sharp loss of productivity. Moreover, when analyzing the structure of the database revealed the error data breaches. Similar problem is especially severe in large organizations. For smaller organizations, performance issues may not be as significant. Now about data security. The question that many simply ignored, and completely in vain. Data security is dependent on the choice of databases and the technology to work with her.

It is clear that if the database is considered part of the client in the form of files that any user can modify it unauthorized changes or even completely destroy the base. Such a situation occurs, for example, all products 1C version 7 and below – any user can at least get all the data base. Such a situation exists in many projects. Would like to remind the authors, in the yard 21. Optimal in terms of security situation – is to use a client-server technology to the imposition of the control rights of the user (and the whole business logic) to the server side.