PostgreSQL with .NET

  • Thread starter Thread starter Penelope Dramas
  • Start date Start date
P

Penelope Dramas

Hello,

We have decided to change our database back-end from MSDE to postgreSQL.

Would anyone please share his/her experience with this database as far as
speed, functionality and security concerns.


Thanks,

Pen D.
 
Hello,

We have decided to change our database back-end from MSDE to
postgreSQL.

Would anyone please share his/her experience with this database as far
as speed, functionality and security concerns.
Click to expand...


Any particular reason you're going with Postgres and not something like
that SQL Server Express, MySQL or SQL Server? These databases have a more
active .NET developer base.
 
Penelope said:
Hello,

We have decided to change our database back-end from MSDE to
postgreSQL.

Would anyone please share his/her experience with this database as
far as speed, functionality and security concerns.
Click to expand...

PostgreSql is very reliable, well documented and has a rich set of
functionality. They had a vulnerability some time ago but that was
patched as well. The .NET provider for PostgreSql is OK, and is
actively maintained.

FB

--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
 
Hello,

We have decided to change our database back-end from MSDE to postgreSQL.

Would anyone please share his/her experience with this database as far as
speed, functionality and security concerns.

Thanks,

Pen D.
Click to expand...

PostgreSQL is a pretty good database. I don't think you have much to worry
about. Personally I would move to SQL Express ... Much better in the sense
that it has increased security, easier to deploy, improved performance and
most importantly no need to rewrite queries, views, etc
 
Sorry for late reply, was out of office yesterday.

Thank you all for answers, I'm sure PostgreSQL will do good for us.

We're having issues with 1cpu limit, application performance dropped by 25%
when switched to SQLExpress. Our customers mainly have dual (physical) CPU
servers.


MSDE 2000 was perfect product, free and good, I don't know why, except for
money reason, Microsoft would introduce so much limitations to SQLExpress
comparing to MSDE (1cpu limit, no agent, ...)
 
Just to add that we wanted to add Unix/Linux server compatibility to our
application. Clients will obviously have to remain on Windows due to .net.


Penelope Dramas said:
Sorry for late reply, was out of office yesterday.

Thank you all for answers, I'm sure PostgreSQL will do good for us.

We're having issues with 1cpu limit, application performance dropped by
25% when switched to SQLExpress. Our customers mainly have dual (physical)
CPU servers.


MSDE 2000 was perfect product, free and good, I don't know why, except for
money reason, Microsoft would introduce so much limitations to SQLExpress
comparing to MSDE (1cpu limit, no agent, ...)
Click to expand...
 
Just to add that we wanted to add Unix/Linux server compatibility to our
application. Clients will obviously have to remain on Windows due to .net.

Penelope Dramas said:
Sorry for late reply, was out of office yesterday.

Thank you all for answers, I'm sure PostgreSQL will do good for us.

We're having issues with 1cpu limit, application performance dropped by
25% when switched to SQLExpress. Our customers mainly have dual (physical)
CPU servers.


MSDE 2000 was perfect product, free and good, I don't know why, except for
money reason, Microsoft would introduce so much limitations to SQLExpress
comparing to MSDE (1cpu limit, no agent, ...)
Click to expand...

Ah, cross platform compatibility is a whole different ball game.
Click to expand...
 
Hi,
Last year I've got some experience with PostgreSQL migration from SQL
server 2000 of real world working database.
One of the most common problems after porting data to the particular
data types implemented in the RDBMS is porting the functionality.

MS SQL server is the only RDBMS which serves multiple result sets, thus
implementation of that kind of stored procedures is impossible in
PostgreSQL (although its my favorite open source DB).

Further more - /stored procedures are functions in Postgresql/, there
were some additional problems with output parameters and other small but
very important issues related to it, which were hard to overcome.

My advice is to stay with SQL server - it's really the best choice, if
you are determined to present professional solution. For educational,
and proof-of-concept, etc. experiments - PostreSQL is ok. SQL is the
leading one, much more reliable, scalable and flexible. Well it's not
perfect but it's ages in front of the others (with features like DDL
triggers in the new 2K5, XML Indexes, materialized views and etc.)

Regards,
Petar Atanasov
http://a-wake.net

p.s.
MySQL - out of the discussion - we're talking about databases ;)
 
Back
Top