From: nospam@nospam   
      
   Trevor wrote:   
      
   > Any other ideas?   
      
      
   1.  Have a DBA monitor your connection while the 15-20 minute operation is   
   occurring to diagnose what the server utilization (cpu, disk, I/O) is.   
   Could be a configuration issue, such as lack of space in tempdb.   
   2.  Have a network engineer analyze the traffic.  Ideally compared to when   
   the old server was in use.   
   3.  Open and scrutinize an ODBC trace on the connection.  Again, ideally   
   compared to when the old server was in use.   
      
   Is the old server still available to test with?   
   Are the non-Paradox related activities not impacted at all?  Can you perform   
   similar actions on the database in, say, Access?  Are direct query   
   operations (e.g., Query Analyzer) impacted at all?   
      
   --   
   Larry DiGiovanni   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)