Does anyone have any knowledge, documentation or performance metrics comparing accessing SQL Server GP tables using their Global Table Buffers versus a SQL Connection when developing Dot Net integrations?
I have used both extensively and haven't noticed any performance difference from the client perspective. Years ago I originally used SQL Connections exclusively but we started have connection timeouts (not related to the integration) and I recoded things to use Table Buffers whenever possible. We are looking at developing a new integration and since any non-GP tables cannot use the Table Buffers anyway we are considering using SQL exclusively to access even the GP tables.
I'm interested if anyone has information on how SQL Server is impacted between these two methods or if they have sound reasoning to use Table Buffers whenever possible. With SQL Connection pooling I can't imagine the overhead of new connections is an issue and am just thinking that Global Table Buffers would have no advantage then.
Thank you.
