stcode wrote: > I tried to test sapdb performance with 50grand records > the table is like this : > > CREATE TABLE MYRANDOM > ( > ID FIXED(18), > CONSTRAINT AMYRANDOMPK PRIMARY KEY(ID), > AName varchar(50), > AValue FIXED(18), > Address varchar(100), > City varchar(50), > Country varchar(40) > ) > > Data File : 50 mb > Log : 10 mb > > I tested it with Delphi - BDE - ODBC > To entry database i used this code : > For i:=0 to 50000 do begin > //entry code > end; > > After several minutes, It hung, didn't response anything... > but I still could look at the database with dbmcli_helpinst.exe > It stops at records #30800. > > I forced to close my app with task manager and tried to > access database > with SAPDB SQL studio. > but sql studio couldn't log in (not responding too). > This confusing made me to restart it, hoping it works after > restart. But It > was same result, > Either SQLexplorer or SQL studio didn't work... seems the database is > corupt or failed > > I don't know what's wrong with it, but i still can access > database with > Database Manager... > > I think it's about DB parameter/configuration (Tuning)... but > I'm not sure.. > Anyone know how to solve this problem? > Thanks for help
Usually this behaviour can be seen if the log is full. Did you check this? Increase log-space or (better!) do some commit from time to time, not handling 50 000 Record within one transaction. AUTOSAVE log will not help if you have ONE open transaction fillig your log space. Elke SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
