访问2010 / Windows 7性能 [英] Access 2010 / Windows 7 Performance

问题描述

嗨：

我正在尝试解决运行MSAccess 2010 / Windows 7的PC上数据库性能大幅下降的问题。 我们发现使用这种配置的性能比我们的MSA 2003 / WinXP PC要低得多（尽管这些PC的价格要低得多，而且规格较慢，即处理器速度较慢，HDD速度较慢，内存较少）。

虽然问题的关键在于对链接表的性能（SQL Server 2000，旧的是，但谷歌搜索显示人们也有类似SQL 2005/2008链接表的问题），我做了一个简单的.mdb只包含一个本机表（I
为SQL Server提供了大约200,000条记录的表），然后通过从该表中选择的记录集进行迭代测试。

我所看到的是，即使在"一体化".mdb中，我们所有的Access 2010 pc（包括一个Access 2010&/ WinXP PC）的性能仍然大大降低。 Access 2003 PC需要大约2-5秒才能返回并迭代
记录集，而功能更强大的MSA 2003 / Windows 7 pc则需要8-10秒才能完成相同的操作。

我花了几个小时阅读各种论坛主题，关于这个/与链表性能相关的类似问题（包括

http://social.msdn.microsoft.com/Forums/en-US/accessdev/thread/eece85a3- 14b9-4d77-9640-874c7d96f184  以及其中引用的主题） - 似乎没有任何可靠的解决方案。 不止一张海报引用了开放式
微软支持案例;没有人回复说他们收到了一个解决方案（除了ODBC注册表调整，大多数其他海报报告说这些调整对他们不起作用，也不适用于我们）。

有没有人对这个问题有进一步的了解？ 很难向客户解释他们使用新版Office的新PC运行速度比旧版PC慢2倍（之前的复杂搜索需要20-40秒才能返回
现在甚至不可能由于ODBC超时）。 他们正在询问"回归"WinXP / Office 2003，虽然这似乎是一个糟糕的长期选择，因为有几个原因（Ebay软件只是一个），我不知道还有什么我b $ b可以解决这个问题。

干杯，

Jan

解决方案

Jsoar写道：

我不知道我还能做些什么来解决这个问题。

你当然已完成作业了。  其中一张海报表示他们正在测试解决问题的修补程序。 然而，根据个人经验，可能需要2-4周的时间才能获得一般性下载的修补程序。$ / b>

贝

Hi:

I'm trying to troubleshoot substantially slower database performance on our PC's running MSAccess 2010 / Windows 7.  We are seeing substantially slower performance using this configuration than our MSA 2003 / WinXP PC's (even though these pc's tend to be much older and slower specifications-wise, i.e. slower processors, slower HDD's, less RAM).

While the crux of the matter relates to performance against linked tables (SQL Server 2000, old yes, but a google search shows people having similar issues with SQL 2005 / 2008 linked tables as well), I made a simple .mdb containing only 1 native table (I impoarted a table of about 200,000 records fro SQL Server) and then tested iterating through a recordset that was selected from this table.

What I'm seeing is that even in an 'all in one' .mdb, performance is still substantially slower in all of our Access 2010 pc's (including one Access 2010 / WinXP PC). The Access 2003 PC's take about 2-5 seconds to return and iterate through the recordset, while the substantially more powerful MSA 2003 / Windows 7 pc's require 8-10 seconds to complete the same operation.

I have spent hours reading various forum threads about this / similar issues related to linked table performance (including http://social.msdn.microsoft.com/Forums/en-US/accessdev/thread/eece85a3-14b9-4d77-9640-874c7d96f184 and the threads referenced therein) - there does not appear to be any reliable solution todate.  More than one of the posters have referenced open Microsoft Support cases; nobody has posted back that they received a solution (with the exception of an ODBC registry adjustment, which most other posters reported did not work for them, and also did not work for us).

Does anybody have any further insight into this issue?  It's hard to explain to a client that their new PC with the new version of Office runs 2x-4x slower than their old pc (and that complex searches that formerly took 20-40 seconds to return are now not even possible due to ODBC timeouts).  They are asking about 'going back' to WinXP / Office 2003 and while this seems like a poor long-term choice for several reasons (Ebay sourcing of software being just one), I don't know what else I can do to resolve this issue.

Cheers,

Jan

解决方案

Jsoar wrote:

I don't know what else I can do to resolve this issue.

You've certainly done your homework.   One of the posters indicated that
they are testing a hotfix which solved the problem.  However it's been
my personal experience that it can be 2-4 weeks before a hotfix is
available for general download.

Tony

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