Http://topic.csdn.net/t/20040317/11/2852242.html
| SQL Server2000 can only use 5% of Xeon CPU resources |
Server: hpdl380 cpu2.8 memory 1.0 GB operating system w2k SQL Server2000 + SP3 test a stored procedure for SQL Server2000 ON THE hpdl380 server. It takes more than 10 minutes to insert 0.1 million records. the CPU usage does not exceed 5%. It takes 35 seconds to insert 0.526 records in PC (p42.0, 0.1 million GB memory operating system w2k SQL Server2000 + SP3. the CPU usage exceeds 50%. server adjustment: 1. the problem of disabling hyper-threading (which took more than 10 minutes) was not solved. 2. The problem of uninstalling SP4 (taking more than 10 minutes) has not been solved. 3. The remote service of the server is not installed. Please advise how to adjust the server or SQL Server 0.1 million to solve the problem that it takes more than 10 minutes to insert records.
| Author: anonymous posting time: |
| Author: anonymous reply date: |
| Author: anonymous reply date: |
Enterprise Manager -- select a registered instance (usually a computer name) -- Right-click -- properties -- processor to check. In general, the system is optimal. Check whether your machine has any worms. In terms of symptoms, your processor seems to be occupied by other processes, not necessarily SQL Server, go to the task manager and check whether there are any abnormal processes.
| Author: anonymous reply date: |
Agree to the upstairs: Enterprise Manager -- Right-click your instance -- properties -- processor to see if the settings of the two computers are different. Generally, do not set them by yourself.
| Author: anonymous reply date: |
SQL Server properties (processor tab) use this tab to view or specify the following options. Option processor specifies the processor that you want the Microsoft SQL server instance to use. The maximum worker thread specifies the maximum number of available worker threads of the SQL server process. Improve the priority of SQL Server on Windows to specify whether the SQL server instance should have a higher priority than other processes running on the same computer. The default value is 0, and the priority base is 7. If this option is set to 1, SQL Server runs with priority 13 in the Microsoft Windows NT 4.0 or Windows 2000 scheduler. We recommend that you change the default value only on Windows NT 4.0 or Windows 2000 for SQL Server. Use a Windows NT fiber to specify that the SQL server instance uses a fiber instead of a thread. In a thread, SQL Server assigns a thread to each CPU, and then assigns a fiber thread to each concurrent user until the max worker threads value is reached. This setting takes effect after the server is restarted. Use all available processors to specify that SQL server uses all available processors for parallel query. Use the number of processors to specify the number of processors that you want SQL Server to use for parallel query execution. Specify the thresholds for SQL Server to create and execute parallel plans for the minimum query plan threshold values that must be met for concurrent queries. SQL Server will create and execute a parallel plan for the query only when the estimated execution cost of the serial plan for the same query is higher than the set value of this option. View or change the configuration values of the options on this tab. If you have changed these values, click "Run value" to check whether the change has taken effect. If the change does not take effect, you must restart the SQL server instance for the change to take effect. Run value view the current run value of the option on this tab. These values are read-only values.
| Author: anonymous reply date: |
The SQL Server of the two machines is configured by default and should not be a worm. The priority of the process is 7 in the latest version and has not been adjusted. The test on another Xeon CPU P3 machine cannot exceed 5%. Depressed !!!
| Author: anonymous reply date: |
Today, I had to move SQL-server to any PC (p42.0, memory 0.526 GB) for the time being, which is much better than hpdl380. I want to reinstall the hpdl380 operating system. Load SP2 and test it. Load SP3 and test it. It is said that the above problem is related to SP4. I installed and uninstalled SP4 through overwriting, and some conflicting settings may be kept internally. Implementation at night
| Author: anonymous reply date: |
It turns out to be a server defect. The dl380 should load a disk read/write cache or select accessories. Thanks !!!! According to a test by the HP service provider loading an accessory on the server, it was found that it would take 28 seconds to run the stored procedure of inserting 0.1 million records from the SQL Server database (CPU usage reaches 100%) on the server ), the number of records read is 17 seconds. Currently, the number of records read is less than 1 second. Read/write performance is greatly improved.
| Author: anonymous reply date: |
