Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Applied Architecture Patterns on the Microsoft Platform

You're reading from   Applied Architecture Patterns on the Microsoft Platform An in-depth scenario-driven approach to architecting systems using Microsoft technologies

Arrow left icon
Product type Paperback
Published in Sep 2010
Publisher Packt
ISBN-13 9781849680547
Length 544 pages
Edition 1st Edition
Arrow right icon
Toc

Table of Contents (26) Chapters Close

Applied Architecture Patterns on the Microsoft Platform
Credits
Foreword
About the Authors
About the Reviewer
1. Preface
1. Solution Decision Framework FREE CHAPTER 2. Windows Communication Foundation and Windows Workflow 4.0 Primer 3. Windows Server AppFabric Primer 4. BizTalk Server Primer 5. SQL Server and Data Integration Tools Primer 6. Windows Azure Platform Primer 7. Simple Workflow 8. Content-based Routing 9. Publish-Subscribe 10. Repair/Resubmit with Human Workflow 11. Remote Message Broadcasting 12. Debatching Bulk Data 13. Complex Event Processing 14. Cross-Organizational Supply Chain 15. Multiple Master Synchronization 16. Rapid Flexible Scalability 17. Low-Latency Request-Reply 18. Handling Large Session and Reference Data 19. Website Load Burst and Failover 20. Wrap Up

Chapter 12. Debatching Bulk Data

Debatching data is the process of turning one huge pile of data into many small piles of data.

Why is it better to shovel one ton of data using two thousand, one pound shovels instead of one big load from a huge power shovel? After all, large commercial databases and the attendant bulk loader or SQL Loader programs are designed to do just that: insert huge loads of data in a single shot.

The bulk load approach works under certain tightly constrained circumstances. They are as follows:

  1. 1. The "bulk" data comes to you already matching the table structure of the destination system. Of course, this may mean that it was debatched before it gets to your system.

  2. 2. The destination system can accept some, potentially significant, error rate when individual rows fail to load.

  3. 3. There are no updates or deletes, just inserts.

  1. 4. Your destination system can handle bulk loads. Certain systems (for example, some legacy medical systems or other proprietary systems) cannot handle...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime