Posting Routines Post Consecutively For One Database V. Separately Posting Routines For One Database
I would like to request that the option be given to customers as to how SmartPost posts the routines. We would prefer SmartPost see and post all routines for one database at once (not meaning the routines post all at the same time but within seconds of each other as opposed to 30 minutes – 1 hour between each routine). This feature was omitted some time after SmartPost 20.11.3.65. I am requesting that the development team give customers the option of how they would like to post the routines (e.g. each routine separately for all databases or each routine together for one database).
We have 210 databases to which we post via SmartPost. We currently have four routines on SmartPost 20.15.02.12. Under the old version (20.11.3.65), SmartPost would see all routines in one database and post them each at that time. Under the newer version, one routine runs for all 210 databases before it moves to the next routine; it takes approximately 45 minutes – 1 hour to run through one routine. Under our current version, we could run through all databases and all routines within 45 minutes – 1 hour. Our runtime under the newer version of SmartPost now takes us 3 – 4 hours, 4 times as long. This is inefficient for us and nearly defeats the efficiency of using SmartPost. Your escalation of this matter would be greatly appreciated. Thank you!
We have 210 databases to which we post via SmartPost. We currently have four routines on SmartPost 20.15.02.12. Under the old version (20.11.3.65), SmartPost would see all routines in one database and post them each at that time. Under the newer version, one routine runs for all 210 databases before it moves to the next routine; it takes approximately 45 minutes – 1 hour to run through one routine. Under our current version, we could run through all databases and all routines within 45 minutes – 1 hour. Our runtime under the newer version of SmartPost now takes us 3 – 4 hours, 4 times as long. This is inefficient for us and nearly defeats the efficiency of using SmartPost. Your escalation of this matter would be greatly appreciated. Thank you!