Hi All,

I looking to learn/use an open source database (I've worked with MS SQL and more recently Oracle but want to try an OS one as well) and it comes down to PostgresSql and Firebird. Both of these support a wide range of features (although I think PostgresSql supports more) and with Version 8 of PostgresSql both now support Windows natively.

As part of my learning exercise I am going to be creating a site that could generate a lot of data (I know a lot is a bit subjective....lets just throw a number out there like 100GB). I also looking at the following:

• Best support for .Net
• Best support for LLBLGen Pro 2
• Easiest to maintain/support
• Least resource intensive

I know PostgresSql has been around for a while and it has better documentation but it seems that Firebird works best with .Net and works best on Windows (since it has had native support for windows for much longer).

I know this is all very general but was wondering what your opinions were.

Cheers

John

If the database will be big, I think postgresql will give you the best results. For .NET support, both providers are pretty OK, and also LLBLGen Pro support should be OK for both. If it doesn't really matter that much for database size, you're more flexible with firebird as you can also run that database 'embedded' which means you can use a dll and the db file and you can access the db, so you in that case don't need an installed service.

Otis wrote:

If the database will be big, I think postgresql will give you the best results. For .NET support, both providers are pretty OK, and also LLBLGen Pro support should be OK for both. If it doesn't really matter that much for database size, you're more flexible with firebird as you can also run that database 'embedded' which means you can use a dll and the db file and you can access the db, so you in that case don't need an installed service.

Thanks!

I already installed Firebird on my dev machine and it installs very easily. The database size could grow very large so I think I will now have a look at PostgresSql.

Thanks for the advice!