[dba-SQLServer] Developer Edition v. LocalDB

[Daniel Waters]

I put an application together as described for one customer with SQL. The scenario was a local area network with ODBC table links, not a WAN, and using DAO - not ADO.  Speed was quite fast. At one time, I did a thorough test to compare speed between SQL with ODBC table links vs. Access tables (BE) and Access table links (FE). The results showed almost identical speed.

But on a WAN I could see a problem! :-)


-----Original Message-----
From: dba-SQLServer [mailto:dba-sqlserver-bounces+df.waters=outlook.com at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: 31 March, 2022 17:49
To: Discussion concerning MS SQL Server
Subject: Re: [dba-SQLServer] Developer Edition v. LocalDB

If this were going to be networked, I'd disagree strongly. There is a huge network overhead 
if you are not using pass through queries and Access has to pull lots of  data to apply joins,  
sorts, filters etc

But since the intention is to have it all on the same machine, that is not really an issue and 
uing FE queries has the advantages outlined. 

On 31 Mar 2022 at 18:24, Daniel Waters wrote:

> Hi Arthur,
> 
> I've thought about query objects in the FE vs. SQL Views (or stored
> procedures) in the BE.  I'm going to put out a big vote to keep things
> in the FE.  This keeps things easier for you because everything is in
> one IDE, and because the query design window in Access is easier to
> use than the View design window in SQL.  Let SQL be the place where
> the tables are and let that be that!
> 
> I've done this with several applications and can't see a reason to
> change.  I have used one built-in SP to let me know who was logged
> into the database.
> 
> Dan
> 

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
https://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com