.net - Are there any major pitfalls using PostgreSQL as a replacement for SqlSever -


I'm just one. Looking for the possibility of using postgresql as the option of sqlserver for the net web app.

(As a host of hosting a cloud, one hand and one leg is spent, your data size is 20 GB or greater)

So really looking for something good with performance that has a lot of information.

However, I'm not completely sure what I can lose by going to posgresql which can be seriously

me minor Issues, or porting issues are not concerned with any issues (until major blocking issues of porting).

We use NHibernate, Linq, as well as the raw SQL against the database (this is a legacy product which is gradually moving to NHibernate as your data access technology)

Unless you are using the features of SQL Server that are not available in postgrasqual, you should be fine. I am using both PostgreSQL and SQL Server on a daily basis and both work ado. It is OK for any Net-based application that accesses the database through Net and / or NHBnet. NHibernate has proven to be a good way to separate its code from the differences between these (and other) database servers.


Comments

Popular posts from this blog

Eclipse CDT variable colors in editor -

AJAX doesn't send POST query -

wpf - Custom Message Box Advice -