I have 2 volumes, and I am only using 30% on each volume. I would suspect that a badly fragmented disk would cause overall system degradation. But my previous e-mail describes that only the dbms component of Sambar is experiencing poor performance. Without even doing the SQL through a dbms STM script, the ISQL utility in Sambar shows that throughput never exceeds 3.5k/sec.
I have MDAC 2.6 installed. Another PC with the same OS, Sambar version/build and MDAC is lighting fast. I think I'm looking at a re-install of the OS and Sambar :-(( Michael >>> [EMAIL PROTECTED] 07/18/02 10:14AM >>> Make sure you have adequate space available on all volumes. The NT-based OSes begin to degrade badly when you dip below 15-10% free space. Run a chkdsk /f on the volumes to make sure they are clean. Run a third-party defrag utility (e.g. Perfect Disk, Diskeeper) - fragmentation is a killer. Are you using the most current MDAC? (2.7 RTM 2.70.9001.0) http://www.microsoft.com/data/ -Jeff -----Original Message----- From: Michael Cook [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 17, 2002 12:48 PM To: [EMAIL PROTECTED] Subject: [sambar] Increasing dbms Performance {05} Thanks for that input. I'm beginning to feel that there is something terribly wrong with the W2K box that Sambar is sitting on. When I run STM scripts that return database queries, things have been slowing down about ten fold over the last few weeks. Here is my set up: Sambar 5.1 March 31 build (w/registered pro key) Windows 2000 Professional w/SP2 Dell Poweredge SCSI drives, 130 Megs RAM I have a 300 row DBF table that takes nearly 30 seconds to load into the browser, even if done on the server using localhost. Oddly, CGI database stuff works without any problems. I then installed the same version/build of Sambar on a lowly P90 with 80 megs RAM. The same DBF table loads within a few seconds. Here is an entry in the dbconfig.ini: [test] Description = Datasource = test Username = admin Password = Maximum Column Length = 8192 Maximum Used Connections = 5 Minimum Free Connections = 1 Maximum Idle Period = 10 Single Thread = true Trace SQL = false Trace Performance = true I've ruled out the Network and Sambar as the problem, and I am now focusing on a W2K problem. I'm still scratching my head as to why things are slowing down on the W2K box (and yes I've re-started and re-booted several times). I'm about to re-install everything on the Dell box, including a clean re-install of Windows. If anyone has any ideas for troubleshooting a W2K problem that may be causing this slowing database behavior through STM scripts, I would appreciate hearing form you. Thanks. ------------------------------------------------------- To unsubscribe please go to http://www.sambar.ch/list/ ------------------------------------------------------- To unsubscribe please go to http://www.sambar.ch/list/
