Hi Robert See answers below.
> -----Original Message----- > From: Robert Klemme [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 02, 2005 4:39 PM > To: Heckendorff. Ronald > Cc: [EMAIL PROTECTED]; [email protected] > Subject: Re: poor insert performance > > Some remarks + questions... > > 2005/11/2, Heckendorff. Ronald <[EMAIL PROTECTED]>: > > Hi Martin, > > I now need 2 minutes to restore my test scenario. I just checked Oracle > and Ms-Sql Server. It is the same computer. Oracle is running on Linux and > MaxDB and Sql Server are running on w2k pro. > > > > For restoring the same backup date from an identical client to nearly > identical network server I got: > > MaxDB: 2 minutes > > Oracle: 30 seconds > > Sql-Server: 40 seconds > > How did Oracle manage to beat SQL Server? Just curious because for us > Oracle is always slower. Or do you have significant differing > hardware? Also, do you use jTDS or Microsoft's JDBC driver? It was the first time that I saw that Oracle is faster then sql server. Maybe a new test will show a slightly different result. I didn't check this in depth. I gathered the results only for getting a first impression. The hardware is the same. But as I wrote before: Oracle runs on Linux, Sql-Server and MaxDB on w2k pro. The restore itself did run always on my client computer winxp pro. It is also the first time that I made a comparison between with Ora10gR2 and other dbms. We use the jTDS driver for ms-sql server. > > > In comparison to oracle this is a ratio of 1:4 (30 seconds : 2 minutes). > This is acceptable for us. > > > > I now still use the jdbc solution with prepared insert statements. Maybe > we'll try the batch update but not sure if this will speed up the restore > too much. > > You can use batch updates with PreparedStatement: > http://java.sun.com/j2se/1.4.2/docs/api/java/sql/PreparedStatement.html# ad > dBatch() > Well I know how to use batch updates. During the last weeks I tried to solve my problem with this too. But it didn't show significant differences in comparison to inserts with a prepared statement. But maybe this was cause by the stupid trigger that we used before. Alexander also told me that it is faster, but anyway, at the moment that has no priority for me. Other tasks are more important then this. I increased the performance for maxdb from 2 hours to 4 minutes, wow ;-) > > The loader is no option for us. We need to have the file that holds the > backup on the client and not on the server. The loader needs the data > always on the server. So this is not practicable for us. > > That's not exactly true: you need the date where the loader is > installed. Should be no problem to install the loader on your client > machine. That's why SQL Server and Oracle have a client utils > installer. > Aha never tried this. The reason is below. > > We also don't want to implement a solution only for one dbms. We have to > support more then maxdb. > > Of course it's easier with JDBC then. > > Kind regards > > Robert Kind regards, Ronald -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
