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? TSQL is very very different from any of the languages supported in PostgreSQL. You are most likely going to end up having to rewrite all the procedures more or less completely, unless they are just wrappers around single SQL statements (in which case you can use a SQL language one). One thing to note is that in PostgreSQL you can't just execute the typical "sp_myfunc" command as you would in MSSQL - you need to do "SELECT sp_myfunc()". That means you may need to change every call in the application, if that's the syntax you have been using. > Secondly, which commercial support vendor would you recommend? I found > EnterpriseDB and CommandPrompt, but I don't know anything about them. > Any other candidates? Depends completely on where in the world you are located. There is a list of providers available on our website at http://www.postgresql.org/support/professional_support The ones you recommended are both good, but depending on where you are there may be another good option available closer to you. //Magnus -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
