Moving from mssql to postgres, advice needed

We have a couple of MS SQL Server 2000/2005 databases with a bunch of ..NET clients written in C#, but may want to replace the dbserver with postgres instead. The clients will still run on Windows, hopefully with as few changes as possible.

We don't have any stored procedures or triggers, so all we need to port are the tables/index definitions.

What are the most common issues/problems people run into on the client side? My guesses are stuff like
- identity columns
- transaction handling(autocommited vs. implicit)
- date and datetime
- general error handling and error codes

Anything else?

I've googled for migration guides and howto's, but without success. Pointers to such are appreciated.

Boa
.

Relevant Pages

  • Re: Moving from mssql to postgres, advice needed
    ... but may want to replace the dbserver with postgres instead. ... The clients will still run on Windows, hopefully with as few changes as possible. ... general error handling and error codes ...
    (comp.databases.ms-sqlserver)
  • Re: OT ? For Computer Experts
    ... So yeah, I like it when clients call me. ... But you don't have a bunch of clueless secretaries calling you once or ...
    (rec.motorcycles)
  • A patch causes network problems
    ... One of my clients finally ran the Windows Update for the ... first time in about a year. ... Installed a bunch of stuff ...
    (microsoft.public.windowsupdate)
  • Re: MS Access forum
    ... > Here's another one of the bunch of losers! ... How do you have time to do all the work for your thousands of clients when ... Prev by Date: ...
    (comp.databases.ms-access)
  • Re: Restrict Remote Access (SBS2003)
    ... They had an employee steal a bunch of their best clients. ... don't have a business need to. ... Is there anyway I can restrict remote access just using the SBS2003 ...
    (microsoft.public.windows.server.sbs)