SLOW update statments
Posted in 1998
Topics: Connectivity: ODBC / JDBC / .NET, Platform-Specific Issues
This is a multi-part message in MIME format. ------=_NextPart_000_00C2_01BDC70B.3A371CE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable We have got a problem with some VERY slow update statements in an = INFORMIX database. Configuration: WEB server accessing Informix DB through CGI using Visigenics ODBC = drivers. Everything running on Sun Solaris stations. The table that we = want to do the updates on has about 40000 rows. =20 I am aware that this is not the optimal solution but that product needs = to the very platform independent. The weird thing is that all other queries are fast. INSERT statements in = this table takes less than 1 second, where an UPDATE on the same row can = takes up to 13 seconds. None of the keys in the table are integer values; all strings, which = might contribute to this problem. Does anyone have an ideas as to what is going on here. Thanks /Erik ------=_NextPart_000_00C2_01BDC70B.3A371CE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"> <HTML> <HEAD> <META content=3Dtext/html;charset=3Diso-8859-1 = http-equiv=3DContent-Type> <META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT color=3D#000000 face=3DArial size=3D2>We have got a problem = with some VERY=20 slow update statements in an INFORMIX database.</FONT></DIV> <DIV><FONT color=3D#000000 face=3DArial size=3D2></FONT> </DIV> <DIV><FONT color=3D#000000 face=3DArial = size=3D2>Configuration:</FONT></DIV> <DIV><FONT color=3D#000000 face=3DArial size=3D2>WEB server accessing = Informix DB=20 through CGI using Visigenics ODBC drivers. Everything running on Sun = Solaris=20 stations. The table that we want to do the updates on has about 40000=20 rows. </FONT></DIV> <DIV><FONT color=3D#000000 face=3DArial size=3D2></FONT><FONT = face=3DArial size=3D2>I am=20 aware that this is not the optimal solution but that product needs to = the very=20 platform independent.</FONT></DIV> <DIV><FONT color=3D#000000 face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>The weird thing is that all other = queries are fast.=20 INSERT statements in this table takes less than 1 second, where an = UPDATE on the=20 same row can takes up to 13 seconds.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>None of the keys in the table are = integer values;=20 all strings, which might contribute to this problem.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Does anyone have an ideas as to what is = going on=20 here.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV> <DIV><FONT face=3DArial size=3D2>/Erik</FONT></DIV></BODY></HTML> ------=_NextPart_000_00C2_01BDC70B.3A371CE0--