Jim Dettman
jimdettman at verizon.net
Thu Jun 9 07:21:00 CDT 2011
John, <<Did you read the sql exchange between JET and SQL Server?>> Yes and once again as in many cases, something which seems simple on surface is really quite complex once you understand all the difficulties involved (functionality required vs. performance). What I found really interesting in there is that you can control the index used by JET used for bookmarking when going after SQL server rows. Never knew you could do that. Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Wednesday, June 08, 2011 06:39 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Optimizing Access for SQL Server I have to say, the interaction between Access and SQL Server is nothing if not convoluted. Did you read the sql exchange between JET and SQL Server? John W. Colby www.ColbyConsulting.com On 6/7/2011 10:06 AM, Jim Dettman wrote: > Some of you may find this interesting: > > <http://msdn.microsoft.com/en-us/library/bb188204.aspx#optaccsql_topic5> > http://msdn.microsoft.com/en-us/library/bb188204.aspx#optaccsql_topic5 > > It's a link to an article by Andy Baron on optimizing Access with SQL > Server; some *very* nice detail on how JET actually implements the keyset > cursor, chooses it's bookmark column(s), etc. > > I haven't read the whole thing yet, but from what I've read so far, if you > work with Access and SQL server, it's definitely worth the time to give a > run through. > > Interestingly enough, it's an "SQL" article, so I can see why many might > miss this. Access types don't typically look for SQL articles and SQL types > will do the "Oh, it's Access" and ignore it<g>. In fact I'm wondering why > it was not published as an Access article... > > Jim. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com