Re: [ADMIN] SQL Server 2000 to PostgreSQL 8.0.3

2005-08-14 Thread Sergey Moiseev
[EMAIL PROTECTED] wrote: I am having difficulty moving a SQL Server 2000 database over to PostgreSQL 8.0.3. In SQL Server, I am performing a backup of the database I want to move. I save that backup on my Desktop. I am then opening up PGAdminIII and attempting to perform a Restore of the

Re: [ADMIN] SQL Server 2000 to PostgreSQL 8.0.3

2005-08-10 Thread Joshua D. Drake
[EMAIL PROTECTED] wrote: I have successfully migrated my db from SQL Server to PostgreSQL. (Aqua Data Studio 4.0 did the trick) If you are comfortable with Aquastudio then just Aquastudio to push it to your Linux box :) Sincerely, Joshua D. Drake -- Your PostgreSQL solutions company - C

Re: [ADMIN] SQL Server 2000 to PostgreSQL 8.0.3

2005-08-10 Thread [EMAIL PROTECTED]
I have successfully migrated my db from SQL Server to PostgreSQL. (Aqua Data Studio 4.0 did the trick) Now, I need to move this PG db from its current installation on Windows over to my RedHat box. So, I performed a Backup on my Windows machine and saved the .backup file to my Windows Deskt

Re: [ADMIN] SQL Server 2000 to PostgreSQL 8.0.3

2005-08-09 Thread Tom Lane
Ben Kim <[EMAIL PROTECTED]> writes: >> In reviewing my tables, I found that for some strange reason a handful >> of fields are not double-quoted. Strange quirk: >> ... > In my case, DTS's "create" always wrapped the field names with double > quote. The script seems to me not from DTS. I think i

Re: [ADMIN] SQL Server 2000 to PostgreSQL 8.0.3

2005-08-09 Thread Ben Kim
>In reviewing my tables, I found that for some strange reason a handful >of fields are not double-quoted. Strange quirk: >-- Table: "Orders" > >-- DROP TABLE "Orders"; > >CREATE TABLE "Orders" >( > "OrderID" int4 NOT NULL, > "CustomerID" int4 NOT NULL, > "DateCreated" timestamptz, > "TotalPri

Re: [ADMIN] SQL Server 2000 to PostgreSQL 8.0.3

2005-08-09 Thread [EMAIL PROTECTED]
I have successfully moved the schema over to PostgreSQL. Now I am working on the data. In reviewing my tables, I found that for some strange reason a handful of fields are not double-quoted. Strange quirk: -- Table: "Orders" -- DROP TABLE "Orders"; CREATE TABLE "Orders" ( "OrderID" int4 N

Re: [ADMIN] SQL Server 2000 to PostgreSQL 8.0.3

2005-08-09 Thread Ben Kim
Here's my 2 cents. If you have access to DTS in SQL Server 2000, it will be one convenient solution for simple transfer. It's a matter of creating a new task, defining the SQL Server database as source and PostgreSQL database as destination, and clicking through. There will be some mismatches in

Re: [ADMIN] SQL Server 2000 to PostgreSQL 8.0.3

2005-08-09 Thread Goulet, Dick
Check out WinSql (http://www.synametrics.com/SynametricsWebApp/WinSQL.jsp) It has the ability to extract data from Sql*Sucker and drop it into PostGreSql, and you can have that functionality free for 90 days to boot. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On

Re: [ADMIN] SQL Server 2000 to PostgreSQL 8.0.3

2005-08-09 Thread Joel Fradkin
Only thing you may run into moving data is field types. I had to convert my bit fields to binary and my datestammp to timestamp. I would just be sure the field types are supported or you may have to do a search replace on the text file created by aquastudio. Although when I used aqua I exported us

Re: [ADMIN] SQL Server 2000 to PostgreSQL 8.0.3

2005-08-09 Thread James Herbers
[EMAIL PROTECTED] wrote: Greetings. I am having difficulty moving a SQL Server 2000 database over to PostgreSQL 8.0.3. In SQL Server, I am performing a backup of the database I want to move. I save that backup on my Desktop. That backup is in Microsofts own format, PostgreSQL will not be

Re: [ADMIN] SQL Server 2000 to PostgreSQL 8.0.3

2005-08-09 Thread Joel Fradkin
I am pretty sure a backup from sql is not going to restore on postgres. I wrote a .net application that read from one and wrote to the other. Does not like tables large then memory available though, since npgsql .net components by default uses a read whole table approach (there is a cursor way, but