help in migrating database

[dodie]

---

[TABLE BY TABLE METHOD]
pwede nimo i-convert to *.csv (comma separated value) file, then parse the data before migrating...

[MIGRATION TOOL]

Download nalng ug software...

I think you are converting it twice(2).
It's better if you parse it directly into Postgre format. In that way, it's more controlled and you can monitor all.

[snaxnacu]

I think you are converting it twice(2).
It's better if you parse it directly into Postgre format. In that way, it's more controlled and you can monitor all.

Actually, wala pa ko nakagamit ug POSTGRE, but i think converting it directly to postgre format will have datatype issues. Same with MSSQL to ORACLE.

By Converting it *.csv ang iya data will be string, after parsing the data from *.csv, then thats the time i-insert sa table na manually created, at least ang mga datatype kay han-ay na.

Thanks

[dodie]

Actually, wala pa ko nakagamit ug POSTGRE, but i think converting it directly to postgre format will have datatype issues. Same with MSSQL to ORACLE.

By Converting it *.csv ang iya data will be string, after parsing the data from *.csv, then thats the time i-insert sa table na manually created, at least ang mga datatype kay han-ay na.

Thanks

I think you didn't got the point. I meant was converting it direcly into POSTGRE sql format.

.csv, is a text format.
.sql, is also a text format.

If we undergo CSV, that means you are parsing twice.
If you parse it into POSTGRE text file command, you are parsing directly.

DATATYPES doesn't matter as long as you include it properly in the commands within your SQL text file.

sometimes CSV has issues. Because sometimes it does not target the actual arrangement of the fields.

[ingkiang]

i thought wla maka tabang nko ngari..karon pako ni balik ug visit ani nga thread..hehe...
daghan man d i ang nang reply...

What ever the database type or table types, always think about compatibility. There are also TOOLS out there might be useful (with payment or free) in some ways they are not compatible with your created system made from scratch by your own hands.

The best method is to create a script or program to REGENERATE the SQL scripts command from the MSSQL application database. Your aim is to REGENERATE DATA SQL COMMANDS into POSTGRESQL.
Create a file called. postgresql_new.sql <--- text file, contains sql commands.


Execute the sql file command into the postgresql manually and wait for it. If there is COMMAND LINE tool available in it then use it. It is very useful if you have very large data without worrying about TIME LIMITATION.

Trust me, this really works. bwahahahahaha

this is what i did...mas nice xa ky control nmo tanan, bt ikaw jud mobuhat sa structure sa database nga imong balhinan....i think my mssql to postgresql data migration is successfull...hahah...wla pa jud nuon macheck nko tanan nga data...bt so far so gud...heheh..

[service.raymond]

why not make a program to transfer your data.

[dodie]

why not make a program to transfer your data.

OMFg are you blind please read the post.