I've been using ADO to connect to SQL Server to run stored procedures.
I'm
just wondering if there are any advantages to using an ADP project instead
of
ADO?
Well, the advantage of a ADP project is that your sql you write in the query
builder is actually on the server side.
So, bad joins or even bad sql that loads a lot of records, but only
*results* in a small dataset is often better executed by a ADP project.
However, if your ado queries are clean, or are in fact NOT based on linked
mdb tables (or are in fact pass-though), then performance will be the same
as a ADP project.
Also I'd like to know if a T-SQL query in ADP is just as fast as running
it
in Query Analyzer?
I can't imagine why using ado, or even DAO is going to make any difference.
In fact, a good many of use still use DAO to sql server, and there is no
performance difference then using ado in 99% of the cases anyway.
T-SQL is 100% executed server side, and sql don't care if that execute
command came from a web site, DAO in ms-access, ADO, or if you build your
own connection object, and use the execute method that way. In all cases, we
talking about code running on the server side...it don't care how that stuff
came to be client side. So, yes, there should not be any speed diffence in
running t-sql, as it is server side...not client side...
