Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

2008 and 2012 client connectivity on a same machine Expand / Collapse
Author
Message
Posted Tuesday, September 11, 2012 12:56 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, May 6, 2014 2:17 AM
Points: 101, Visits: 197
Hello,

I'm setting up new ETL servers and I might need to install both 2012 and 2008 clients. Because I can't read 2000 server OK with 2012 atleast so it seems to me. I might even have to read 7.x Sql...

If I install both clients, how do I tell which client connectivity the different db-connections should use or will it be automatic?

Ville
Post #1357161
Posted Tuesday, September 11, 2012 4:23 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 12:40 PM
Points: 7,210, Visits: 6,352
Ville Lucander (9/11/2012)
Hello,

I'm setting up new ETL servers and I might need to install both 2012 and 2008 clients. Because I can't read 2000 server OK with 2012 atleast so it seems to me. I might even have to read 7.x Sql...

If I install both clients, how do I tell which client connectivity the different db-connections should use or will it be automatic?


I am not quite sure what question you are really asking. How does client connectivity happen with your current SQL Server installation?


Brandie Tarvin, MCITP Database Administrator

Webpage: http://www.BrandieTarvin.net
LiveJournal Blog: http://brandietarvin.livejournal.com/
On LinkedIn!, Google+, and Twitter.

Freelance Writer: Shadowrun
Latchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.
Post #1357280
Posted Tuesday, September 11, 2012 4:31 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, May 6, 2014 2:17 AM
Points: 101, Visits: 197
Hi,

via native sql server connectivity: servername@dbname and now, in new server, there is Sql 2012 client installed by a third party and it does not read one of the source databases which is probably Sql 7.x...

I was wondering that if Sql 2000 client connectivity is now installed as well, will the connection to the 7.x start working just like that or do you have to configure it to use the older connectivity somehow?

ville
Post #1357288
Posted Tuesday, September 11, 2012 4:49 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 12:40 PM
Points: 7,210, Visits: 6,352
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.

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

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?

And why can't you upgrade these older databases?

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


Brandie Tarvin, MCITP Database Administrator

Webpage: http://www.BrandieTarvin.net
LiveJournal Blog: http://brandietarvin.livejournal.com/
On LinkedIn!, Google+, and Twitter.

Freelance Writer: Shadowrun
Latchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.
Post #1357304
Posted Tuesday, September 11, 2012 4:59 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, May 6, 2014 2:17 AM
Points: 101, Visits: 197
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
Post #1357313
Posted Tuesday, September 11, 2012 5:09 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 12:40 PM
Points: 7,210, Visits: 6,352
Ville Lucander (9/11/2012)
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


Not saying it doesn't. Just saying I have absolutely no idea what this is.


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.


Again, not saying the third party tool is the problem. I'm just saying I can't answer that question because I don't know what third party tool you're using and I'm not the vendor. (I don't know anything about Informatica either).


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....


Each installation of SQL Server has its own set of tools, dlls, and drivers (which is what I think you're actually talking about) that come with it. If you install SQL 2000 *over* the folder in which SQL 2012 is located, then yes, you'll ruin the install of 2012. Of course, I'm not even sure if it will let you install it that way.

You can, however, install SQL 2000 in its own folder (I did this after installing SQL 2005) so that you have all the SQL 2000 tools in one spot that do not conflict with the tools of the other SQL installations. So, if you need the SQL 2000 client and connectivity tools, that's the route I recommend you go. Install in a different folder after installing the newer versions (to make sure the newer versions don't overwrite the old tools).


Brandie Tarvin, MCITP Database Administrator

Webpage: http://www.BrandieTarvin.net
LiveJournal Blog: http://brandietarvin.livejournal.com/
On LinkedIn!, Google+, and Twitter.

Freelance Writer: Shadowrun
Latchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.
Post #1357318
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse