访问腐败/ MySQL [英] Access Corruption / MySQL

问题描述

我最近有一个Microsoft Access 97数据库损坏了我。

设置是一个拆分数据库（前端/后端）设置，大约10-15

用户。这是一年之内的第一次腐败。

数据库有大约25个表，总大小约为15MB，后面是紧凑的
。前端位于用户Windows 2000 Professional

桌面上，文件服务器是Windows 2000 Server。


我一直在考虑迁移后端，但由于成本，

我一直在考虑使用MySQL（ www.mysql.com ）并在前端使用链接的

ODBC表。


我有几个问题..


据我所知，当Access97前端查询

Access后端时，它实际上只是提取所有需要的数据

网络，运行查询，并显示所需内容。对于

示例，如果我有一个表EMPLOYEE（ID，NAME）并且我运行了查询：

SELECT ID FROM EMPLOYEE WHERE NAME =" John Doe


前端将通过网络从EMPLOYEE获得所有行，

然后执行SELECT。我的理解是否正确？


其次，如果我是正确的，将使用MySQL阻止这种情况发生

如果我使用链接的ODBC表？我宁愿不改写整个前面

结束使用ADO。


想法？


- -

Mike Loll

解决方案

Mike，


2003年11月20日07:06:28 -0800， mi ********* @ hotmail.com （Mike）写道：

comp.databases.ms-access：

我一直想着迁移回来结束，但由于成本原因，我一直在考虑使用MySQL（ www.mysql .com ）并在前端使用链接的
ODBC表。

我有几个问题..

我的理解是当Access97前端查询访问后端时，它实际上只是将所有需要的数据传递到网络上，运行查询并显示所需内容。例如，如果我有一个表EMPLOYEE（ID，NAME）并且我运行了查询：

SELECT ID FROM EMPLOYEE WHERE NAME =" John Doe"


是的，有点。


虽然JEt确实需要通过电线提供100％的需求，

并且绝对没有在文件服务器上进行处理，什么喷气机需要

根本不是表中的完整行集。你的桌子是

大概是索引的。 Jet将检查表定义，找到适用的索引定义

，带上必要的索引页

（这根本不是指所有索引页），找到位置

适当的数据页面与目标数据，然后带回那些包含您想要的记录的小数据页面。结果是比你想象的少了很多i / o，但是仍然有100％的数据在每个使用db的客户端pc上都会发生
处理 - 不是
文件服务器上的
。

其次，如果我是正确的，如果我使用链接的ODBC表，将使用MySQL阻止这种情况发生吗？我宁愿不重写整个前端使用ADO。

在你的例子中，是的，所有工作都是由mysql完成的

服务器，只有通过电线返回的正确行。


但是，有人说喷气式飞机会降低更多的压力
数据，甚至来自服务器rdbms。例如，如果你试图从引用两个表的查询中绘制数据，一个在mysql

服务器和一个本地，或者从另一个rdbms上，那么Jet必须要求b $ b解析查询，而mysql不能为你完成所有的工作。在像这样的情况下，它会回到类似于仅限喷气式飞机的实施方案。


但一般来说，服务器rdbms会很好地为你服务，而且mysql很好。

很多人更喜欢postgresql（我是其中之一）因为

功能集更全面，但这一切都取决于您的需求

。对于大型数据集olap类型项目，mysql优于

postgresql。为了满足全方位的服务需求，并且作为全面替换

喷气机，postgresql更好。


Peter Miller

__________________________________________________ __________

PK解决方案 - Microsoft Access / Jet / SQL数据恢复

免费报价，保证最低价格和最佳结果
www.pksolutions.com 1.866.FILE.FIX 1.760.476.9051

< BLOCKQUOTE>>但一般来说，服务器rdbms会很好地为你服务，而且mysql很好。

很多人更喜欢postgresql（我是其中之一）因为
功能集更多全面，但这一切都取决于您的需求是什么。对于大型数据集olap类型项目，mysql优于postgresql。对于全面的服务需求，并且作为全面的喷射器的一般替代品，postgresql更好。

win32上postgresql的状态是什么？它稳定吗？我问b
的原因是因为我在网站上阅读了win32常见问题，他们列出了一些在cygwin下运行它的一些事情，关于管道不安全或

东西。你是否用于win32的制作工作？


-

Mike
mi ********* @ hotmail.com

2003年11月20日19:09:27 -0800， mi ********* @ hotmail.com （Mike）写道

comp.databases.ms-access：

postgresql的状态是什么win32的？它稳定吗？我之所以问的原因是因为我在网站上阅读了win32常见问题解答，他们列出了一些在cygwin下运行它的一些事情，关于管道不安全或什么东西。你是否在win32上用于生产工作？

编号我从linux盒子里运行postgresql。对于一台

开发机器来说Cygwin很好，但是我不想把它作为一个要求建议

用于生产环境。

Peter Miller

__________________________________________________ __________

PK解决方案 - Microsoft Access / Jet / SQL数据恢复

