On Fri, May 08, 2009 at 12:21:51AM -0700, 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 maki
On Fri, May 8, 2009 at 3:48 PM, Joshua D. Drake wrote:
> On Fri, 2009-05-08 at 10:11 +0200, Magnus Hagander wrote:
>> Eugene . wrote:
>
>> > Secondly, which commercial support vendor would you recommend? I found
>> > EnterpriseDB and CommandPrompt, but I don't know anything about them.
>> > Any ot
On Fri, 2009-05-08 at 10:11 +0200, Magnus Hagander wrote:
> Eugene . wrote:
> > Secondly, which commercial support vendor would you recommend? I found
> > EnterpriseDB and CommandPrompt, but I don't know anything about them.
> > Any other candidates?
>
As a person from Command Prompt :) we do ha
In response to johnf :
> On Friday 08 May 2009 12:08:44 am 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
On Friday 08 May 2009 12:08:44 am 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
On Fri, 2009-05-08 at 00:08 -0700, Eugene . wrote:
> 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 two companies operate mostly in US. There are various other
companies
Hi
I have migrated a very large database from MSSQL to PG. This was a
database of +/- 400 tables. You should note the following.
- MSSQL datatypes are not always compatible with PG datatypes. If you do
this carefully PG will save you a lot of time.
- The "timestamp" datatype of MSSQL is not t
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 simi
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 experi
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
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 som
11 matches
Mail list logo
