The sproc is used by the EPiServer scheduler. However it certainly shouldn't hog 50% of the DB resource! You can try stopping the EPiServer Scheduler service to see if that stops the issue.
I Turned off the scheduler, set all running jobs to 0 in the database (I think there were, among others, 5-6 EPiServer.Util.IndexPageJobs running since last year) then restarted IIS and turned the scheduler back on. Now the test environment takes next to nothing on the dabase, which is really great.
Thank you for your reply
We have two environments with EPiServer CMS 6 R2, one for production and one for test. The problem is that our test-environment hogs the database and compared with our production environment the load from our test takes 50% of all database-server resources.
I've managed to track the high load to a stored procedure called netSchedulerList in the episerver database. But now I wonder why this stored procedure takes more resources on our test environment rather than our production environment.
Which part in EPiServer is executing this stored procedure?