|Subject:||Re: Performance problem opening database on SQL-server
|Date:||Tue, 24 Mar 2020 10:43:22 +0100
|From:||Anders Jonsson <andersREMOVETHIS@jonssondata.se>
Den 2020-03-24 kl. 04:19, skrev Tom Krieg:
> Anders, do the two computers use the same ODBC driver and version?
> Also, do the two PCs have the same version of Windows 10?
I did the initial install of the computers here in my office. Identical
hardware and Windows verions. Same BDE and Paradox version. Run alla
> Silly idea, but
> is one PC looking for the database in the Azure cloud first? Or
> somewhere else?
That was also I thought I had, maybe that some kind of DNS problem that
made it search for the SQL server in the wrong place but this wouldn't
explain why it has problem with only one of the databases.
Azure is not involved.
> Maybe one version of the ODBC driver has issues with 2 databases with
> different collations?
That is my main theory. If the the ODBC driver for some strange reason
are different on the two computers - that could explain the problem. I
have no idea how they can be different, but thas is my next thing to check.
The problem is that testing is soooo timeconsuming and you can imageinen
that a retail company that struggled already before Corona, don't want
to spend money on something they think should just work.