关闭主题 - 访问Postgres [英] Off Topic - Access to Postgres

问题描述

我们刚刚将Access 2000

后端的数据迁移到Postgres。所有表单和报告似乎都运行正常但是，很多情况下，b $ b非常缓慢。我们不希望切换，直到我们

可以加快速度。我们想开始实施Stored

程序，以便我们可以进行服务器端处理。

任何人都可以推荐一本可以帮助我们学习如何使用的书b $ b使用sprocs或pass-through查询？如果我的术语是错误的，那么我很抱歉。我不知道怎么问

正确的问题。

谢谢，

Hank Reed

解决方案

2005年12月27日18:00:46 -0800，汉克 <公顷******** @ aol.com>写道：

我们刚刚将数据从Access 2000
后端迁移到Postgres。所有表单和报告似乎都运行正常，但在很多情况下，非常缓慢。我们不希望切换，直到我们能够加快速度。我们希望开始实施存储
程序，以便我们可以进行服务器端处理。
任何人都可以推荐一本可以帮助我们学习如何使用sprocs或传递查询的书吗？如果我的术语不正确，我道歉。我不知道如何问正确的问题。
谢谢，汉克·里德

当你客户端/服务器存在速度问题，使用传递查询

和存储过程通常不是最佳答案，可能根本没有帮助。

这样做是但是，这是一个很好的方法，使您的程序难以开发和维护4到5倍。


对于Access客户端/服务器性能问题，请先制作确保您的

应用程序能够很好地与客户端/服务器配合使用，并与

配合使用，以确保Access如何与服务器配合使用。


一般客户端/服务器问题：

- 不要返回未经过滤的，未按照集中的结果，并且一次只能输回几百个结果行。


访问问题：

- 确保每张桌子都有一把主钥匙。


从这些开始，看看它是怎么回事。

Steve Jorgensen写道：

2005年12月27日18:00:46 -0800，Hank <公顷******** @ aol.com>写道：

我们刚刚将数据从Access 2000
后端迁移到Postgres。所有表单和报告似乎都运行正常，但在很多情况下，非常缓慢。我们不希望切换，直到我们能够加快速度。我们希望开始实施存储
程序，以便我们可以进行服务器端处理。
任何人都可以推荐一本可以帮助我们学习如何使用sprocs或传递查询的书吗？如果我的术语不正确，我道歉。我不知道如何提出正确的问题。
谢谢，Hank Reed
当你遇到客户/服务器速度问题时，使用pass-通过查询
和存储过程通常不是最好的答案，并且可能根本没有帮助。
然而，这样做是让你的程序难以实现4或5次的好方法
开发和维护。

Steve，

感谢您的建议。我总是在每张

表中使用PK。我对像Postgres这样的数据库的新手理解是，我们

只会获得过滤后的记录。我被引导相信（或者说自己确信）存储过程只会选择并返回感兴趣的记录，因此可以节省带宽和传输时间。 br />
一般。如果sprocs和传递查询不是解决方案那么

你会推荐什么？

再次感谢，

Hank Reed对于Access客户端/服务器性能问题，首先要确保您的
应用程序能够很好地与客户端/服务器配合使用，以及与Access如何与服务器配合使用。

一般客户端/服务器问题：
- 不要返回未经过滤的，未按照集中的结果，并且一次不要返回超过几百个结果行。

访问问题： - 确保每张桌子都有一把钥匙。

从这些桌子开始，看看它是怎么回事。

< BLOCKQUOTE>"汉克" <公顷******** @ aol.com>在消息中写道

news：11 ********************** @ z14g2000cwz.googlegr oups.com ...

Steve Jorgensen写道：

2005年12月27日18:00:46 -0800，Hank <公顷******** @ aol.com>写道：

我们刚刚将数据从Access 2000
后端迁移到Postgres。所有表单和报告似乎都运行正常，但在很多情况下，非常缓慢。我们不希望切换，直到我们能够加快速度。我们希望开始实施存储
程序，以便我们可以进行服务器端处理。
任何人都可以推荐一本可以帮助我们学习如何使用sprocs或传递查询的书吗？如果我的术语不正确，我道歉。我不知道如何提出正确的问题。
谢谢，汉克·里德

当你遇到速度问题时使用客户端/服务器，使用传递
查询和存储过程通常不是最佳答案，并且可能根本不会帮助
。但是，这样做是一个很好的方法，可以使你的程序4到5次b $ b更难开发和维护。

史蒂夫，
感谢您的建议。我总是在每个表中使用PK。我对像Postgres这样的数据库的新手理解是，我们只能获得过滤后的记录。我被引导相信（或者说服自己）存储过程会选择并仅返回感兴趣的记录，从而节省带宽和传输时间，一般情况下。如果sprocs和传递查询不是解决方案，那么你会推荐什么？
再次感谢，
Hank Reed

坦率地说，我''对于史蒂夫的一些评论感到困惑。我肯定

同意关于不返回未经过滤的，未分类的结果的部分。

但是，我发现使用视图，存储过程并通过查询

是实现这一目标的最有效方法之一。


-

Randy Harris

tech at promail dot com

我很确定我知道我记得的一切。

