It should not cause a problem as long as you are not trying to relate the
different data pulls. If you are doing this
Spawn thread
Call for user information
Spawn another thread
Call for user orders
Spawn another thread
Call for user order details
When all are returned, relate them
That could be problematic as there is no locking mechanism across all calls,
which means data could be updated rendering user or orderinformation invalid
when you call for details.
If you are pulling data asynch that is not related, you should not have any
problems. Looking at your post, it appears you are simply calling the same
stored procedure on multiple threads (for multiple users?).
Short answer: As long as the threads are not talking to each other (or
aggregating for the main app thread to relate data), you should not have any
problems.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***************************
Think Outside the Box!
***************************
"tr**************@yahoo.com" wrote:
Hi all,
i am having application which is using stored procedure written in sql
server.
I want to develop multithreaded applicaton.
The store procedure is returing list of rows of table.
what i want to ask is, if i tried to call same stored procedure in
different thread , is it possible or it will created problem in
multithreaded application.
If yes how to get rows returing from stored procedure.
Any help will be appreciated.
thanks in advance.