On 24.03.2006, at 23:03, Döhr, Markus ICC-H wrote:
One current issue is this. Using Access as the front end and
ODBC it takes a long time to open an attached MaxDB table and
a table with only 5 records in it takes minutes to delete one
record. Is this an ODBC problem a MaxDB problem. What can I
do to fix this. I want to continue to use the application I
have with an Access 2003 front end. It can be on either
client machines or the 2003 server. In either case it must
link to the MaxDB tables and work with acceptable speed.
[...]
Is you name resolution work in both directions? Means, can the server
reverse lookup the name of the IP address that is connecting?
If your IP address resolution doesn't work, go and fix it. You'll get
other problems as well.
As a short term work around, you can disable the name lookup in the X
Server
by starting it with option '-F'
http://dev.mysql.com/doc/maxdb/en/7a/6e424089ff2571e10000000a155106/
content.htm
-F
If you set this option, the X Server does not determine the computer
name of the application logging on to the DNS server (no reverse DNS
lookup).
If it is taking a long time to connect to a remote database instance,
you should restart the X Server with this option. This will tell you
whether the DNS server is responsible for the slow connection.
Henrik
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
