![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 4 of 4 total |
![]() |
Fri, Nov 21 2008 1:09 PM | Permanent Link |
Dale Derix | I know that transactions are ideal for making sure that a group of inserts, updates, or deletes is handled as a whole. For instance, when posting an order to make sure that all related tables are updated together. But suppose I'm importing 50,000 records. Can I use a single transaction to handle the entire import? (ie: either import them all, or if there's a problem, import none of them). Thanks, Dale |
Fri, Nov 21 2008 1:34 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Dale,
<< But suppose I'm importing 50,000 records. Can I use a single transaction to handle the entire import? (ie: either import them all, or if there's a problem, import none of them). >> For 50,000 rows, yes. For 1,000,000 rows, you'll probably want to break things up a bit. I would say that the cut-off point for the largest transaction is around 200,000 rows. Anything larger than that, and you'll want to investigate using multiple transactions. -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Apr 16 2009 6:58 PM | Permanent Link |
Dale Derix | Tim Young [Elevate Software] wrote:
> Dale, > > << But suppose I'm importing 50,000 records. Can I use a single transaction > to handle the entire import? (ie: either import them all, or if there's a > problem, import none of them). >> > > For 50,000 rows, yes. For 1,000,000 rows, you'll probably want to break > things up a bit. I would say that the cut-off point for the largest > transaction is around 200,000 rows. Anything larger than that, and you'll > want to investigate using multiple transactions. > Tim, What is it that becomes an issue after around 200,000 rows. In otherwords, how will I know when I've hit the limit? Thanks, Dale |
Fri, Apr 17 2009 2:13 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Dale,
<< What is it that becomes an issue after around 200,000 rows. In otherwords, how will I know when I've hit the limit? >> You start to hit a point of diminishing returns where the buffering overhead costs more and more processing time. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Wednesday, August 14, 2024 at 03:12 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |