[SQL Server] Scheduled SSIS package not pulling all data |
Scheduled SSIS package not pulling all data Posted: 07 Aug 2013 06:16 AM PDT I have a scheduled SSIS package that is not including all information every morning into the flat file it generates. It's a really simple SSIS package. It does a data extract to a comma delimited file, renames it with the current date then it uploads the file. After that it moves it to an archive folder.It seems that 2/3's of the time it gets all the data it needs to but the other part of the time, it skips records. When I run the same script in SSMS after the fact, the results (within SSMS) are spot on but the file it created might be 5 to 15 records short. Normally there are anywhere from 20-40 records every day and it's a really simple SQL script. When running the script in SSMS it takes less than 1 second.What would be causing the script to skip over records? The filter criteria is such that it pulls on information that is never changed once it's entered into the system so I could go back and do day by day screen shots if I wanted to and running my SQL script matches perfectly with what the application shows. I'm thinking this has something to do with a bad connection or something along those lines.I went through all 15 packages that run on this server and none of them overlap. The AV scan takes place 11 hours before this script fires off. The backups take place 7 hours before this job fires off. I'm not sure what could be interfering with this SSIS package. I don't have any issues with any of the other SSIS packages on that server. The packages that pull data from our database pull complete data.Does anyone have any troubleshooting tips to suggest?TIA,John |
You are subscribed to email updates from SQLServerCentral / SQL Server 2008 / SQL Server Newbies To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
Google Inc., 20 West Kinzie, Chicago IL USA 60610 |
No comments:
Post a Comment