|
|
Posted by Erland Sommarskog on 02/23/07 11:49
(jsmall@visinet.com.au) writes:
> We currently have a fairly old product, which was originally only
> compatible with SQL 2000.
>
> When we upgraded our server to SQL 2005, the client product gave us a
> "This product is not compatible with this version of SQL server"
> error.
> We put the server into SQL 2000 compatability mode, and things worked.
>
> Then I tested a Windows Vista workstation client. The error returned.
>
> I realise that if we are simply dealing with a client incompatability
> with Vista, then I'm in the wrong forum, but what I'm hoping is that
> someone knows anything server side, perhaps where SQL 2000
> compatability mode becomes ignored for some reason, when the client is
> running Vista.
There are several ways that the product could perform this test. None of
which where the client operating system would matter. But if the check
is against @@version of the like, you will always get the message. If
the check is against the compatibility level of the database, it helps
setting it compatibility mode.
You can use Profiler to determine what the application sends to SQL Server.
Maybe the vendor was sloppy, and the message for incompatieble OS is the
same as the message from SQL Server.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|