If you are really just duplicating the database, not using replication (transactions
performed on both databases more or less simultaneously) this is a very easy thing to
do.
Dump the table defininitions with the MS SQL Server scripting tool. Include the
indexes. Use your favorite scriptin
>Interesting. SQL Server -> Access is a done deal, so that is no problem.
>There are scripts already to move from Access -> PGSQL. (Not usually using
>ODBC; most instead generate an SQL dump, which you can then load. I think
>that's even nicer.)
>
>I guess it hangs on how much of the real stuff is
We have a need to replicate a Microsoft SQL server out to a PostgreSQL
server. Pretty much, the client uses SQL server right now, and we don't
want to expose that to the internet in any way, so we want to set up a
Postgres box with the same data at the colo facility. Also helps to have a
box you c
