Beginning Microsoft SQL Server 2008 ... - S3 Tech Training
Beginning Microsoft SQL Server 2008 ... - S3 Tech Training Beginning Microsoft SQL Server 2008 ... - S3 Tech Training
Chapter 18: Getting Integrated with Integration Services Figure 18-16 Cancel out of all the dialogs to leave things as they were when we completed the wizard. Event Handlers 556 Moving over to the Event Handlers tab, we can see the many events that we can supply code for. Activate the drop-down (as I have in Figure 18-17). While the default is OnError, we can deal with a very wide range of scenarios. Let’s examine how a few of these might be used: ❑ OnError: Well, I would hope that this is the most obvious one. As you would expect, this event is fired in the event an error is detected. It allows you to address the error in some fashion. ❑ OnWarning: Basically the same as OnError, but it allows you to examine and possibly address warnings too. ❑ OnProgress: For long running processes, this can be handy for updating some form of progress indicator (perhaps a status table somewhere). ❑ OnPreExecute: Allows for things like preparation code to run prior to starting the main part of the task. And this is, of course, just a taste. What events to use will vary by need.
Figure 18-17 Package Explorer This is, again, one of those things that is what it sounds like. Much like Windows Explorer is a way to explore your file system in a folder-based paradigm, the Package Explorer allows you to explore the package in a similar paradigm. In Figure 18-18, I’ve expanded a few of the folders to give you a feel. Figure 18-18 Chapter 18: Getting Integrated with Integration Services 557
- Page 544 and 545: Chapter 16: A Brief XML Primer Chec
- Page 546 and 547: Chapter 16: A Brief XML Primer 508
- Page 548 and 549: Chapter 16: A Brief XML Primer 510
- Page 550 and 551: Chapter 16: A Brief XML Primer 512
- Page 552 and 553: Chapter 16: A Brief XML Primer The
- Page 554 and 555: Chapter 16: A Brief XML Primer 516
- Page 556 and 557: Chapter 17: Reporting for Duty, Sir
- Page 558 and 559: Chapter 17: Reporting for Duty, Sir
- Page 560 and 561: Chapter 17: Reporting for Duty, Sir
- Page 562 and 563: Chapter 17: Reporting for Duty, Sir
- Page 564 and 565: Chapter 17: Reporting for Duty, Sir
- Page 566 and 567: Chapter 17: Reporting for Duty, Sir
- Page 568 and 569: Chapter 17: Reporting for Duty, Sir
- Page 570 and 571: Chapter 17: Reporting for Duty, Sir
- Page 572 and 573: Chapter 17: Reporting for Duty, Sir
- Page 574 and 575: Chapter 17: Reporting for Duty, Sir
- Page 576 and 577: Chapter 17: Reporting for Duty, Sir
- Page 578 and 579: Chapter 17: Reporting for Duty, Sir
- Page 580 and 581: Chapter 17: Reporting for Duty, Sir
- Page 582 and 583: Chapter 18: Getting Integrated with
- Page 584 and 585: Chapter 18: Getting Integrated with
- Page 586 and 587: Chapter 18: Getting Integrated with
- Page 588 and 589: Chapter 18: Getting Integrated with
- Page 590 and 591: Chapter 18: Getting Integrated with
- Page 592 and 593: Chapter 18: Getting Integrated with
- Page 596 and 597: Chapter 18: Getting Integrated with
- Page 598 and 599: Chapter 18: Getting Integrated with
- Page 601 and 602: 19 Playing Administrator And so, he
- Page 603 and 604: ❑ Write the information to the ev
- Page 605 and 606: Creating Jobs and Tasks Using Manag
- Page 607 and 608: Let’s go ahead and move on to the
- Page 609 and 610: Figure 19-8 Figure 19-9 Chapter 19:
- Page 611 and 612: Figure 19-11 Figure 19-12 Chapter 1
- Page 613 and 614: Backup and Reco very No database-dr
- Page 615 and 616: ❑ Differential: This might be ref
- Page 617 and 618: ❑ Simple: Under this model, the t
- Page 619 and 620: The older DBCC commands are still s
- Page 621 and 622: many rows inserted over time and th
- Page 623: Chapter 19: Playing Administrator T
- Page 626 and 627: Appendix A: System Functions In add
- Page 628 and 629: Appendix A: System Functions @@TOTA
- Page 630 and 631: Appendix A: System Functions CHECKS
- Page 632 and 633: Appendix A: System Functions SUM Th
- Page 634 and 635: Appendix A: System Functions The de
- Page 636 and 637: Appendix A: System Functions @@REMS
- Page 638 and 639: Appendix A: System Functions Cert_I
- Page 640 and 641: Appendix A: System Functions Encryp
- Page 642 and 643: Appendix A: System Functions @@FETC
Chapter 18: Getting Integrated with Integration Services<br />
Figure 18-16<br />
Cancel out of all the dialogs to leave things as they were when we completed the wizard.<br />
Event Handlers<br />
556<br />
Moving over to the Event Handlers tab, we can see the many events that we can supply code for. Activate<br />
the drop-down (as I have in Figure 18-17). While the default is OnError, we can deal with a very<br />
wide range of scenarios. Let’s examine how a few of these might be used:<br />
❑ OnError: Well, I would hope that this is the most obvious one. As you would expect, this event<br />
is fired in the event an error is detected. It allows you to address the error in some fashion.<br />
❑ OnWarning: Basically the same as OnError, but it allows you to examine and possibly address<br />
warnings too.<br />
❑ OnProgress: For long running processes, this can be handy for updating some form of progress<br />
indicator (perhaps a status table somewhere).<br />
❑ OnPreExecute: Allows for things like preparation code to run prior to starting the main part of<br />
the task.<br />
And this is, of course, just a taste. What events to use will vary by need.