对于大型只读数据库进行研究,SQLite是否是一个不错的选择? [英] Is SQLite a good choice for a large, read only database for research?

查看:35
本文介绍了对于大型只读数据库进行研究,SQLite是否是一个不错的选择?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有很多记录(例如大约10到1亿条),我希望能够查询这些记录.

I have a large number of records (say around 10 to 100 million), which I want to be able to query.

这是一个研究项目,数据库将大部分是只读的,并且我一次只需要一个连接.我希望查询能够相当快.

This is a research project, the database is going to be mostly read only, and I only need one connection at a time. I would like the queries to be reasonably fast.

为此,SQLite是否是一个合理的选择?

Is SQLite a reasonable choice for this purpose?

推荐答案

我对SQLite的经验是,在大型记录集上,它的运行速度可能很慢,具体取决于您构造查询的方式.如果您的数据是非规范化的,并且可以通过对它的主键查询单个表来获得,那么它可以接受得很快.但是,如果您的数据是完全规范化的,并且您的查询涉及多个联接,那么它可能比客户端-服务器数据库慢得多..

My experience with SQLite is that it may be quite slow on large recordsets, depending on how you structure your queries. If your data is de-normalized and you can get by querying a single table against its primary key then it's acceptably fast, but if your data is fully normalized and your queries involve several joins then it can be much slower than a client-server database.

SQLite的主要优点是它的体积小和单个文件的特性,这使得分发嵌入在应用程序中变得容易.因为这似乎并不是您的必需条件,所以我认为您最好还是别的东西了.如果您使用Windows,MySQL或Postgres,则SQL Server Express很好,否则是一个不错的选择.

SQLite's principal advantage is its small size and single file nature that make it easy to distribute embedded in an app. As that doesn't seem to be a requirement for you though, I think you'd be better off going with something else. SQL Server Express is good if you're using Windows, MySQL or Postgres otherwise would be a good choice.

这篇关于对于大型只读数据库进行研究,SQLite是否是一个不错的选择?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