在设置具有外部表引用的数据库时，我应该注意哪些注意事项？
请不要笑，但我正在维护一个 Access 数据库，其中包含用于链接本地表的外部客户表。我想用 MySQL 或 SQL Server 后端在 ASP.NET 中重建它。我仍然需要引用外部表进行查询，但我从未设置过它。
对于外部连接来说，一个引擎是否比另一个引擎更好？是否还有其他考虑因素，例如安全性（外部凭据如何存储在每个凭据中）？
感谢您抽出时间，
汤姆
编辑：抱歉，我没有具体说明。我链接到的主数据库是外部 SQL Server 数据库，但它位于企业系统上。我维护的数据库适用于有权访问企业数据库的一个部门，但我无法在其中创建新表。
目前，.mdb 位于网络共享上，速度非常慢，如果单个用户没有正确关闭 Access，偶尔会出现问题。我正在尝试在网络应用程序上出售它们。
Please don't laugh, but I'm maintaining an Access database with an external customer table for linking the local tables. I'd like to rebuild this in ASP.NET with a MySQL or SQL Server backend. I will still need to reference the external table for queries, but I've never set this up.
Is one engine better than the other for external connections? Are there any other considerations, such as security (how are the external credentials stored in each)?
Thanks for your time,
Tom
Edit: Sorry, I didn't specify. The primary database I'm linking to is an external SQL Server database, but it's on an enterprise system. The database I maintain is for one department that has access to the enterprise database, but I can't create the new tables in it.
Currently the .mdb is on a network share that is painfully slow and occasionally has issues if the single user doesn't close Access properly. I'm trying to sell them on a web application.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我在这里只解决问题的“其他考虑因素”部分：
我对链接表的最大问题是从维护程序员的角度来看的。我无法告诉你我有多少次浪费时间跟踪链接表，因为它们的文档记录很差。我强烈建议甚至不要走“链接表”路线，但如果你这样做，我会强烈推荐某种方法来跟踪你的依赖关系。 （我们为此使用 Pathway Systems 的蓝图）。
没有什么比必须支持由多个 Access 数据库组成的应用程序更糟糕的了，这些数据库具有来回链接的表。如果处理不当，设置权限将是一场管理噩梦。
I'm only addressing the "other considerations" part of the question here:
The biggest problem I have with linked tables is from a maintenance programmer's perspective. I can't tell you how often I've wasted time tracing linked tables because they were poorly documented. I STRONGLY recommend not even going the "linked tables" route, but if you do, I would strongly recommend some way of tracking your dependencies. (We use Blueprints from Pathway Systems for this).
There are few things worse than having to support an app made up of multiple Access databases with linked tables going back and forth. And it's an administrative nightmare for setting permissions if not handled correctly.
我认为最灵活的数据库引擎是带有 mysql 的 innoDB，您可以在其中使用外键。这是安全的，因为您的数据库密码是秘密的，没有其他安全考虑。
I think that the most flexible db engine is innoDB with mysql where you can use foreing keys. This are secure as your db password is secret, no other considerations on security.