Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
JimWhitby
Starting Member
1 Post |
 Posted - 2012-04-09 : 07:18:18
|
| Hi,I've got a BIDS project that has multiple packages getting fired off loading in hundreds of data files. On day one of the month I want it to do a set of packages and all other days I have it doing other packages. So At the very begnining I have a simple data flow task that does a check using a conditional split, if it is day one I allow the task to continue and if it's not I cause a failure. Then from this I handle the error so that it follows another path.In BIDS this works fine but as soon as I put it into SQL Server agent it hits the error and falls over, no longer handling it as before.Is there a simple way of doing a conditional split in the control flow or is there a reason why a failure is handled neat and tidily in BIDS but not once it has been moved to SQL Server agent?This is driving me mad so any help would be much appreciated.ThanksJim |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2012-04-09 : 11:16:40
|
| why do you need to raise it as an error. why not simply put the check and if its 1st day do rest of processing, otherwise sent a notification back telling that its not 1st day as email or log it in control table------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
 |
|
|
|
|
|
Handled errors in SQL Server Agent