Hi Legolas, Hope you find some of the answers below:
1) We need highest performance, Should we use stored procedure? Writing and running stored procedures in Java allows you obviously to run Java logic within the same JVM as the Derby DB core engine - If your application runs Derby embedded, you may not gain from a noticeable improvement as everything runs embedded - However, you will bypass some of the JDBC layer(s) as the stored procedure will run inside the database spectrum in theory, with direct access to data, not requiring the use of JDBC for that - If you feel that you can run some of your logic inside the database, then it certainly a good thing to do it but as usual, there are tradeoffs as far as portability ( i.e. stored procedure in Java), if you ever intend to port your stored procedure logic to other RDBMS that does not support this. 2) We will encrypt the database using derby Encryption mechanism, will it cause performance problem? Well, as usual, encryption is not free (it has some cost), you can expect some 10-15% performance overhead with an encrypted database - Of course, this can vary based on the encryption cipher (algorithm) you decide to go with. 3) Is it correct that we can include a jar file or some Java classes into the database? if it is correct, what is its use? Yes, check http://db.apache.org/derby/docs/dev/devguide/devguide-single.html#cdevdeploy30736 Use described in the doc as well. Hope this helps, On 1/20/07, legolas wood <[EMAIL PROTECTED]> wrote:
Hi Thank you for reading my post. We have planned to use Derby embedded for our application internal data storage. Here I have some questions which any answers could be helpful about them. - We need highest performance, Should we use stored procedure? - We will encrypt the database using derby Encryption mechanism, will it cause performance problem? - Is it correct that we can include a jar file or some Java classes into the database? if it is correct, what is its use? Thank you very much.
