Re: Converting JET Queries to MSDE Stored Procedures
- From: "Albert D.Kallal" <PleaseNOOOsPAMmkallal@xxxxxxx>
- Date: Fri, 17 Jun 2005 16:53:00 -0600
"Robert1105" <Robert1105@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CE82A97B-D513-475C-AB2B-5E18E6AD1112@xxxxxxxxxxxxxxxx
> Our current plan is to use a linked mdb file as our application is quite
> involved and has a lot of dao code.
Good, I also find that the above makes the most sense for existing
applications.
>
> We are using Access to manage the MSDE. Are you referring to using
> Enterprise Manager in SQL? We looked at this but could not find the DMO
> Tools in our SQL 7.0 version? Is this a special add-in?
Yes, you need to install the sql server tools to manage the MSDE. The MSDE
does NOT come with the sql enterprise manger tools. However, there is a neat
way to get the enterprise manager for free. Simply download the trial
edition of sql server (I don't know if it is still available, now that we
got sql 2005 express). When you download the trial edition of sql server,
simply install the CLIENT TOOLS ONLY, and you get a copy of the enterprise
manager for free, and this is NO expiry date on the client tools for sql
server.
So, yes, I am saying to manage the MSDE with the sqls erver client tools. In
fact, if you don't use a ADP project, then how were you managing the MSDE
from a mdb file anyway? (can't do much with a mdb to manage the MSDE). So,
it makes a lot of sense to get the sql server client tools running on your
computer, as then you get the SAME tools you use with the full blown version
of sql server, and yet you can do this all for free, and legal too!
> 1) Gain access to stored procedure for a number of our queries that are
> very
> complex and slow in the present environment. We are hoping this will
> improve
> some of our performance issues. We are also doing some optimization as
> well.
Remember, a local jet data database as compared to a local sql server (FULL
or MSDE) tends to run quite a bit faster then sql server. This is nor for
all cases, but as general rule I find JET quite a bit faster then sql
server when no network is involved. Of course, this assumes you don't have
code that does dump things like try and open a recordset in the middle of a
loop. If by converting some VBA code that opens a reocrdset in the middle of
the loop to a stored procedures, you see a ENORMOUS increase in speed, but
that increase is only due to removing the opening of the reocreset in the
loop
Anyway, the above is a great way to get the enterprise manager installed,
and the EM does work very well with the MSDE.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@xxxxxxx
http://www.members.shaw.ca/AlbertKallal
.
- Follow-Ups:
- Re: Converting JET Queries to MSDE Stored Procedures
- From: Robert1105
- Re: Converting JET Queries to MSDE Stored Procedures
- References:
- Converting JET Queries to MSDE Stored Procedures
- From: Robert1105
- Re: Converting JET Queries to MSDE Stored Procedures
- From: Albert D.Kallal
- Re: Converting JET Queries to MSDE Stored Procedures
- From: Robert1105
- Converting JET Queries to MSDE Stored Procedures
- Prev by Date: Re: Access 97 Shell
- Next by Date: Re: problems after converting from 97 to 2003
- Previous by thread: Re: Converting JET Queries to MSDE Stored Procedures
- Next by thread: Re: Converting JET Queries to MSDE Stored Procedures
- Index(es):
Relevant Pages
|