April 26, 2015 at 6:16 pm
We've recently upgraded to SQL Server 2014, and are now using SSIS integrated with Visual Studio. We have a SSIS project which contains about 20 packages which are nested in Sequence Containers and executed concurrently. These packages have been set up as project references.
The problem is that when I press the start button to run the packages, they all light up green reporting completion before the data has finished loading into the SQL database. If I press the stop button without waiting a sufficient length of time, then not all of the data gets loaded. i.e. a certain number of rows will be missing from some of the SQL tables.
If I click through to the individual package items and check the data flow progress while running, some of the data flows appear to hang at a certain number of rows without ever reaching completion. The number of rows indicated in the data flow is incorrect - i.e. it will count up to ~150,000 and stay there indefinitely in the running state, when in actual fact there are ~500,000 rows to load.
To clarify, the main package will show all items green and display the "Finished: Success" message in the log window, however when I drill through to certain packages in the set, they'll be stuck in the yellow running state, with no way of knowing whether they've actually completed or not.
My current workaround is to just wait a certain length of time before pressing the stop button. This bug doesn't seem to inhibit rows being loaded - it just incorrectly identifies the point when the load finishes, causing people to terminate the load prematurely.
This issue only occurs if I run the project from the main package container. If I execute the child packages individually, they correctly report the number of rows being loaded and light up green once complete.
Can anyone tell me what's going on? This seems like a pretty serious bug in the SSIS software which undermines our ability to use it as a business tool.
April 26, 2015 at 9:58 pm
Quick question, have you tried to run the packages with the dtexec Utility?
😎
I suspect that this may be a quirk in the Visual Studio interface, certainly you don't intend to run the packages from there as a part of a production process?
May 5, 2015 at 4:14 pm
Eirikur Eiriksson (4/26/2015)
Quick question, have you tried to run the packages with the dtexec Utility?😎
I suspect that this may be a quirk in the Visual Studio interface, certainly you don't intend to run the packages from there as a part of a production process?
We've always run it from there in the past, but I can try alternative methods
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply