SQL Server Agent jobs seems to be running in parallel by 2 separate accounts

Naomi Nosonovsky 8,431 Reputation points
2023-06-09T16:01:01.5833333+00:00

Hi everybody,

In our SQL 2019 Stage server we have SQL Server jobs running. Recently I started to observe this strange behavior - 2 of the extracts started to run in parallel. The problem is that once the extracts finish running, they re-run again for all regions but one resulting in incorrect data and file sizes. I'm trying to investigate a reason for this strange behavior and I see two separate accounts changing the extract detail records. I just don't understand what may suddenly cause this behavior in our SQL Server. Do you have any ideas what may cause this problem and how to make sure that the SQL Agent job runs under 1 account only and not in parallel by 2 accounts?

The job in question (although the same issue exists for another job) consists of 2 steps being run using the command similar to this

dtexec.exe /FILE E:\SSIS_ROOT\VA\package\Main_Extract.dtsx /SET "\package.variables[User::varJobNbrToProcess].Properties[Value]";33 /MAXCONCURRENT 1 /CHECKPOINTING OFF /REPORTING V

Thanks in advance.

SQL Server | Other
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. ZoeHui-MSFT 41,491 Reputation points
    2023-06-12T06:44:03.0833333+00:00

    Hi @Naomi,

    You may Configure a User to Create and Manage SQL Server Agent Jobs.

    By default, members of these database roles can create their own job steps that run as themselves. If these non-administrative users want to run jobs that execute other job step types (for example, SSIS packages), they will need to have access to a proxy account.

    Regards,

    Zoe Hui


    If the answer is helpful, please click "Accept Answer" and upvote it.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.