Migration from 6.5 to 2000

Question

Migration from 6.5 to 2000

sqlquery-101401

SSCarpal Tunnel

Points: 4951
More actions
January 3, 2006 at 11:02 pm

#364621

Hi All,
We are doing a migration from SQL 6.5 to SQL 2000.
We are facing a small problem:

We have installed SQL 6.5 server Enterprise edition on Windows 2000 Advanced server. On this system, in the regional settings, the Locale is Japanese and in Office 2003 Language settings also, we have added Japanese.

We have another system with Windows 2000 server on which we have installed SQL 2000 server Enterprise edition with SP4. On this system, in the regional settings, the Locale is Japanese and in Office 2003 Language settings also, we have added Japanese.

From the front end VB code, a query is formed which contains Japanese value. This works in the SQL 6.5 environment but does not work in the SQL 2000 environment. If we directly execute the query in SQL 2000 server, it is returning the row. But the VB front end is not recognizing the row.

The query is like this:
SELECT * FROM Tstar_Currency WHERE Currency = N'ÆÎÝ'

This query works when the VB client connects to the SQL 6.5 server and the front end fetches one row. But when the VB client connects to SQL 2000 server, the front end is not fetching any row. However, if we directly execute this in query analyzer in SQL 2000 server, it returns one row.

Please suggest.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

David.Poole SSC Guru Points: 76195 More actions · Answer 1

In your VB app what is brought back if you list the results of SELECT * FROM Tstar_Currency?

Also, I have come across a situation where a user database and system database have had different collations so when I have performed a join I have had to use a statement similar to that below

FROM #idx AS i LEFT JOIN dbo.sysobjects AS IX

ON i.index_name = IX.name COLLATE Database_default

Note the COLLATE statement. You may have to do something similar in your WHERE clause

LinkedIn Profile

Steve Jones - SSC Editor SSC Guru Points: 738643 More actions · Answer 2

Also, are you running your server in 6.5 mode or 2000 mode?

Yelena Varshal SSC-Dedicated Points: 34287 More actions · Answer 3

When you say VB Client Connects... what do you mean?

Is it OLEDB or ODBC connection? It may depend on the driver:

OLEDB: sqloledb.dll, ODBC: sqlsrv32.dll

also, did you install sql server 2000 connectivity SW on the machine with the VB client? 6.5 connectivity SW was different. By default Windows 2000 and XP computers do have a correct MDAC installed, but if you still running your client from the machine that had 6.5 connectivity SW there could be problems.

I would advise to use Profiler to track what statement is submitted to SQL Server 2000 when it does (from QA) and does not (from the app) return rows.

Regards,Yelena Varsha