First, WHY move off sqlite.
Hosting companies are a dime-a-dozen.
sqlite is a library, it's part of your code, you are not asking the
provider to set up
or maintain another RDBMS engine.
Option one in my opinion is to find a cooperative hosting company and
move you
app unmodified.
IF your app is currently running on your PC and IF it's currently
running sqlite
and IF your design and SQL code are reasonably optimized I highly doubt
you'll find anything that cane come close speed-wise.
IF you do have a poor design and are forced to fix it in order to
migrate it may be
faster once you are done, but that doesn't count. ;-).
I'm an Oracle DBA I make good money doing it, but I'm not beyond using a
more
appropriate database for a given situation.
Just to muddy the waters a bit more...
Oracle has a free version for windows and linux that is good for a 1 GB
or smaller database
if I recall.
DB2 has just been released for free on windows and linux for machines
with up to 2 dual Core
processors and 4 Gig RAM. No limits of database size.
Oracle just changed the way they license multi-core processors but List
price for the
enterprise edition for a 2 CPU dual core machine it still $100,000 list.
I currently support about 20 Oracle instances driving 5 commercial
applications which cost
about 150 million dollars to develop.
From what I've seen so far this free version of DB2 running on good
linux hardware would
outrun the sun/oracle systems for about 1/5th the cost.
Jim C. Nasby wrote:
See also http://sql-info.de/mysql/gotchas.html.
About the only downsides I can think of with PostgreSQL is that it's
out-of-the-box configuration is meant for like a 486 and that not quite
as many hosting providers offer it. That url has about 100 downsides to
MySQL (many of which are rather serious). PostgreSQL is also strives to
stay as close to ANSI SQL as possible and makes it nearly impossible to
configure your database in such a way that it's only a matter of time
and luck before you end up with corrupted data.
Granted, MySQL added a lot of features in 5.0, but they still focus much
less on doing things the right way than PostgreSQL does.
And remember: Feb 31st isn't a date. :)
On Thu, Feb 09, 2006 at 07:47:47AM +1100, John Stanton wrote:
PostgreSQL implements standard SQL as well as the features of an
enterprise DBMS. On that basis if you are changing it makes sense to
change to the fuller-featured product, one in the same class as Oracle
and DB2. In the short term Mysql could be as good as PostgreSQL.
Fanda Vacek wrote:
I'm not sure, if Postgres is better choice than MySQL. I have used both
of them to find out which is the better one. Both of them can do
almost anything. The choice is a matter of taste and person. We are
free to choose:)) I'm talking about MySQL 5 and PostgreSQL 8.1.
Sorry for writing this to SQLite mail-list.
Fanda
On Tue, 07 Feb 2006 22:35:09 +0100, John Stanton <[EMAIL PROTECTED]>
wrote:
Jim C. Nasby wrote:
On Mon, Feb 06, 2006 at 05:30:39PM +0100, Laurent Goussard wrote:
Hi there,
I use SQLite on my website for 2 years now. I do like SQLite a lot and
will use it for a lot of new web projects but, because I got more and
more traffic, I consider to move this one to MySQL in order to reduce
the over load of my computer (I host it @ home).
Do you know if there is a way to convert easily an SQLite database
into a MySQL one ?
(I'm especially thinking about the escapestring and other "create
table [myTable] {" issues...)
FWIW, I believe SQLite's syntax is closer to PostgreSQL's than it
is to
MySQL, so it might me easier to migrate that direction...
If you are migrating to an enterprise level DBMS, PostgreSQL is a
better choice than Mysql. It is fully featured with all the
qualities of DB2 and Oracle but without the expense.
Note that you will need considerably more machine resources to run a
"heavier" DBMS than Sqlite. For example on our 166MHz, 256MB RS/6000
PostgreSQL is sluggish but on our dual processor 1.2GHz, 2GB P-Series
it is lightning fast. Sqlite runs fast on the 166MHz machine.
