Both explanations sound very similar and very logical indeed.
Never occurred to me to think that way.
Actually, now I remembered, that in a few rare occasions we had to
restart the whole server after the "refresh" and then there was no
problem, at all.
Thank you both! Iv.
--
Sent via pgsql-
We are using PostgreSQL for more than 5 years by now and at least the
last 2-3 years we experience the following situation.
We refresh the live database on the development server using the
following shell script -
/usr/local/etc/rc.d/postgresql stop
rm -r /home/data/postgresql/data
/usr/loc
Gwyneth Morrison wrote:
Ray,
I think we tried that and I think it works but not for us. It may work
for you.
MS wants to copy all the tables over with exactly the same names
including [dbo]. and so on.
When it doesn't find an exact match, it wants to create the table. This
may be ok for you
Hi Ray,
I have something that does this. I am currently awaiting project
approval on pgfoundry.
It does tables, views, and stored procedures. I have tested it on
450,000 lines of mssql code
including 400 tables and 3700 stored procedures, although it is a work
in progress.
I applied last wee
Hello,
what is the current status of the MSSQL to PostgreSQL tools/tips?
Google returns results as old as 2001...
The MSSQL database in question has only tables, no stored procedures, etc.
Thanks,
Iv
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your
