拆分数据库性能不佳 [英] Split Database Poor Performance

问题描述

您好，

自从拆分我的数据库以来，与未拆分相比，一个表格特别需要加载和刷新大约10

倍

服务器上的版本。


它背后的代码包含36个SQL语句，这些语句填充表单上的单个

文本框 - 这可能是为什么？


谢谢 - 大卫

解决方案

总之，是的。网络*显着*慢于您的硬

驱动器。你的问题几乎就是说：我需要花更长的时间才能开车经过高峰时间从我家到工作的交通比

过去带我走路楼下到我的家庭办公室。嗯，是的，

特别是因为你不需要进入高峰时段交通

拥堵。


那'这就是为什么人们通常会将所有静态表转储到数据库的前端，并根据需要一起更新它们。你可能想要读取Access Developer Handbook第2卷，也许是Chipman和
Baron'关于使用Access作为SQL服务器前端的书......

感谢阅读建议。


我很欣赏我的硬盘和网络之间的区别但是

我的unsplit数据库也在服务器上与

拆分后端相同的位置。当我运行未分割的那个时，我是否将整个东西加载到我的客户端PC内存中？


我认为拆分应该可以提高性能吗？ />

谢谢 - 大卫

拆分数据库会慢一点，但系数10表示

其他问题也在这里发挥作用。


按照Tony Toews在Access中列出的项目进行工作

性能常见问题解答：
http://www.granite.ab.ca /access/performancefaq.htm

其中一些如姓名自动更正和子数据表产生了一个主要的

差异。


关于此特定表格，您可以做其他事情。你

不能直接在文本框的控制源中使用SQL语句，所以

我不知道这36个语句在何处/如何使用，但如果它们都来自一个表格，你可能会使用未绑定的文本框，并通过在Form_Current中打开一个记录集来为它们分配值

所以这一切都发生在一个行程中

而不是36次不同的旅行。


-

Allen Browne - 微软MVP。西澳大利亚州珀斯。

访问用户提示 - http：// allenbrowne.com/tips.html

回复群组，而不是mvps dot org的allenbrowne。


Daveo < WR ********** @ gmail.com>在消息中写道

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

自从拆分我的数据库以来，与服务器上的未分割版本相比，一个表单特别需要加载和刷新大约10倍的时间。
<它背后的代码包含36个SQL语句，它们填充表单上的各个文本框 - 这可能就是为什么？

谢谢 - 大卫

Hi there,

Since splitting my database, one form in particular takes about 10
times as long to load and refresh, compared to the unsplit version on
the server.

The code behind it contains 36 SQL statements which populate individual
text boxes on the form - could that be why?

Thanks - David

解决方案

In a word, YES. Networks are *significantly* slower than your hard
drive. Your question is almost like saying "It takes a lot longer for
me to drive through rush hour traffic from my house to work than it
used to take me to walk downstairs to my home office." Well, yeah,
especially since you don''t need to get into rush hour traffic
congestion.

That''s why people usually dump all that static tables into the front
end of the database and update them en masse as necessary. You might
want to read Access Developer Handbook volume 2 and maybe Chipman and
Baron''s book on using Access as a front end to SQL server...

Thanks for the reading advice.

I appreciate the difference between my hard drive and the network but
my unsplit database is on the server too in the same location as the
split backend. When I run the unsplit one, am I loading the whole thing
into my client PCs memory?

I thought splitting was supposed to improve performance?

Thanks - David

A split database will be somewhat slower, but a factor of 10 indicates that
other issues are playing a part here too.

Work your way through the items that Tony Toews lists in the Access
Performance FAQ at:
http://www.granite.ab.ca/access/performancefaq.htm
Several of them such as Name AutoCorrect and Subdatasheets make a major
difference.

Regarding this specific form, there may be other things you can do. You
cannot use a SQL statment directly in the Control Source of a text box, so
I''m not sure where/how these 36 statments are used, but if they are all
coming from one table, you might use unbound text boxes, and assign values
to them by opening a recordset in Form_Current so it all happens in one trip
instead of 36 different trips.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Daveo" <wr**********@gmail.com> wrote in message
news:11**********************@g47g2000cwa.googlegr oups.com...

Since splitting my database, one form in particular takes about 10
times as long to load and refresh, compared to the unsplit version on
the server.

The code behind it contains 36 SQL statements which populate individual
text boxes on the form - could that be why?

Thanks - David

这篇关于拆分数据库性能不佳的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！