非Jet OLEDB后端？ [英] Non-Jet OLEDB backends?

问题描述

我正在开发c ++，OLEDB，并以Jet后端为目标。我在项目后期实现了
Jet后端太慢了，我需要重新调整
重新定位。我不想重写我的源代码。我不想支付
特许权使用费。我想要更好的表现。该应用程序是单用户，本地

访问权限，但需要高性能。

一般不需要花哨的功能...


有人可以推荐一个新的后端吗？


RDeW

I am developing in c++, OLEDB, and targeting the Jet backend. I have
realized late in the project that the Jet backend is too slow, and I need to
retarget. I do not want to rewrite my source code. I do not want to pay
royalties. I want better performance. The application is single user, local
access only, but needs high performance. Fancy features are not required in
general ...

Can anyone recommend a new backend?

RDeW

推荐答案

" Riley DeWiley" < RI *********** @ gmail.com>在消息中写道

新闻：10 ************* @ corp.supernews.com ...

"Riley DeWiley" <ri***********@gmail.com> wrote in message
news:10*************@corp.supernews.com...

我用c ++开发， OLEDB，瞄准Jet后端。我已经在项目后期意识到Jet后端太慢了，我需要
来重新定位。我不想重写我的源代码。我不想支付版税。我想要更好的表现。该应用程序是单用户，仅限
本地访问，但需要高性能。花哨的功能一般不需要
...

任何人都可以推荐一个新的后端吗？

I am developing in c++, OLEDB, and targeting the Jet backend. I have
realized late in the project that the Jet backend is too slow, and I need to retarget. I do not want to rewrite my source code. I do not want to pay
royalties. I want better performance. The application is single user, local access only, but needs high performance. Fancy features are not required in general ...

Can anyone recommend a new backend?

在那个环境中我怀疑你会发现*任何东西*比Jet快。

也许你应该重新检查你的数据结构，查询，

和索引的设计。性能问题几乎总是由于设计不佳，而不是数据引擎，而且有很多正当理由将Jet转储到另一个数据引擎上，性能是很少靠近那个

列表的顶部。

-

我没有查看附上的电子邮件帐号

来自此消息。发送给... ...

在Hunter dot com的RBrandt

In that environment I doubt that you would find *anything* faster than Jet.
Perhaps you should re-examine the design of your data structures, queries,
and indexes. Performance problems are nearly always due to poor design,
not the data engine, and while there are many valid reasons to dump Jet in
favor of another data engine, performance is rarely near the top of that
list.
--
I don''t check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

本地太慢，只有一个用户，或者局域网或者太慢有很多

的用户。如果它是一个单独的用户本地，JET就像你找到的大多数

数据库一样快。如果你想要一些可以与多个用户快速共享的其他东西，我推荐使用PostgreSQL或Firebird。如果OLEDB驱动程序

还不稳定，使用OLEDB提供程序进行ODBC，并使用

ODBC驱动程序可以正常工作。我曾多次使用PostgreSQL。


周一，2004年11月1日02:13:08 -0800，Riley DeWiley < ri *********** @ gmail.com>

写道：

Too slow locally, with a single user, or too slow over a LAN or with many
users. If it''s local with a single user, JET is just as fast as most any
database you''ll find. If you want something else that will be fast shared
with multiple users, I recommend PostgreSQL or Firebird. If the OLEDB drivers
are not yet stable for these, using the OLEDB provider for ODBC, and using the
ODBC drivers work fine. I''ve done that with PostgreSQL on several occasions.

On Mon, 1 Nov 2004 02:13:08 -0800, "Riley DeWiley" <ri***********@gmail.com>
wrote:

我在c ++，OLEDB和针对Jet后端。我已经在项目后期意识到Jet后端太慢了，我需要重新定位。我不想重写我的源代码。我不想支付版税。我想要更好的表现。该应用程序是单用户，仅限本地访问，但需要高性能。
一般不需要花哨的功能......

任何人都可以推荐一个新的后端吗？

RDeW

I am developing in c++, OLEDB, and targeting the Jet backend. I have
realized late in the project that the Jet backend is too slow, and I need to
retarget. I do not want to rewrite my source code. I do not want to pay
royalties. I want better performance. The application is single user, local
access only, but needs high performance. Fancy features are not required in
general ...

Can anyone recommend a new backend?

RDeW

Riley DeWiley写道：

Riley DeWiley wrote:

我正在开发c ++，OLEDB，并以Jet后端为目标。我已经在项目后期意识到Jet后端太慢了，我需要重新定位。我不想重写我的源代码。我不想支付版税。我想要更好的表现。该应用程序是单用户，仅限本地访问，但需要高性能。
一般不需要花哨的功能......

任何人都可以推荐一个新的后端吗？

RDeW

I am developing in c++, OLEDB, and targeting the Jet backend. I have
realized late in the project that the Jet backend is too slow, and I need to
retarget. I do not want to rewrite my source code. I do not want to pay
royalties. I want better performance. The application is single user, local
access only, but needs high performance. Fancy features are not required in
general ...

Can anyone recommend a new backend?

RDeW

添加其他人提到的内容......

有些问题：


需要什么性能？今天是什么？

（具体数字，不仅仅是它似乎比它应该是b / b更慢。）


初步估算：你有相应的

指数设定吗？


二等概率：


我的经验，感知性能问题

几乎没有任何后端DBMS，但是可能是由于访问代码做了什么而导致


"不明智"。例如：


- 一个应用程序发出44个查询来填充屏幕上的44个字段。

- 另一个应用程序查询元数据

找出字段名称和属性然后

制定SQL动态查询

值。


-

不可能做任何万无一失的事情

因为傻瓜太聪明了

- A. Bloch

To add to what others have mentioned ...

Some questions:

What performance is required? What is it today?
(Specific numbers, not just "it seems slower than
it should be.")

First approximation: do you have the appropriate
indices set?

Second approximation:

In my experience, perceived performance problems
are hardly ever due to any back-end DBMS, but are
probably due to the access code doing something
"unwise." For example:

- An application which issued 44 queries to populate
44 fields on a screen.
- Another application which queried the meta-data
to find out the field names and attributes and then
formulated the SQL on the fly to query for the
values.

--
"It is impossible to make anything foolproof
because fools are so ingenious"
- A. Bloch

这篇关于非Jet OLEDB后端？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！