What does it mean that Quickbase is single threaded ?
Is this single threaded nature by App (or by instance?) or quickbase in it's entirety ?
Forum Discussion
... let me think for a moment.
YES YES YES YES YES YES YES YES :)
Once you get the knack of these sync tables they are super quick to setup. Be sure to use a robot type system userid as the Sync will die when you do - or when you lose access to the app, so I suggest that you have a generic userid for the Sync.
It is also often a better user experience anyways to say bring in a nice table of Customers instead of just that cross app lookup. Often a user may want to look at a customer record and see an embedded child table of their detail records being processed by the app.
Sync tables are "best practice". They did not exist a couple of years ago, but now that they exists, yes that is what you want to do. They are Quick Base's main answer to avoiding eco-systems of connected and hence performance challenged apps. Also, when a Sync table is updating, say every hour, they seem to have them tuned to not impact performance at all. The must run as low priority "end of the queue" in the single threaded queue vs real users working with an app to run reports or process records.
YES YES YES YES YES YES YES YES :)
Once you get the knack of these sync tables they are super quick to setup. Be sure to use a robot type system userid as the Sync will die when you do - or when you lose access to the app, so I suggest that you have a generic userid for the Sync.
It is also often a better user experience anyways to say bring in a nice table of Customers instead of just that cross app lookup. Often a user may want to look at a customer record and see an embedded child table of their detail records being processed by the app.
Sync tables are "best practice". They did not exist a couple of years ago, but now that they exists, yes that is what you want to do. They are Quick Base's main answer to avoiding eco-systems of connected and hence performance challenged apps. Also, when a Sync table is updating, say every hour, they seem to have them tuned to not impact performance at all. The must run as low priority "end of the queue" in the single threaded queue vs real users working with an app to run reports or process records.