Sorry, I've never heard of "servername@dbname" being a connection string for the native SQL Server connections. So I'm still blank on this.

==> this works anyway

Let me ask this, where are the SQL 2000 and SQL 7.x databases located? Same server but different instance? Different server?

==> L

ocatelocated different sqlserver machine

When you're trying to read this 2000 database, are you trying to connect to it via the SSMS GUI or an application? Or is this the same third party that is having trouble with your suspected 7.x database?

==> application (Informatica ETL tool). I cannot even conect tconnectSql7 via SSMS GUI, not even with 2005 GUI, so that's why I think it must be Sql7.0

And why can't you upgrade these older databases?

==> Not in my control and I know it won't happen....

FYI: I can't answer questions about nameless third party tools. You'll have to contact the vendor about that issue.

==> IMO, I'd say this is not a matter of third party software. Informatica will definately work, if the connectivity is there.

I'll put it this way. if I secretly install Sql2000 client to the new server, will it not destroy the curren 2012 client? and I could try the connection to this 7.0 database....

ville