I would suspect that it's the rollback that's taking the additional time. I would suggest you do the consistency checks first before starting the import process. -Eric Isaacs
Thread: SSIS Packages fail, but takes a LONG time to end  |
|||||||||||||
|
Started 1 month, 1 week ago by Ron Ruble
We have a number of SSIS Packages that can fail with bad data from external sources. We handle the bad data without an issue, but after the package logs that an error occurs and it is failing, they often take a VERY long time to end. I'm talking about a package that normally takes 5 minutes, logging a failure, then taking an HOUR to end. This is getting to be a significant problem for us, ...
|
|
||||||||||||
|
|||||||||||||
Other posts in this thread:
Eric Isaacs replied 1 month, 1 week ago
Size: 202 bytes
Customize: 
Charles Wang [MSFT] replied 1 month, 1 week ago
Ron, Rolling back on thousands of rows may also cause a lot of time waiting for the locks from other operations on the table. I recommend that you refer to the following two KB articles to monitor if there are blocking issue on your server: How to monitor blocking in SQL Server 2005 and in SQL Server 2000 http://support.microsoft.com/default.aspx/kb/27150 9 INF: Understanding and resolving ...
Size: 585 bytes
Customize:
Ron Ruble replied 1 month, 1 week ago
I'd love to. But the prolem is the data isn't internally inconsistent. It's being pushed to an external source that uses proprietary triggers and stored procs to compare against rules internal to that system. We can, and have, checked the data to the extent that we can. But we can't peek inside this external system.
Size: 348 bytes
Customize:
Ron Ruble replied 1 month, 1 week ago
On Nov 16, 1:04 am, chang...@online.microsoft.com ("Charles Wang [MSFT]") wrote: > Ron, > Rolling back on thousands of rows may also cause a lot of time waiting for [quoted text clipped - 6 lines] > Best regards, > Charles Wang
Size: 1,708 bytes
Customize:
Charles Wang [MSFT] replied 1 month ago
Ron, For such kind of performance related issues, it is hard for us to give a specific answer immediately due to lack of enough information at the community. In most cases, we try to give some directions for helping customers manually troubleshoot the problem at his side in the community. For this issue, since the data sources and destinations are not SQL Server, SQL Server Profiler will ...
Size: 1,045 bytes
Customize:
Ron Ruble replied 3 weeks, 1 day ago
Comments inline On Nov 18, 5:41 am, chang...@online.microsoft.com ("Charles Wang [MSFT]") wrote: > For this issue, since the data sources and destinations are not SQL Server, > SQL Server Profiler will not help in this case.
Size: 14 kb
Customize:
|
Top contributing authorsRelated threads on "SQL Server Forum":Related threads on other sites: |
||||||||||||
Thread profile page for "SSIS Packages fail, but takes a LONG time to end" on http://www.sqlmonster.com.
This report page is a snippet summary view from a single thread "SSIS Packages fail, but takes a LONG time to end", located on the Message Board at http://www.sqlmonster.com.
This thread profile page shows the thread statistics for: Total Authors, Total Thread Posts, and Thread Activity
Home |
About Us |
Submit Your Site |
Update Your Site |
Get Search For Your Site |
Partners |
Contact |
Search Plugin |
Blog |
 |
Last Searches | Top Searches |
Designated brands and trademarks are property of their respective owners.
Use of this website constitutes acceptance of BoardReader's User Agreement and Privacy Policy.