CMDEXEC job PRIORITY

  • I have a visual basic executable that I scheduled to run from within SQLAgent. The job ran successfully except that it was running very slow( 1 hour to write out 100K records). All the vb app is doing is reading records from a table and writing them to a file( I know this can probably be done another way that is not the answer I am looking for) I took the same vb app and scheduled it to run using the scheduled tasks and the process ran to completion within 10 minutes for the creation of the same file. I have not found out why this would occur. Are there any settings within SQLAgent that I need to make to give jobs running a higher priority I don't know? Any input would be appreciated. Thanks

  • You can't do anything specifically with SQLAgent. What you can do, however, is have SQLAgent call a batch file that calls the VB program. I believe this gets around the priority issue.

    K. Brian Kelley

    http://www.truthsolutions.com/

    Author: Start to Finish Guide to SQL Server Performance Monitoring

    http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1

    K. Brian Kelley
    @kbriankelley

  • You can execute the file directly from a job (with the type set to Operating System Command):

    start /normal <file_name> <parameters>

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply