vsql 5.0 client

[JimKnicely]

Hi,

Hmm. I tried this too. I copied the windows vsql executable to a new directory and then uninstalled the Vertica 6 drivers (if you don't copy the executable it gets deleted during the uninstall). I then installed the 4.19 drivers but still could not connect to a Vertica 5 database using the Vertica 6 vsql Windows client I copied previously

Code: Select all

C:\Vertica\bin>vsql -h verticatest01 -U dbadmin
vsql: FATAL :  unsupported frontend protocol 3.3: server supports 3.0 to 3.1

I'm guess the issue is on the server side... Maybe Vertica will release a vsql Windows version compatible with Vertica 5?

Note that I could still connect to a Vertica 6.0.0-2 database:

Code: Select all

C:\Vertica\bin>vsql -h verticatest01 -U dbadmin
Welcome to vsql, the Vertica Analytic Database interactive terminal.

Type:  \h for help with SQL commands
       \? for help with vsql commands
       \g or terminate with semicolon to execute query
       \q to quit

Warning: Console code page (437) differs from Windows code page (1252)
         8-bit characters may not work correctly. See vsql reference
         page "Notes for Windows users" for details.

dbadmin=> select version();
              version
------------------------------------
 Vertica Analytic Database v6.0.0-3
(1 row)

[jpcavanaugh]

Windows vsql was not supported with server version 5 unfortunately and most likely will not be back ported.

[Julie]

Windows vsql was not supported with server version 5 unfortunately and most likely will not be back ported.

Boo! Just kidding

I've already upgraded to 6.0.0-3.

vzingertal, maybe you can upgrade your database? It is pretty painless to do so.

[id10t]

Hi Julie!

To upgrade it's painless - it's true, but Vertica 5 much more stable than version 6. I still do not recommend to use Vertica 6, especially 6.0.0.0, -1, -2.
On production system I still will use in version 5.

[Julie]

Uh oh. We already upgraded in production

So far so good as I haven't had any issues (knock on wood).

Have you heard about any major bugs in 6.0.0-3?