SQL Server Performing too bad when a SQL Job Executes On Schedule.

  • Hi , 
    I have a SQL Job which is hooking up an sps pulling data from the table/s which is having billions of rows.
    When the Job gets executed and when i see the status (select   * from sys.dm_exec_requests) this allocate too much of CPU/IO to the Job/SQL-SPS 
    and hence the System Performance is badly degrade. Can somebody help me how I manage SQL Resource/ or any other way to handle this situation.

    Regards,
    VD

  • vineet_dubey1975 - Thursday, October 26, 2017 6:55 AM

    Hi , 
    I have a SQL Job which is hooking up an sps pulling data from the table/s which is having billions of rows.
    When the Job gets executed and when i see the status (select   ='mso-spacerun:yes'>* from sys.dm_exec_requests) this allocate too much of CPU/IO to the Job/SQL-SPS 
    and hence the System Performance is badly degrade. Can somebody help me how I manage SQL Resource/ or any other way to handle this situation.

    Regards,
    VD

    We're going to need more detail.   What do you mean by "hooking up an sps" ?  Are you referring to a stored procedure that accesses the multi-billion row table?   If you are, please post the CREATE TABLE statements for all the tables the stored procedure (aka "sp" or "sproc") references.  Then identify what if any indexes are in place on that large table, and post the stored procedure code, and someone can probably help.   There are no "generic" solutions to performance problems.   The first thing you need to know is what's causing the problem.   In this case, if you ARE talking about a stored procedure, then please also post the execution plan, as that will give us a much better idea of what's going on.

    Steve (aka sgmunson) 🙂 🙂 🙂
    Rent Servers for Income (picks and shovels strategy)

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

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