[dba-SQLServer] Access Connection to SQL Server (was: Upsizewizard and named queries)

Mike & Doris Manning mikedorism at verizon.net
Mon Jan 23 18:38:00 CST 2006


Access 2003 and SQL Server 2000.

Impact on the developer = none
Impact on the user = HUGE if you have a lot of data coming over at once...

In my case, my main screen contains a list of all open work orders.  Even
with a stored procedure targeting a specific set of work orders, the load
time for a list box bound to the stored procedure is 6 seconds at 4096
packet.  When I moved to VB.Net and changed the packet size to 32767, the
same amount of data took 1 second.  I know that doesn't sound like much of a
savings, but my end users reported a huge difference in response time
throughout the app.

An Access ADP automatically sets up 3 connections to the SQL BE so I found
it more economical to use AccessConnection because that allowed me to use
one of the existing 3 connections instead of launching another one.

Doris Manning
mikedorism at verizon.net






More information about the dba-SQLServer mailing list