Database instant file initialization - enabling this option speeds up
Posted: Wed Jan 22, 2025 10:32 am
After launching the program, a connection request will appear and here you can select one of the connection methods: use the login + password SA pair (set when installing the MS SQL kernel), or Windows account authentication. After selecting an option, click "Connect": Optimizing MS SQL for working with 1C That's it - installation of MS SQL components is complete. Now we have everything we need for the client-server version of the 1C database. Next: we will place the database on the server and configure MS SQL for optimized operation. Create a database on the server In the 1C start window, click "Add" - "Create a new information base" - specify a name and select "On the 1C:Enterprise server" - fill in the fields to add the database on the 1C server and in MS SQL: After filling in the data, click "Next" and "Done".
Now our database is used in mexico phone number list client-server mode. Optimization steps First of all, if the 1C server and MS SQL are located on different machines (as in our example), then you should disable the use of shared memory and switch to the TCP/IP protocol. If the location is on the same machine, then use the shared memory "Shared Memory": Also, we recommend formatting the disk file system where the DB is located in 64 KB cluster size, but there is no particular point in this if you are using SSD and the database sizes are small. For HDD - this will give a good increase in the speed of reading files in parallel. To check, you can use CrystalDiskInfo: operations on creating databases, adding files, logs and new data to existing databases + increasing the size of existing files.
To enable: Open "Local Security Policy" via "Run" (enter "secpol.msc" in the line) In the left part of the window that opens, select the node “Local Policies” → “Assigning User Rights” On the right side, select "Perform volume maintenance tasks" Click "Add User or Group" and select the user under which the MS SQL Server service is running Click "Ok" 4. "Lock pages in memory" - allows certain accounts to store data in RAM, which prevents data from being moved to disk in the system's virtual memory: To give permission, open the editor: click Start and enter "Run" and then in the field that appears → "gpedit.
Now our database is used in mexico phone number list client-server mode. Optimization steps First of all, if the 1C server and MS SQL are located on different machines (as in our example), then you should disable the use of shared memory and switch to the TCP/IP protocol. If the location is on the same machine, then use the shared memory "Shared Memory": Also, we recommend formatting the disk file system where the DB is located in 64 KB cluster size, but there is no particular point in this if you are using SSD and the database sizes are small. For HDD - this will give a good increase in the speed of reading files in parallel. To check, you can use CrystalDiskInfo: operations on creating databases, adding files, logs and new data to existing databases + increasing the size of existing files.
To enable: Open "Local Security Policy" via "Run" (enter "secpol.msc" in the line) In the left part of the window that opens, select the node “Local Policies” → “Assigning User Rights” On the right side, select "Perform volume maintenance tasks" Click "Add User or Group" and select the user under which the MS SQL Server service is running Click "Ok" 4. "Lock pages in memory" - allows certain accounts to store data in RAM, which prevents data from being moved to disk in the system's virtual memory: To give permission, open the editor: click Start and enter "Run" and then in the field that appears → "gpedit.