Re: Migration from SQLServer - Mailing list pgsql-general

From Tapan Trivedi
Subject Re: Migration from SQLServer
Date
Msg-id 3EC4A602.3000003@webifyservices.com
Whole thread Raw
In response to Re: Migration from SQLServer  ("Nigel J. Andrews" <nandrews@investsystems.co.uk>)
Responses Re: Migration from SQLServer  (Jeff Eckermann <jeff_eckermann@yahoo.com>)
List pgsql-general
Thanks Nigel but too late :-((

Did try something and got really messed up. I guess database recreation
is the only alternative left. Actually wanted to do this in 2 hrs time -
already am late by a day.

Thanks anyway.

Tapan

Nigel J. Andrews wrote:

>On Fri, 16 May 2003, Nigel J. Andrews wrote:
>
>
>
>>On Fri, 16 May 2003, Tapan Trivedi wrote:
>>
>>
>>
>>>b. Create script. Let me explain - I generated the script from MSSQL and
>>>it gave a whole lot of issues (for SQL statements and types) . When  I
>>>resolved all of them, I encountered Relation ".." not found error. The
>>>only way I could resolve it was by giving the table names in quotes. I
>>>guess I should have converted all table names in lowercase and then all
>>>would be OK.
>>>
>>>What I am trying to find out now is - Is there anyway I can avoid
>>>dropping the database and recreating it ??
>>>
>>>
>>Sure, take a look at relname in pg_class and typname in pg_type.  The other
>>columns in those table will help you decide who owns what and what schema
>>they're in so you can change only those ones you want to.
>>
>>
>
>Oh, and don't forget to start a transaction before making the changes so that
>you get the chance to rollback if you make a mistake, these are system tables.
>
>
>--
>Nigel Andrews
>
>
>
>



pgsql-general by date:

Previous
From: "Nigel J. Andrews"
Date:
Subject: Re: Migration from SQLServer
Next
From: "Bartlomiej Frackiewicz"
Date:
Subject: Rollback when value too long