Job refuses to run after the 8th job

[chaoma]

Hello,

Microsoft SQL 2000 Server Agent refuses to run after the 8th jobs already running. Is anyone know how to overcome this limitation.

I am using Windows XP, MS SQL 2000 Personal Edition.

Thanks

 

[SQLBill]

You may not like the answer. You need to upgrade your version. Personal Edition only allows eight connections and each job is a connection. One job must finish AND close its connection before a 9th job can start.

-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875

 

[SQLBill]

This is another issue with PE and MSDE versions:

A concurrent workload governor limits the performance of the database engine in these two editions. The performance of individual Transact-SQL batches is decreased when more than five batches are executed concurrently. The amount each batch is slowed down depends on how many batches over the five-batch limit are executing concurrently, and the amount of data retrieved by the individual batches. As more batches are executed concurrently, and as more data is retrieved by each batch, the more the governor slows down the individual batches. You can use the DBCC CONCURRENCYVIOLATION statement to report how often the concurrent workload governor is activated. For more information, see DBCC CONCURRENCYVIOLATION.


Ref: Books OnLine - SQL Server 2000 Databases on the Desktop

-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875

 

[chaoma]

Thank you Bill. I cannot upgrade. Windows XP only like PE.