D
D
dlevchenko2011-06-23 21:56:57
1C
dlevchenko, 2011-06-23 21:56:57

Choosing hardware for SQL Server 1C

Friends, I ask for your advice.

There is currently one server (Intel Xeon X3430 2.4 Ghz CPU, 4 GB RAM) that assumes the format structure:
Windows 2008 Server 64x,
Terminal Server,
1C Enterprise 8.2 Enterprise Management.
with the number of 1C clients in the region of 20.

There is an idea to purchase a 2nd server on which I will store 1C databases in SQL.
Can you at least push on the right path, what kind of server is needed for such a purpose?

And by how much is it necessary to expand the number of operatives on the 1st server?

Answer the question

In order to leave comments, you need to log in

8 answer(s)
M
mobileDeveloper, 2011-06-24
@dlevchenko

Recently they took a server, just under 1C.
As mentioned above, use counters, you need to monitor the load on memory, disks, processor, network interface, paging file access. It is necessary to collect information periodically, constantly monitor changes in indicators - it will be very useful later, for analyzing and solving problems with bottlenecks.
In your case, with a 0.5 GB database, the existing server should suffice.
In case of significant growth, it is necessary to think over everything in advance.
In our organization, the database has grown from 20 to 70 GB in 2 years, the number of users from 25 to 50 simultaneously working.
Based on experience and meter readings:
- the processor is very rarely heavily loaded and it will hardly be a bottleneck, I can only say that it is more profitable to choose one 4-core, instead of two 2-core ones due to the MS SQL licensing scheme for the processor, if the DBMS is different, then consider it yourself, by money;
- network interface, sometimes it is loaded significantly, but so far it has not been a bottleneck, 2 gigabit interfaces are enough;
- memory, here, as always, there is not much of it, and now it is relatively inexpensive, plus all 64-bit server software (OS, DBMS, SCP);
- the biggest plug in the disk subsystem, the greatest load on it, so for large volumes, choose the fastest RAID type, not forgetting about reliability (we have Raid 10). As advised above, we chose an SSD - it's quite expensive, in addition, these disks tend to die quickly, so a mandatory reserve in case of failure, but these disks give many times higher speeds on random read and write operations, overtaking any HDD . Also, do not forget to spread the databases and logs to different raid volumes, and remember about tempdb in MS SQL.
With an increase in the number of simultaneously working users, the problem of locks at the level of database tables will come to the fore. It's probably too early for you to think about it.
I recommend you read it once or twice .

A
alex_dredd, 2011-06-24
@alex_dredd

1. It is desirable that the entire SQL database fits into the server's RAM
2. In order to avoid slowdowns due to a "slow" network, it is desirable to connect the terminal and the database server directly with a patch cord through gigabit network cards. And register in the 1Sky settings the IP address of the SQL server network card, which looks directly into the terminal.

M
max_rip, 2011-06-24
@max_rip

under the first which under a DB consider so that all base was located in the opera.
And the second, somewhere it is written how much one terminal bites off + you can see how much 1s bites off and add up everything that is.

A
Alexander Starostin, 2011-06-24
@al1k

1C is very fond of memory, especially SCP. It is worth considering 16GB or more. At least 500 MB per client, otherwise it will be sad.
about SQL already answered.

P
pel0tkin, 2011-06-24
@pel0tkin

> at the moment the base is 0.5 GB
I had a DELL PowerEdge 1950 2xXeon 2.8GHz/8GB DDR2/4xSAS 147GB in RAID1+0/Win2003 at one of my workstations. It ran
a terminal server (~30 users online) and 1C TIS+ Accounting (.DBF) with huge databases for several years. The processor load rarely exceeded 30% and it was decided to install spare parts catalogs for car service on it, which are quite heavy (one Tecdoc has a database of more than 10 gigabytes!) And even after that, the load did not exceed 50%
Similar pieces of iron are no longer so expensive, but their productivity is enough with a margin.

C
Cher, 2011-06-24
@Cher

I don’t know what kind of load on SQL in 1C, but if there is a lot of write, see if the disk becomes a bottleneck. An SSD is highly recommended. There are all sorts of space SSDs on a PCI slot like www.nix.ru/autocatalog/ssd_ocz/OCZ_OCZSSDPX1RVD0110_Revo_Drive_PCIExpress_SSD_110_PCIEx4_MLC_116403.html

D
dlevchenko, 2011-06-24
@dlevchenko

Thanks everyone for the replies. We'll keep thinking.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question