Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-12 Thread Matt Quackenbush
All- I am very pleased to announce that I have the entire SQL Server database duplicated on PostgreSQL, indexed, PKs, FKs, clustered, etc, and it ROCKS! Not only that, but my 43-line queries all work properly and are lightening fast! Unless I come across something completely unexpected, I feel co

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-12 Thread Jon Clausen
Glad to help. Have fun. :-) -Jon On Jan 12, 2007, at 4:52 PM, Matt Quackenbush wrote: > Jon, > > Your solution worked just fine actually :-) Thanks again! > > > Matt > ~| Create robust enterprise, web RIAs. Upgrade & integ

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-12 Thread Matt Quackenbush
Jon, Your solution worked just fine actually :-) Thanks again! Matt ~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adob

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-12 Thread Jon Clausen
Truthfully,I've always done it with CF so I don't know what the fully query would be with postgres. You can run the following query to get the table names and primary key names (where they are defined) select table_name, column_name from information_schema.constraint_column_usage ; Then ju

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-12 Thread Matt Quackenbush
Jon, Thanks for the reply. Indeed I did miss it. I was hoping to write one long ..sql script and run it from my query editor and update all tables in a single connection. Are you aware of a way to do that? If not, I'll use your CF solution :-) Matt On 1/12/07, Jon Clausen <[EMAIL PROTECTED

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-12 Thread Jon Clausen
Matt, I sent in a previous e-mail but you may have missed it: SELECT pg_catalog.setval(pg_catalog.pg_get_serial_sequence ('#table#','#table_id#'), (SELECT max(#table_id#) FROM #table#), true); That way you don't have to provide the sequence name. HTH, Jon On Jan 12, 2007, at 2:41 PM, Matt Qu

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-12 Thread Matt Quackenbush
I don't know why i wrote the '+1' in there when I wrote the email. I'm not using it in the actual statement. The specific syntax error is that the ( is invalid. On 1/12/07, Matt Quackenbush <[EMAIL PROTECTED]> wrote: > > Okay, so far I'm *really* liking Pg. I have successfully imported all of >

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-12 Thread Matt Quackenbush
Okay, so far I'm *really* liking Pg. I have successfully imported all of my tables and data, and have everything fixed with one exception: updating the currval() of the sequence for the 'auto_number' fields. I can go through each sequence one at a time with the GUI and update it, but I'd obviousl

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-12 Thread Jochem van Dieten
David Livingston wrote: > If you just want a single IP to be able to connect the format is > 555.555.555.555/0 . > Obviously you replace the 555 stuff with your IP. It is the other way around. /32 means 1 IP address, /0 means all IP addresses. The number after the slash is the number of bits in

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-11 Thread David Livingston
If you just want a single IP to be able to connect the format is 555.555.555.555/0 . Obviously you replace the 555 stuff with your IP. Dave On Jan 11, 2007, at 4:14 PM, Matt Quackenbush wrote: > Jochem, > > Thank you. That was the problem. I didn't realize that it was > needed. > Remote c

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-11 Thread Matt Quackenbush
Jochem, Thank you. That was the problem. I didn't realize that it was needed. Remote connection up and running; time to play! :-) Matt On 1/11/07, Jochem van Dieten <[EMAIL PROTECTED]> wrote: > > How did you write your IP address? Did you add the /32 to use > *CIDR-address* notation? > > Jo

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-11 Thread Jochem van Dieten
Matt Quackenbush wrote: > > host *database* *user* *CIDR-address* *auth-method* [*auth-option*] > host *database* *user* *IP-address* *IP-mask* *auth-method* > [*auth-option*] > My pg_hba.conf file contains the following lines (below all of the > instructions): > > # TYPEDATABASE

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-11 Thread Matt Quackenbush
On 1/11/07, Jochem van Dieten <[EMAIL PROTECTED]> wrote: > > > LOG: invalid IP mask "password" in file "C:/Program > > Files/PostgreSQL/8.2/data/pg_hba.conf" line 72: Unknown host > > You are missing a column in your pg_hba.conf. Do you have the real one > somewhere? > > Jochem Which column am

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-11 Thread Jochem van Dieten
Matt Quackenbush wrote: >> This is a bad combination because they result in a cleartext communication >> and even a cleartext password. Best would be to install a certificate and >> use hostssl instead of host, but at least you should use md5 instead of >> psssword. > > Thank you for the tip on the

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-11 Thread Matt Quackenbush
Jochem, This is a bad combination because they result in a cleartext communication > and even a cleartext password. Best would be to install a certificate and > use hostssl instead of host, but at least you should use md5 instead of > psssword. Thank you for the tip on the ssl/md5/password issue

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-11 Thread Jochem van Dieten
Matt Quackenbush wrote: > Hmmm... I setup PostgreSQL on one of my production (remote to me) servers. > It's all working wonderfully from localhost. To prepare it for allowing > remote access, I added the following line to the pg_hba.conf file: > > hostsameuserall (the IP, e.g. 555.55

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-11 Thread Matt Quackenbush
Hmmm... I setup PostgreSQL on one of my production (remote to me) servers. It's all working wonderfully from localhost. To prepare it for allowing remote access, I added the following line to the pg_hba.conf file: hostsameuserall (the IP, e.g. 555.555.555.555)password I then add

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-10 Thread Jim Wright
Dave Watts wrote: >> Am I correctly understanding what I'm reading on their site >> that Aqua Data Studio supports ALL of the listed databases in >> the same client? (As opposed to having a different one for each DB?) > > Sure. It's a JDBC client, just like CF. I doubt it provides GUI managemen

RE: Transferring from MS SQL (2000) to PostgreSQL

2007-01-10 Thread Dave Watts
> Am I correctly understanding what I'm reading on their site > that Aqua Data Studio supports ALL of the listed databases in > the same client? (As opposed to having a different one for each DB?) Sure. It's a JDBC client, just like CF. I doubt it provides GUI management functionality found in

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-10 Thread David Livingston
I concur with Jon. I'd use Character Varying. Dave On Jan 10, 2007, at 5:31 PM, Jon Clausen wrote: > No you're right - now days. I've had some issues with older drivers > where they would throw a syntax error on me so I always use character > varying with Pg just to be on the safe side. > > On

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-10 Thread Jon Clausen
No you're right - now days. I've had some issues with older drivers where they would throw a syntax error on me so I always use character varying with Pg just to be on the safe side. On Jan 10, 2007, at 6:10 PM, Matt Quackenbush wrote: > Sweet (regarding the single interface)! > > Jon, I wa

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-10 Thread Matt Quackenbush
Sweet (regarding the single interface)! Jon, I was under the impression that varchar() was still a valid datatype in Postgre, and would not require changing to 'character varying'. http://www.postgresql.org/docs/8.2/static/datatype-character.html Am I mis-reading that? Dave, Thanks for the tip

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-10 Thread Jon Clausen
On Jan 10, 2007, at 5:13 PM, Matt Quackenbush wrote: > Am I correctly understanding what I'm reading on their site that > Aqua Data > Studio supports ALL of the listed databases in the same client? > (As opposed > to having a different one for each DB?) Yes. It rocks! Dave L's instructions

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-10 Thread Jim Wright
Matt Quackenbush wrote: > Am I correctly understanding what I'm reading on their site that Aqua Data > Studio supports ALL of the listed databases in the same client? (As opposed > to having a different one for each DB?) > Yes...it is very nice having the same interface for multiple database sys

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-10 Thread Matt Quackenbush
Am I correctly understanding what I'm reading on their site that Aqua Data Studio supports ALL of the listed databases in the same client? (As opposed to having a different one for each DB?) ~| Create robust enterprise, web RIAs

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-10 Thread David Livingston
Here is what I have done in the past. Use enterprise manager to script out the tables to a sql script. Then do a find an replace on the script to convert the data types and remove all of the MS specific stuff. Once you have a good generic SQL script run it on postgres to create all of your

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-10 Thread Jim Wright
Matt Quackenbush wrote: > Jim, > > Are you referring to v6 RC1? That's all I've seen so far on their site. > Yes, I believe that is the latest version...but I think the 4.7 version also had the export capability I was describing. I went ahead and started using the RC because I wanted to use

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-10 Thread Matt Quackenbush
Joshua, Thanks for the pointer and the link. Jim, Are you referring to v6 RC1? That's all I've seen so far on their site. Thanks, Matt On 1/10/07, Jim Wright <[EMAIL PROTECTED]> wrote: > > Joshua Cyr wrote: > > Wasn't Aqua Data Studio free at one point? I swear I didn't buy it... > but >

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-10 Thread Jim Wright
Joshua Cyr wrote: > Wasn't Aqua Data Studio free at one point? I swear I didn't buy it... but > could be forgetting. I don't do the warez thing, so either it was > legitimately free at one point or very inexpensive or I am losing too many > brain cells on WOW. > Prior to the current version 6, i

RE: Transferring from MS SQL (2000) to PostgreSQL

2007-01-10 Thread Joshua Cyr
[mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 4:17 PM To: CF-Talk Subject: Re: Transferring from MS SQL (2000) to PostgreSQL Joshua Cyr wrote: > I have used Aqua Data Studio for just that task. (mysql and mssql to > postgre). I had to do it table by table, but I did it for m

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-10 Thread Jim Wright
Joshua Cyr wrote: > I have used Aqua Data Studio for just that task. (mysql and mssql to > postgre). I had to do it table by table, but I did it for millions of > records with relative ease. Export to delimited text file or file with > insert statements, then import to the other db. > > http://w

RE: Transferring from MS SQL (2000) to PostgreSQL

2007-01-10 Thread Joshua Cyr
Savvy Software 866.870.6358 www.besavvy.com -Original Message- From: Matt Quackenbush [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 3:50 PM To: CF-Talk Subject: Transferring from MS SQL (2000) to PostgreSQL Hello, I have a heavily used and ever-growing MS SQL database that

Re: Transferring from MS SQL (2000) to PostgreSQL

2007-01-10 Thread Matt Quackenbush
I have found this software, but it appears to be brand new. Has anyone had any experience with it? Or with something similar that you would recommend? http://www.download3k.com/Business-Finance/Database-Management/Download-MS-SQL-Server-PostgreSQL-Import-Export-Convert-Software.html ~~

Transferring from MS SQL (2000) to PostgreSQL

2007-01-10 Thread Matt Quackenbush
Hello, I have a heavily used and ever-growing MS SQL database that I would like to transfer over to PostgreSQL. It is currently 143mb (plus about 67mb in log files). The database is relatively basic, in that it does not currently use any stored procedures, and the tables makeup is pretty sql-gen