Steve, I still don't have a clear answer for my similar situation. We have a 6.5++ Windows app running on a 10/100 network. The database resides on the domain controller, a Windows 2000 Server with Active Directory.
I have come to believe that the major issue we face is having the database sitting on this box. A domain controller in a WAN installation has a lot of communicating to do with the other servers and other locations. The server is not stressed, but it seems that the file i/o services get reduced in priority to other tasks on the box. We see not only delays in connects, we see failed connects, and we see a lot of "Waiting for access to required resource" messages as well as "Updating database information - this operation cannot be interrupted." Granted I am not a W2k Server expert; far from it. But my common sense tells me that something is locking up file 1. Early on we were seeing situations where a desktop PC would insert a row, but a thin client on Metaframe would not be able to see that row for up to 10 minutes. Either the DC was not flushing its write cache to disk, or it was not refreshing the read cache, or both, or the Metaframe server was not refreshing its cache, or something. I have no other explanation for how it could take ten minutes to see a new row from a different machine. Recently at this location we replaced a patch cable between the DC and the switch, and matters have improved. The cable tests to within spec, but its removal eliminated all sorts of collisions. But we still see the messages that appear to be file 1 contention, just not as many. We are working on our next major installation, and here I have included a souped-up database server for nothing more than holding the database files. Database I/O will not have to compete with anything other than network I/O. This installation goes live 1/19/02; I'll report our findings in early February. >I know I have seen this talked about before, but I need to ask it again. I >have a client who is running RBDOS and upgraded from Novell to Windows 2000 >Server. Whenever a second user connects, the CONNECT command bogs down. It >takes about 10 seconds to connect to a 600MB data base. This would not be a >big problem except the application has to connect to a second data base when >one of the menu selections is made. I was able to solve most of their >problems but minimizing the number of time the data base is connected to, >but I was hoping someone would have a solution that would eliminate the >connect delay. > >Thanks > >Steve Hartmann Emmitt Dove Manager, DairyPak Business Systems Blue Ridge Paper Products, Inc. 40 Lindeman Drive Trumbull, CT 06611 (203) 673-2231 [EMAIL PROTECTED] [EMAIL PROTECTED] ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l
