Does it make sense to switch from file options 1c to SQL?

Question

System administration

at the moment there is a terminal server on Windows based on two six-core processors and 64 GB of RAM. the second server - backup copies.
on the main there are about 100 databases 1c in the file version (accounting firm). bases are small, 2-5 GB, but there are two larger ones, 40GB and 60GB.
It's time to replace the disks (they can't cope with the speed of work and have worked for 5 years 24/7) and purchase an additional server.
The management plans to distribute the load between the two servers.
whether there is a sense to overtake all bases in SQL and to distribute roles between two servers?
budget 200 thousand rubles, server key is present

Answer 1

Large databases where a large size, and users of simultaneous 4-6, of course, should be transferred to SQL.
Small databases will work faster in the file version, and it is more convenient in many ways.
In general, switching to SQL makes sense when the filebase is approaching the limit of its capabilities - in terms of size or number of users. In other cases, the file option is more profitable.
As a rule, an accounting outsourcing company has no more than one user in the database, so the ideal option is a file database.
Those bases where boo. outsourcing works together with accountants at the client's primary office, usually placed separately.

Answer 2

File 1C does not work well in multitasking mode - that is, even two users, if they want to work not just together, but at the same time - in the file version they will greatly interfere with each other.
Talk to your accountants about how often you need to work at the same time.

Answer 3

If more than one person works with the database at the same time, then it is better to switch to SQL.