Sql updating multiple tables simultaneously Free mins cam chat no creditcards

12 Sep

The first table stores the benefit detais as pdf file.(in the PDF_IMAGE column) more than one state is associate with the benefitdetails.(thts why we have plan_pdf table) like 2 states can have the same benefit details. I need to provide a way to the client that he can able to populate these 2 tables through stored procedures.

i am wondering that should I write a single sp to do this or I need 2 sp's to acomplish this task.

Suppose we have two tables Categories and Categories_Test. The common column in the two tables is CATEGORY_ID. Please note that query below is used for illustration purpose because Category_ID alone is primary key.

We are going to update column DESCRIPTION and PICTURE in table Categories_Test by using data in table Categories, based on data in the common column CATEGORY_ID. Update data in a column in table A based on a common column in table B. Update data in two columns in table A based on a common column in table B. Conditionally update data in table A based on a common column in table B. No portion may be reproduced without my written permission.

So, in real life there are people who spend much of their time trying to find which resources are causing these bottlenecks for an application and getting rid of those bottlenecks.

At the very least though, there are usually Your question implies that before the improvements, SQL access was sequential, i.e.

The Oracle UPDATE statement is used to update existing records in a table in an Oracle database.

Among other optimizations, we split some of these calls off into a separate thread.

From this change alone, we are seeing a large improvement in processing time (the code is almost exactly the same, just some has been moved into a different thread) Question: Assuming that the time spent running the code in memory is negligible, I would have guessed that performing some of the reads/writes in another thread would yield no performance gain.

As I said Stored proc may not be the best way, it depends on a lot of things?

Depending on your front end it may not even be possible to use a stored proc for this. Hi Delerna, I just confirmed with my team lead that we should make use of the stored procedure, Because the font end we are using is JAVA right now.