免费报价，保证最低价格和最佳结果
www.pksolutions.com 1.866.FILE.FIX 1.760.476.9051

I recently had a Microsoft Access 97 database corrupt on me. The
setup is a split database (front end/back end) setup with about 10-15
users. This is the first corruption in something like a year. The
database has about 25 tables, and the total size is about 15MB, after
a compact. The front end sits on users Windows 2000 Professional
desktops, and the file server is a Windows 2000 Server.

I''ve been thinking of migrating the back end, but because of cost,
I''ve been thinking about using MySQL (www.mysql.com) and using linked
ODBC tables from within the front end.

I have a few questions..

It is my understanding that when an Access97 front end queries an
Access backend, it really just pulls all of the needed data accross
the network, runs the query, and displays what is needed. For
example, if I had a table EMPLOYEE(ID, NAME) and I ran the query:

SELECT ID FROM EMPLOYEE WHERE NAME = "John Doe"

The front end would get ALL of the rows from EMPLOYEE via the network,
and then perform the SELECT. Is my understanding correct?

Secondly, if I am correct, will using MySQL stop this from happening
if I use linked ODBC tables? I''d rather not rewrite the entire front
end to use ADO.

Thoughts?

--
Mike Loll

解决方案

Mike,

On 20 Nov 2003 07:06:28 -0800, mi*********@hotmail.com (Mike) wrote in
comp.databases.ms-access:

I''ve been thinking of migrating the back end, but because of cost,
I''ve been thinking about using MySQL (www.mysql.com) and using linked
ODBC tables from within the front end.

I have a few questions..

It is my understanding that when an Access97 front end queries an
Access backend, it really just pulls all of the needed data accross
the network, runs the query, and displays what is needed. For
example, if I had a table EMPLOYEE(ID, NAME) and I ran the query:

SELECT ID FROM EMPLOYEE WHERE NAME = "John Doe"

The front end would get ALL of the rows from EMPLOYEE via the network,
and then perform the SELECT. Is my understanding correct?
Yes, kind of.

Although JEt does need to pull 100% of what it needs over the wire,
and absolutely no processing occurs on the file server, what jet needs
is not at all the complete set of rows from your table. Your table is
presumably indexed. Jet will check the table definition, find the
applicable index definitions, bring over the necessary index pages
(which does not at all mean all index pages), find the location of the
appropriate data page(s) with the target data, then bring back those
small data pages that contain your desired records. The result is a
lot less i/o than you might think, but still, 100% of the data
processing occurs on each and every client pc that uses the db - not
on the file server.
Secondly, if I am correct, will using MySQL stop this from happening
if I use linked ODBC tables? I''d rather not rewrite the entire front
end to use ADO.

In your example case, yes, all the work is done by mysql on the
server, and only the correct rows returned over the wire.

But that said, there are cases where jet will pull down much more
data, even from a server rdbms. For instance, if you attempted to
draw data from a query that referenced two tables, one on the mysql
server and one local, or on from a different rdbms, then Jet has to
resolve the query, and mysql can''t do all the work for you. In a case
like that, it''s back to a similar scenario as a jet-only
implementation.

But in general, a server rdbms will serve you well, and mysql is fine.
A lot of people prefer postgresql (I''m one of them) because the
feature set is more comprehensive, but it all depends what your needs
are. For large dataset olap type projects, mysql has an edge over
postgresql. For full service needs, and as a general replacement for
jet across the board, postgresql is better.

Peter Miller
__________________________________________________ __________
PK Solutions -- Data Recovery for Microsoft Access/Jet/SQL
Free quotes, Guaranteed lowest prices and best results
www.pksolutions.com 1.866.FILE.FIX 1.760.476.9051

> But in general, a server rdbms will serve you well, and mysql is fine.

A lot of people prefer postgresql (I''m one of them) because the
feature set is more comprehensive, but it all depends what your needs
are. For large dataset olap type projects, mysql has an edge over
postgresql. For full service needs, and as a general replacement for
jet across the board, postgresql is better.

What''s the status of postgresql on win32? Is it stable? The reason I
ask is because I read the win32 faq on the web site and they listed
some things with running it under cygwin about pipes being insecure or
something. Do you use in for production work on win32?

--
Mike
mi*********@hotmail.com

On 20 Nov 2003 19:09:27 -0800, mi*********@hotmail.com (Mike) wrote in
comp.databases.ms-access:

What''s the status of postgresql on win32? Is it stable? The reason I
ask is because I read the win32 faq on the web site and they listed
some things with running it under cygwin about pipes being insecure or
something. Do you use in for production work on win32?

No. I run postgresql from a linux box. Cygwin''s fine for a
development machine, but I don''t like suggesting it as a requirement
for a production environment.
Peter Miller
__________________________________________________ __________
PK Solutions -- Data Recovery for Microsoft Access/Jet/SQL
Free quotes, Guaranteed lowest prices and best results
www.pksolutions.com 1.866.FILE.FIX 1.760.476.9051

这篇关于访问腐败/ MySQL的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！