No. We have done rigorous performance testing on our solution. In a simulated production test environment where we created and/or updated over 1,400 orders in one hour, we were unable to detect an impact on performance. As for space concerns, our booking transaction history table typically usually has 1.1 to 1.3 times the number of rows in your order lines table. Since it contains significantly fewer columns than the order lines table, it usually remains smaller in physical size than the order lines table. Our customers have never had transaction history performance or disk space problems.