June 11, 2011 at 11:22 am
Hi All,
I came to know that PostGreSQL is a RDBMS. can any one of you came accross of this technology ? how will be the future if we work on this ?
Thank You.
Regards,
Raghavender Chavva
June 11, 2011 at 11:28 am
PostgreSQL is an Open Source Database.
I converted a Database from PostgreSQL to SQL Server several years ago.
I can't speculate on it's future but if you can afford a license my preference would be SQL Server.
http://www.postgresql.org/docs/
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
June 12, 2011 at 6:39 am
Raghavender (6/11/2011)
I came to know that PostGreSQL is a RDBMS. can any one of you came accross of this technology ? how will be the future if we work on this ?
PostgreSQL is a Oracle what MySQL is a SQL Server; an open source, several versions behind rdbms.
If you are a SQL Server DBA looking for an "open source" alternative I'll suggest to look into MySQL, on the other hand if you are an Oracle DBA I'll suggest to favor PostgreSQL.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.June 12, 2011 at 7:15 pm
The following URL contains a comparison of PostgreSQL 8.4, Microsoft SQL Server 2008 & MySQL 5.1:
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
June 15, 2011 at 10:38 pm
PostgreSQL (PGS) actually offers a far more feature-complete database engine than MySQL. In terms of PGS's query optimizer, locking mechanisms, push for ANSI-SQL compliance and language features/extensions it rivals, and in some areas exceeds, the quality of SQL Server. MySQL is nowhere as robust a database engine as PostgreSQL. Where PGS falls down is as a platform. PGS offer very few tools and sub-systems that SQL Server users have come to take for granted. MySQL has done a better job of keeping up on that front as well as at grabbing the web development community (and headlines) but at the peril of their database engine which is inferior when compared to all of the other RDBMS's mentioned.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
June 17, 2011 at 3:18 pm
Raghavender (6/11/2011)
Hi All,I came to know that PostGreSQL is a RDBMS. can any one of you came accross of this technology ? how will be the future if we work on this ?
Your future depends both on the features in your particular version of Postgres (http://www.postgresql.org/about/featurematrix), and the tool you use.
Just as you could use osql to access SQL Server from the command line, it's much easier to use the free pgAdmin3 (http://www.pgadmin.org/index.php) tool, like SSMS (though not as nice).
SQL Server 2008 did a lot of catching up - the Date data type and filtered ("partial") indexes, for example, has been in Postgres for some time. Similarly, Postgresql has been doing catching up of its own (hot backup and other replication, role security, etc).
Postgres "Tablespaces" can be used like "Filegroups" to specifically put certain objects on certain spindles (just as you could have a SQL Server Filegroup on Raidset A and another Filegroup on RaidsetB, you can do the same with Postgresql Tablespaces).
Just as Oracle has performance tuning features SQL Server does not (multiple block/page sizes), SQL Server does have performance tuning features Postgres either does not have, or has hidden away in the usual *nix-style config files. You'll have to set Postgresql to use reasonable amounts of memory; the defaults are pretty low. Note that Postgres depends on the OS to do file caching, very unlike SQL Server.
Note that Postgres, does have automated maintenance "autovacuum" enabled by default.
There are quite a few newer features available; perhaps my favorite is a constraint that prevents overlapping date ranges with an "exclusion constraint" (http://wiki.postgresql.org/wiki/What%27s_new_in_PostgreSQL_9.0#Exclusion_constraints).
If you encounter reserved word issues, try using " (double quotes) where you might use [] (square brackets) in SQL Server.
Note that some upgrades require backing up your databases, upgrading, and restoring them; read the upgrade docs each time, they state this quite clearly.
As far as MySQL vs. Postgresql, a reasonably up to date comparison is at http://www.wikivs.com/wiki/MySQL_vs_PostgreSQL
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply