Access SQL to Transact SQL - Translator?

Friends,
I am new to SQL Server, and I access it mainly through
Access (ODBC DSN).
I need my queries to run faster, so I want to switch from
regular Access queries against linked SQL tables to faster
pass-through queries written in Transact SQL.
QUESTION: Does anyone know of an easy way to translate
Access SQL into Transact SQL - in other words, a way to
copy the Access SQL from SQL View, and paste it into a
translator?
Thanks in advance ...
"bill morgan" <willmorgan@.lisco.com> wrote in message
news:3f3d01c4a5bc$4dbaf7f0$a301280a@.phx.gbl...
> I am new to SQL Server, and I access it mainly through
> Access (ODBC DSN).
> I need my queries to run faster, so I want to switch from
> regular Access queries against linked SQL tables to faster
> pass-through queries written in Transact SQL.
If you want performance you may want to consider using SQL Server VIEWS and
Stored Procedures.

> QUESTION: Does anyone know of an easy way to translate
> Access SQL into Transact SQL - in other words, a way to
> copy the Access SQL from SQL View, and paste it into a
> translator?
There is no "easy" way to do this since the SQL syntax is different between
these 2 products.
On suggestion though, you could try running SQL Profiler and capture the SQL
Server SQL generated by an Access query. This you might be able to translate
into an SQL Server View or Stored Procedure.
Steve
|||Steve,
Thanks for your response. Actually, I have been capturing
the Access SQL, and generally it is simple to translate it
into Transact SQL. It gets sticky, though, when trying to
translate computed fields. For example, SQL Server does
not accept IIF() functions, so I have to come up with
alternative syntax and structure.
Thanks again ...[vbcol=seagreen]
>--Original Message--
>"bill morgan" <willmorgan@.lisco.com> wrote in message
>news:3f3d01c4a5bc$4dbaf7f0$a301280a@.phx.gbl...
from[vbcol=seagreen]
faster
>If you want performance you may want to consider using
SQL Server VIEWS and
>Stored Procedures.
>
>There is no "easy" way to do this since the SQL syntax is
different between
>these 2 products.
>On suggestion though, you could try running SQL Profiler
and capture the SQL
>Server SQL generated by an Access query. This you might
be able to translate
>into an SQL Server View or Stored Procedure.
>Steve
>
>.
>