Is Multi Threading required for this scenario

Please see my comment to the question. The problem is not formulated to the detail allowing to decide finally.

Multithreading may have many different justification. In particular, you should call all methods which blocks or simply considerably delay the execution, in a separate (non-UI) thread.

More essentially, it can be required by logic. If you have some sequential processing, more or less independent in its logic, it should be a separate thread. The problem should be considered in a holistic way. Some algorithm working the best in a console-only application, will require a separate thread in a windowed UI, and so on.

[EDIT]

Please see some of my past answers on related topics:

One of the best ways to create a thread:
How to pass ref parameter to the thread[^],
Change parameters of thread (producer) after it is started[^],
MultiThreading in C#[^];

throttling threads properly (Resume/Pause is deprecated as unsafe):
ManualResetEvent and AutoResetEvent in Thread[^],
pause running thread[^];

invocation to UI thread:
Control.Invoke() vs. Control.BeginInvoke()[^],
Problem with Treeview Scanner And MD5[^].

The topics I listed are practically the most important, when the UI is involved.

—SA

While CPallini is generally right, I always try to keep anything that is potentially reusable, or could possibly someday exhibit unexpected or unwanted behavior out of the UI. If there's a possibility that you can build your database calls into a class you can reuse, then do that. Also, I think making database calls off the UI thread is not a bad idea. There could always be network slowness/trouble someday, or database server slowness or problems - and if your making those calls in the UI thread then your UI will freeze.

I would set up a delegate and do that stuff off thread, and then pass your callback the results to update your UI.

Hey,

Here if there are two buttons then I think only 1 button event will be firing at a single call.

You cant hit both buttons at a single moment so there will be only 1 event triggering (either GET or Update) in a single postback.

May be here multithreading is not reqd.

Hope it helps...


Cheers!!
Sam