Home Dashboard Directory Help
Search

A keep-running CmdEXEC job will block the scheduled SSIS job in SQL Agent by v-xiaowy


Status: 

Active


1
0
Sign in
to vote
Type: Bug
ID: 863300
Opened: 4/28/2014 11:55:12 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

I scheduled the SSIS job to run every 10 second. It worked fine. But if I start a CmdEXEC job which will keep running for a long time, the SSIS job will not start running as scheduled again. No more job history of SSIS job, no error message, even no event log. If I stop the SSIS job and start it manually, it will be keep running.
There is no connection between the two jobs, nor common resource.
Details
Sign in to post a comment.
Posted by v-xiaowy on 7/6/2014 at 10:11 PM
A recent test gave me some clues, if I use Console.ReadLine() to keep the CmdEXEC job running, it will block SSIS job, but if I loop Thread.Sleep(1000), it won't. So, try to read from Console is the key to this problem. But, I can't make my work thread sleep. Can't you resolve this problem?
Posted by Sethu Srinivasan on 7/1/2014 at 2:24 PM
Let us know if you still see this issue in SQL 2014. You can get a SQL Server 2014 Virtual machine from http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-provision-sql-server/

Thanks
Sethu Srinivasan [MSFT]
SQL Server
Sign in to post a workaround.