Server choice: operating system, database and files
To select "operatsionka" for the server – it isn't simple, and it is very difficult: to each argument "into plus" many can bring argument and "into a minus". Therefore it is necessary to understand in the beginning in details – for what such applications you want such or other operating system? OS for servers often conditionally break into three raznomoshchny classes: Statistics of service Netstat.ru on Web servers says that about 32% from them work with Linux OS, about 44% - with FreeBSD OS, about 12% - with Windows OS (remaining - "who in what"). – there is a lot of factors influencing such choice, for example, in favor of Windows or FreeBSD the price speaks. The server with an operating system – the tool, both for operation, and for framing and implementation of strategy of the company, the enterprise that can't but affect level of corporate operation. The positive side of Windows is possibility of integration with a wide choice of applications from Microsoft. If it is a company Web server where already corporate network (the intranet network functions or even local area networks) with servers clients under Windows, nevertheless it is reasonable to put on the Windows OS server. It is possible to turn it into powerful tools if to use the technologies.NET, ActiveX, MS SQL and others. The Windows operating system evolves, becomes high-productive. Besides, it is customary for the organizations where there is a rational conservative approach, for example, on traditions of Windows NT. Up-dating of system both is expensive, and it is "psychologically unpleasant" for ordinary employees who don't want to investigate into additional settings and possibilities of OS. "Old OS – the best" is often equivalent "old OS I know" better. At UNIX systems – possibility of remote administration (telnet and ssh utility) that isn't present (directly) in Windows if the server and the client aren't in one network is positive. At UNIX-like OS low cost, possibility of remote administration and high safety, absence of division into the user and server OS impresses. For example, processing any advanced query, the client application will receive only necessary for it one data sampling. All intermediate processing will be executed thus by the server. In case of such effective distribution of computation between "a server layer" and "a client layer" the maximum productivity (throughput) of system without additional financial attachments in hardware-software extension that is important when you make a server choice for SQL and appropriate support can be reached. "1С:Предприятие 8" can work with different versions of SQL servers. But nevertheless SQL-2000 is recommended with later versions, at least, to PostgreSQL (propatchenny), etc. Structure of tables of databases both "file", and the "client server" version of 1C system almost match. But thus (in early versions especially) there could be some "braking" of system – because in case of modification of the table one client, this table can be locked for others. Besides, SQL queries by "feeble" client machines (the minimum configuration) difficult or can't often be processed. Such machines don't suit for productive work with the powerful server: or the processor of the server stands idle, or it all the time is occupied as the input-output processor. Unbalanced operation is got not only the server processor, but also disk memory – data from the server are activated through a hard drive of the client. The three-level architecture of the new version of the environment, also tries to solve this problem. "Braking" or aren't present, or it isn't noticeable for the client. In case of "blamestorming session" of the environment it is necessary to consider not only possibilities of the server, and first of all, possibilities of clients. The server choice for SQL by operation in "1С:Предприятие 8" effectively shall consider possibilities of the SQL server in case of execution of different procedures (reading, record, transfer, search, sorting, calculations, filling of tables, report generation, etc.) and the data volume, transferred to the computer of the client shall be directed on reduction of loading by a client cluster at the expense of abbreviation. It is important to consider thus throughput and time of response of system (peak intensity and a simultaneity of operation of users at all levels – including expected values). Especially it is important for an assessment of a random access memory and number of processors. For example, the Standard Edition doesn't support more than four processors and two Gb of memory. More resources are provided by the Server Enterprise Edition version. How to store data, files and where it is safe to store them if them is great variety, and they – "entirely valuable information"? Sentences "to buy a place on the server for storage of files" - also there is a lot of. But it is necessary to remember that good free or cheap doesn't happen, and "free cheese – only in a mousetrap". It is necessary to remember the following basic principles of search of service, selecting the server for storage of files and then it using: There is a mass of servers for files. Each server for storage of files has "pluses" and "minuses". From mass of existing servers (services) it is possible to mark the following (the list both incomplete, and not ranged): There is a set of other services. It is necessary to mark two quite similar: Файлы@mail.ru (one file – to 1 Gb, all files – to 10 Gb, 3 months of storage) from of the same name
