# Any reason not to use SQLite3?

**URL:** <https://www.ruby-forum.com/t/any-reason-not-to-use-sqlite3/156977>\
**Category:** Radiant CMS\
**Created:** [January 5, 2009, 11:50pm UTC](https://www.ruby-forum.com/t/any-reason-not-to-use-sqlite3/156977 "2009-01-05T23:50:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nateless](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/96bed5/32.png) [@nateless](https://www.ruby-forum.com/u/nateless)\
**Post date:** [January 5, 2009, 11:50pm UTC](https://www.ruby-forum.com/t/any-reason-not-to-use-sqlite3/156977/1 "2009-01-05T23:50:37Z")

</div>

Since Radiant is meant for more medium scale projects, is there any real  
drawback to using an SQLite3 database instead of the heavier-duty MySQL?  
Sort of thinking out loud here. I have my projects now managed with git,  
but  
to move the database content from my local machine to the production  
server  
I am doing a dump then import approach. Is there a better way? Perhaps  
something that can be automated into a deploy.rb file?

~Nate

---

<div class="post-metadata">

**Author:** ![nateless](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/96bed5/32.png) [@nateless](https://www.ruby-forum.com/u/nateless)\
**Post date:** [January 6, 2009, 12:51pm UTC](https://www.ruby-forum.com/t/any-reason-not-to-use-sqlite3/156977/2 "2009-01-06T12:51:18Z")

</div>

Hi Nate,

As far as my experience goes, I can see no problem in using sqlite as  
a production database. Indeed, my site is about 200 pages with average  
of 4000 to 5000 pageviews per day and sqlite is handling it with no  
problems.

The only case I wouldn’t recomend sqlite is if you perform a bunch of  
concurent writes to the database, then sqlite is not the tool,  
otherwise if it’s mainly reads sqlite will do fine.

2009/1/5 Nate T. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid):