From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | "Eugene (dot)" <eugene750(at)yahoo(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: migrating from MSSQL |
Date: | 2009-05-08 07:40:07 |
Message-ID: | 4A03E1D7.5070002@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Eugene . wrote:
> Hi all,
>
> I've been tasked with evaluating the feasibility of migrating our
> in-house application from MSSQL to PostgreSQL. It is fairly old and
> has lots of stored procedures, which is why we need to think carefully
> before making the switch. Does anyone else have a similar experience?
> What are some of the things to watch out for?
>
from what all I gather, transact*SQL is -way- different, so you'll be
pretty much rewriting your procedures, you might consider just
rearchitecting the whole application. A lot of people are moving
their business logic out of stored procedures and into a application
server, programmed in a conventional language, such as Java, or Ruby, or
whatever, and just using stored procedures where it makes sense for
performance.
> Secondly, which commercial support vendor would you recommend? I found
> EnterpriseDB and CommandPrompt, but I don't know anything about them.
> Any other candidates?
Those are both fine upstanding members of the postgres community, each
employs a number of primary project developers, and both have a long
history of providing support.
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2009-05-08 08:11:13 | Re: migrating from MSSQL |
Previous Message | Eugene . | 2009-05-08 07:21:51 | migrating from MSSQL |