I can give one suggestion: DTS is your friend. At least for migration
of data. One other thought though, if you want to make any changes to
your db layout, do them in MS SQL while you still can. Pgsql is not
friendly to changes in db structure (dropping columns, changing data
types, etc). If you have a lot of changes to be done use the query
analyzer. DTS is too painful to do large scale changes in a migration.
Also, another reason for changing the data with MS SQL before importing
to pgsql is that it will take sometime when DTS is transfering the data
(at least an hour). When you do your migration the way to do is is
install the Pgsql ODBC driver on the MS SQL server, set it up, and
define it as you other data source in DTS.
Geoff
Andrew G. Hammond wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
> I know I saw an article recently about transitioning from MS SQL Server to
>Postgres, but I have no idea where. Anyone have any pointers?
>
>- --
>Andrew G. Hammond mailto:drew@xyzzy.dhs.org http://xyzzy.dhs.org/~drew/
>56 2A 54 EF 19 C0 3B 43 72 69 5B E3 69 5B A1 1F 613-389-5481
>5CD3 62B0 254B DEB1 86E0 8959 093E F70A B457 84B1
>"To blow recursion you must first blow recur" -- me
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.0.6 (GNU/Linux)
>Comment: For info see http://www.gnupg.org
>
>iEYEARECAAYFAjvyh9kACgkQCT73CrRXhLHwOwCfT5AJl9xGy1YXrW0U7pcMHGg5
>Zn4An0VCdAotkTEQkhie73kVDr4+EQ5I
>=/EOH
>-----END PGP SIGNATURE-----
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
>