对于Access客户端/服务器性能问题，首先要确保你的
应用程序能够很好地与客户端/服务器配合使用，并且能够很好地使用Access与服务器协同工作的方式。

一般客户端/服务器问题：
- 不要返回未经过滤的，未分类的结果，并且一次不要返回超过几百个结果行的
。

访问问题： - 确保每个表都有一个主键。

从这些表开始，看看它是怎么回事。

We have just recently migrated the data from our Access 2000
backend to Postgres. All forms and reports seem to run correctly but,
in many cases, very slowly. We do not want to switch over until we
can speed things up. We would like to start implementing Stored
Procedures so we can do Server-Side processing.
Can anyone recommend a book that would help us learn how to
use sprocs or pass-through queries? I apologize if my terminology is
incorrect. I am in the position of not quite knowing how to ask the
right questions.
Thanks,
Hank Reed

解决方案

On 27 Dec 2005 18:00:46 -0800, "Hank" <ha********@aol.com> wrote:

We have just recently migrated the data from our Access 2000
backend to Postgres. All forms and reports seem to run correctly but,
in many cases, very slowly. We do not want to switch over until we
can speed things up. We would like to start implementing Stored
Procedures so we can do Server-Side processing.
Can anyone recommend a book that would help us learn how to
use sprocs or pass-through queries? I apologize if my terminology is
incorrect. I am in the position of not quite knowing how to ask the
right questions.
Thanks,
Hank Reed

When you have a speed problem with client/server, using pass-through queries
and stored procedures is not usually the best answer, and may not help at all.
Doing that is, however, a good way to make your program 4 or 5 times harder to
develop and maintain.

For Access client/server performance problems, first make sure your
application is designed to work well with client/server and to work well with
how Access works with servers.

General client/server issue:
- Don''t return unfiltered, unaggregated results, and don''t return more than a
couple hundred result rows at a time.

Access issue:
- Make sure every table has a primary key.

Start with those, and see how it goes.

Steve Jorgensen wrote:

On 27 Dec 2005 18:00:46 -0800, "Hank" <ha********@aol.com> wrote:

We have just recently migrated the data from our Access 2000
backend to Postgres. All forms and reports seem to run correctly but,
in many cases, very slowly. We do not want to switch over until we
can speed things up. We would like to start implementing Stored
Procedures so we can do Server-Side processing.
Can anyone recommend a book that would help us learn how to
use sprocs or pass-through queries? I apologize if my terminology is
incorrect. I am in the position of not quite knowing how to ask the
right questions.
Thanks,
Hank Reed
When you have a speed problem with client/server, using pass-through queries
and stored procedures is not usually the best answer, and may not help at all.
Doing that is, however, a good way to make your program 4 or 5 times harder to
develop and maintain.

Steve,
Thanks for the advice. I have always used PKs in every
table. My novice understanding of a database like Postgres is that we
would ONLY get the filtered records. I have been led to believe (or
convinced myself) that a stored procedure would select and return only
the records of interest, thus saving bandwidth and transfer time, in
general. If sprocs and pass through queries are not the solution then
what would you recomend?
Thanks again,
Hank Reed For Access client/server performance problems, first make sure your
application is designed to work well with client/server and to work well with
how Access works with servers.

General client/server issue:
- Don''t return unfiltered, unaggregated results, and don''t return more than a
couple hundred result rows at a time.

Access issue:
- Make sure every table has a primary key.

Start with those, and see how it goes.

"Hank" <ha********@aol.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...

Steve Jorgensen wrote:

On 27 Dec 2005 18:00:46 -0800, "Hank" <ha********@aol.com> wrote:

We have just recently migrated the data from our Access 2000
backend to Postgres. All forms and reports seem to run correctly but,
in many cases, very slowly. We do not want to switch over until we
can speed things up. We would like to start implementing Stored
Procedures so we can do Server-Side processing.
Can anyone recommend a book that would help us learn how to
use sprocs or pass-through queries? I apologize if my terminology is
incorrect. I am in the position of not quite knowing how to ask the
right questions.
Thanks,
Hank Reed

When you have a speed problem with client/server, using pass-through queries and stored procedures is not usually the best answer, and may not help at all. Doing that is, however, a good way to make your program 4 or 5 times harder to develop and maintain.

Steve,
Thanks for the advice. I have always used PKs in every
table. My novice understanding of a database like Postgres is that we
would ONLY get the filtered records. I have been led to believe (or
convinced myself) that a stored procedure would select and return only
the records of interest, thus saving bandwidth and transfer time, in
general. If sprocs and pass through queries are not the solution then
what would you recomend?
Thanks again,
Hank Reed

Frankly, I''m a bit puzzled by that portion of Steve''s comments. I certainly
agree with the part about not returning unfiltered, unaggregated results.
However, I find that using views, stored procedures and pass through queries
are among the most effective ways of accomplishing that.

--
Randy Harris
tech at promail dot com
I''m pretty sure I know everything that I can remember.

For Access client/server performance problems, first make sure your
application is designed to work well with client/server and to work well with how Access works with servers.

General client/server issue:
- Don''t return unfiltered, unaggregated results, and don''t return more than a couple hundred result rows at a time.

Access issue:
- Make sure every table has a primary key.

Start with those, and see how it goes.

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