Migration of users of 1C from an ecosystem of Microsoft on open source: possible advantages and reefs

Traditionally products 1C were implemented in Microsoft Windows ecosystem, and the main platform for database maintenance (DB) was Microsoft SQL (MS SQL). If earlier such option of installation suited most of customers, then today more and more companies bring up a question of migration from an ecosystem of Microsoft on the softwares alternative platforms. The reasons for this purpose exists two: the first consists in a difficult world situation, and the second is caused by the growing popularity of operating systems of Linux.

More and more companies bring up a question of migration of solutions 1C from an ecosystem of Microsoft on alternative platforms

While Microsoft does global business, it is after all the American company. And at any time it can refuse support or updates to those organizations which fall under sanctions. If on a DB of MS SQL important business processes are started, it is better for companies already today "enclose straws" and be prepared for migration, than do it in a hurry after emergence of problems, - Alexander Rudnitsky, the programmer of CorpSoft24 company notes.

In a case with PostgreSQL Russian "registration" guarantees to the company resistance to any sanctions or other political collisions. And the open source code allows to supplement a distribution kit and to make changes according to requirements of specific installation of 1C.

The second reason is defined by requirements of an ecosystem of Microsoft to resources of computing systems.

Customers often ask quite correct question: "Why 10 DB work on the Linux server from 8 GB of OZU, and nobody complains, and on the Windows server from the same 8 GB of OZU – only 4 DB, but everything brakes?" Administrators usually answer this question that on the Windows server there is not enough memory because a third of all resources is occupied with OS, its components and other programs. After emergence of similar situations many have a question of optimization methods, - the expert of CorpSoft24 company says.

Moving on Postgre: reefs

Fortunately, 1C already some time supports an opportunity for work with alternative DB of PostgreSQL, and for their transfer or start of a new configuration no additional integration should execute. However the companies practicing new approach pay attention that it is necessary to consider certain moments and just to replace MS SQL or file storage with PostgreSQL it will not turn out.

For example, in 1C there is an automatic mode of management of blocking of data. It allows administrators to avoid the conflicts at an information access of different users and systems and successfully functions together with MS SQL. However in PostgreSQL the similar mode can lead to the conflicts and "podvisaniye" of a system which goes to a standby mode because of blocking of data.

Also "the tar spoon" to system operation is entered by the mode of compatibility with versions 1C 8.2 or 8.1 which are often used in different divisions of the Russian companies. To avoid the conflicts, these modes are also recommended to turn off. In many cases it leads to additional labor costs on configuring of 1C and completion of a system.

If you are going to place a terminal server on the same server, as DBMS, when using the Linux operating system it will be necessary to correct configuration 1C. Without it the mechanisms of the software product intended and developed initially for the Windows environment will not work. For example, reconfiguration is required for interaction with email clients, files and directories, COM connections.

Use in requests of such widespread construction of 1C as "Complete connection" can lead to decline in production. Let's emphasize that questions of performance should be considered in more detail, and though 1C Company positions the standard configurations as ready for work for PostgreSQL (direct to it confirmation – service 1cFresh), in each case transition to open and free DBMS can result both in increase in productivity, and to its decrease. Therefore by preparation of migration it is necessary to consider historical features of development of an ecosystem of 1C in the specific company.

In a cloud – it is more convenient

During the work of 1C together with the database it is necessary to provide permanent availability not only servers, but also a DB. For example, at operation of PostgreSQL with settings "by default" often there are problems with a stop and restart of service, and at reset or failure restoring access to the database requires several hours.

It is the simplest to begin testing of a new DB together with a cloud service as it allows to avoid similar situations, having placed a DB in a cloud environment where there is an automatic reservation of server capacities. Specially prepared by Linux servers start a DB on virtual machines with instant recovery. Thanks to it customers do not need to worry about backup of own DB and additional protection of power supply for the supporting servers.

Additional plus of cloud implementation of a DB for 1C consists in scaling options. At the request of the customer the provider can increase at any time available resources and ensure effective functioning of 1C for any number of users and even for multiply increasing amounts of data.

Migrate or not?

As it is possible to notice, the reasons for migration can be quite a lot: concerns of sanctions, the aspiration to pass to more reliable OS, the growing load of file bases 1C. However considering that in the different companies different versions 1C are used and also different amounts of data are processed, the migration problem on PostgreSQL has no universal solution and, as a rule, requires support from the specialized companies.

At the cumulative positive economic effect which is reached at the expense of the free license Postgres there are cases when use of a new DB is not justified. For example, one of clients of CorpSoft24 complained of a performance concern, and in an analysis result of a situation it turned out that its 1C system is not adapted for hard work on PostgreSQL. In this case adaptation was more expensive, than, on the contrary, of transition to MS SQL, - Alexander Rudnitsky, CorpSoft24 programmer notes.

With respect thereto questions of transition to PostgreSQL should be solved in a complex, considering both possible risks, and technical features of work of 1C in each case. Audit of a system and testing of work with a new DB should be the beginning of such transition.