pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Simon Riggs <simon@2ndquadrant.com>
To: David.Bear@asu.edu
Cc: pgsql-admin@postgresql.org
Subject: Re: product feature sets
Date: Wed, 17 Nov 2004 23:34:27 +0000
Message-ID: <1100734467.4113.7795.camel@localhost.localdomain> (raw)
In-Reply-To: <20041117225617.GZ1041@asu.edu>
References: <20041117225617.GZ1041@asu.edu>

On Wed, 2004-11-17 at 22:56, David Bear wrote:
> This may sound like an impossible thing to ask because it may seem
> like an apples to oranges questions. If there were a book entitled
> "Using Postgresql with MS Access" I would suspect answers there.
> 
> Still I'm going to draw upon the collective experience of this list.
> 
> 1) are there any comparisons done between the relational features of
> ms-access vs postgresql?  Things like, does access enforce referential
> integrity... triggers... transactions... etc.  
> 

There is no need. Microsoft themselves explain how Access is not
suitable for use in business critical activities. PostgreSQL is
comparable with SQLServer, and clearly ahead of Access DB.

> 2) Since Access has the upsize tool that helps converting data to an
> ms-sql server, has anyone made a similar tool that helps with access?
> I have received from this group an email with some script in it that
> helps with table migration but I haven't had a chance to really
> understand what it does -- 

The upsize tool is a myth. SQLServer DBAs do not accept it, nor will
they accept the poor designs of Access databases. Replicating something
that exists only for marketing perceptions is not something that you'll
find people spending their time on.

This is the reason Access now provides "project files" that allow an
Access application to work against a SQLServer database.

The "Access problem" is one big reason PostgreSQL is well supported, and
will continue to be so. Microsoft are responding by making SQL Server
2005 free for use on one CPU... as if that helps.

-- 
Best Regards, Simon Riggs




view thread (2+ messages)

Message-ID: <1100734467.4113.7795.camel@localhost.localdomain>
Permalink:  ../1100734467.4113.7795.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1100734467.4113.7795.camel@localhost.localdomain

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: simon@2ndquadrant.com, David.Bear@asu.edu
  Subject: Re: product feature sets
  In-Reply-To: <1100734467.4113.7795.camel@localhost.localdomain>
  References: <20041117225617.GZ1041@asu.edu> <1100734467.4113.7795.camel@localhost.localdomain>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox