June 4, 2002 at 2:01 pm
Our network clients will all be upgrading to Windows XP in the near future (most currently are either NT or 95). One of the vendors for an application that I support states that they do not support XP due to a "documented compatibility issue with SQL 7.0" and they are waiting for MS to fix the problem.
A cursory search of Microsoft's sites didn't reveal any issues. My first question is, has anyone else heard of this? If I'm only running the API from the XP client and not SQL Server, can I still expect trouble? FYI - My DBMS server is NT 4.0 SP6a with SQL Server 7.0 SP3. Any information is appreciated.
June 4, 2002 at 2:21 pm
I'd be surprised. More likely that it would be an issue trying to run SQL on a XP box than connect to one.
Andy
June 4, 2002 at 4:52 pm
This is usually when I suggest stomp your vendor with the give me the details of what you are talking about. The current MDAC with XP supports fully connecting to a SQL 7 server and I have no issues. Sounds to me like they are pulling the old it's not our fault routine. They should be able to provide you exact documentation just demand it.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
June 5, 2002 at 1:50 pm
Thank you both very much. I logged an issue with their support site and am waiting for an answer (in writing). My thinking is that since most all my users are accessing the app via an ASP (TSE/Metaframe 1.8) that this is essentially a moot point but it always pays to check.
June 6, 2002 at 7:45 am
If the users are coming through TSE, it's the TSE server where the application runs and so the client is irrelevant.
One issue with SQL Server and Windows XP involves the MDAC version that ships with XP. MDAC 2.7 is not supported on SQL Server 7.0 or SQL Server 6.5 Clustered Servers. This is due to issues with clustering (as specific as Microsoft gets). Here is the quote from the Release Manifest:
quote:
Versioning problems with clustered servers. If a clustered server is running Microsoft SQL Server™ version 6.5 or 7.0, installing MDAC version 2.6 through 2.7 on that server causes connectivity problems within the cluster. There is currently no work around. Do not install MDAC 2.6 or 2.7 on a clustered server if it is running SQL Server 6.5 or 7.0. There is no problem with SQL Server 2000 clusters using MDAC 2.6 or 2.7. There is no problem using MDAC 2.7 on a client connecting to a SQL Server 6.5 or 7.0 clustered server.
I should clarify, this MDAC is a problem if installed on the server itself. However, I know I've had a couple of developers ask me if there are any issues with installing MDAC 2.7 on their client systems. That really is a moot point, because if a SQL Server is clustered where I work, it's a SQL Server 2000 box. So there is some confusion on the subject.
Here is the release manifest link: http://www.microsoft.com/data/MDAC27Info/en/readmerefresh.htm
There is also a connectivity issue with XP, and it's documented on the page as well. This may be what the vendor is referring to.
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
Edited by - bkelley on 06/06/2002 07:50:04 AM
K. Brian Kelley
@kbriankelley
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply