Hi all,
I'm wondering if it is possible to have a regular Access mdb, but have
exactly one table which stores images in an MSDE database. Is it possible
to keep all my forms and reports and queries but just have the one image
table stored in MSDE. It appears, from my tests that MSDE doesn't suffer
from the image bloat problem that access does.
"Yair Sageev" <geekyheeb-news@.yahoo.com> wrote:
>I'm wondering if it is possible to have a regular Access mdb, but have
>exactly one table which stores images in an MSDE database. Is it possible
>to keep all my forms and reports and queries but just have the one image
>table stored in MSDE. It appears, from my tests that MSDE doesn't suffer
>from the image bloat problem that access does.
Certainly. That's exactly what linked tables are for. You can have tables
linked to any number of external sources.
- Tim Roberts, timr@.probo.com
Providenza & Boekelheide, Inc
|||To add to Tim's post, yes, it's possible, but beware of heterogeneous
joins. When executing queries that join your MSDE table to Jet tables
(or tables from any other database). Access needs to fetch *all* of
the data from your MSDE table to perform the join locally *before* it
can execute a WHERE clause. In the case of large images, this could
have serious performance implications.
--Mary
On Wed, 4 Aug 2004 12:51:56 -0400, "Yair Sageev"
<geekyheeb-news@.yahoo.com> wrote:
>Hi all,
>I'm wondering if it is possible to have a regular Access mdb, but have
>exactly one table which stores images in an MSDE database. Is it possible
>to keep all my forms and reports and queries but just have the one image
>table stored in MSDE. It appears, from my tests that MSDE doesn't suffer
>from the image bloat problem that access does.
>
|||Thanks for both of your repsonses.
I succeeded in moving all my jet tables to MSDE in the hope that the way
data is stored is improved and that images don't bloat the database. Not
sure if this will work. The application is working fine. I'm not doing any
heterogeneous joins.
I would love to migrate to an ADP file but all my queries break in that
case. I don't know how to reference forms in queries within an ADP.
"Mary Chipman" <mchip@.online.microsoft.com> wrote in message
news:tc37h01h37suaqlk9a92ed583o8mjgafac@.4ax.com... [vbcol=seagreen]
> To add to Tim's post, yes, it's possible, but beware of heterogeneous
> joins. When executing queries that join your MSDE table to Jet tables
> (or tables from any other database). Access needs to fetch *all* of
> the data from your MSDE table to perform the join locally *before* it
> can execute a WHERE clause. In the case of large images, this could
> have serious performance implications.
> --Mary
> On Wed, 4 Aug 2004 12:51:56 -0400, "Yair Sageev"
> <geekyheeb-news@.yahoo.com> wrote:
possible
>
|||It's not a matter of knowing how -- you can't reference forms in
queries in an ADP because they are processed by the SQL Server engine,
which doesn't know anything about Access forms. You'd need to re-write
all your saved Access queries in T-SQL as views or stored procedures.
FWIW, you gain nothing and lose a lot of flexibility when you use an
ADP over an MDB, not just the query processor. You're better off with
an mdb front-end to your SQL Server back-end, which is even what the
Access team is recommending these days. They're definitely moving away
from recommending ADPs for new development.
--Mary
On Sat, 7 Aug 2004 20:11:54 -0400, "Yair Sageev"
<geekyheeb-news@.yahoo.com> wrote:
>Thanks for both of your repsonses.
>I succeeded in moving all my jet tables to MSDE in the hope that the way
>data is stored is improved and that images don't bloat the database. Not
>sure if this will work. The application is working fine. I'm not doing any
>heterogeneous joins.
>I would love to migrate to an ADP file but all my queries break in that
>case. I don't know how to reference forms in queries within an ADP.
>
>"Mary Chipman" <mchip@.online.microsoft.com> wrote in message
>news:tc37h01h37suaqlk9a92ed583o8mjgafac@.4ax.com.. .
>possible
>
Showing posts with label regular. Show all posts
Showing posts with label regular. Show all posts
Monday, March 26, 2012
Monday, March 12, 2012
servers
We are creating a newServer grabbing data from an extrnal data source.
We need to perform regular audits to verify the record counts (for now) are the same.
We have 2 physically separate SQL servers 1 with old 1 with new.
I have created a linked server but when i do a query on the linked server the performace is pathetic (2mins 12 secs) to do a simple count.
Is there a better way, or can improv the perf?
Thanks
Greg CSomething is grieviously broken, but I don't have enough information to tell you what is broken or how it should be fixed.
The first step would be to attempt the same query the new server using Query Analyzer. The purpose of this step is to determine if the problem lies in the connection between the two machines or within the SQL Server itself. If the query runs poorly in Query Analyzer, then the problem is in the connection between the machines (something is impeding SQL communications between them). If the query runs acceptably in Query Analyzer but does not using the linked server, then the problem is in the linked server.
-PatP|||Yep thanks, field i was counting wasnt indexed.. thanks|||That would be what we call a "bad thing" for lack of a better term! I'm glad to know that the answer was so simple.
-PatP
We need to perform regular audits to verify the record counts (for now) are the same.
We have 2 physically separate SQL servers 1 with old 1 with new.
I have created a linked server but when i do a query on the linked server the performace is pathetic (2mins 12 secs) to do a simple count.
Is there a better way, or can improv the perf?
Thanks
Greg CSomething is grieviously broken, but I don't have enough information to tell you what is broken or how it should be fixed.
The first step would be to attempt the same query the new server using Query Analyzer. The purpose of this step is to determine if the problem lies in the connection between the two machines or within the SQL Server itself. If the query runs poorly in Query Analyzer, then the problem is in the connection between the machines (something is impeding SQL communications between them). If the query runs acceptably in Query Analyzer but does not using the linked server, then the problem is in the linked server.
-PatP|||Yep thanks, field i was counting wasnt indexed.. thanks|||That would be what we call a "bad thing" for lack of a better term! I'm glad to know that the answer was so simple.
-PatP
Subscribe to:
Posts (Atom)