In order to move data and tables from MS SQL Server to PostgreSQL, use the
MS SQL Server DTS wizard and gave it the ODBC for PostgreSQL as the target
database.
--
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 1/23/07, Robert Fitzpatrick <[EMAIL PROTECTED]> wrote:
On Mon, 2007-0
On Mon, 2007-01-22 at 12:13 -0500, Ted Byers wrote:
> Is the original application ASP or SP.NET? It makes a difference,
> particularly if it was developed to take advantage of ASP.NET 2. It might
> conceivably be ASP.NET 3, but since that is brand new I can't see anyone
> paying to replace an
Robert Fitzpatrick wrote:
Any docs or other helpful info is welcome, just
looking for some advise.
One think I would recommend is to make sure when creating the new table
structure that you make
sure not to use capitalized object names. Because MS SQL server can be
case insensitive I have
Is the original application ASP or SP.NET? It makes a difference,
particularly if it was developed to take advantage of ASP.NET 2. It might
conceivably be ASP.NET 3, but since that is brand new I can't see anyone
paying to replace an ASP.NET 3 application that was just created. If it is
ASP.
On Mon, 2007-01-22 at 16:32 +, Peter Rosenthal wrote:
> Wanting to do something similar I recently submitted a large patch to
> the mysql2pgsql project. It will now handle conversion of a mysqldump
> file complete with data for the quite large and diverse DB I was using
> it with. I'm sure ther
Wanting to do something similar I recently submitted a large patch to the
mysql2pgsql project. It will now handle conversion of a mysqldump file
complete with data for the quite large and diverse DB I was using it with.
I'm sure there are still corner cases, but you should give it a try:
http://g
