| Rick Sawtell 2006-02-06, 1:23 pm |
|
<vichai.levy@gmail.com> wrote in message
news:1139226979.456381.22750@z14g2000cwz.googlegroups.com...
> I'm writing a simple application that stores/pulls data into/from SQL
> 2005 Express Edition database.
>
> In one process data is inserted to the database, on another process
> same data gets pulled out. Both operations complete successfully and
> fast however the puller sees the inserted data way after data insertion
> has completed (1 - 3 minutes afterwards). I'm talking about no more
> then a 100 records inserted while a select with a group by pulling this
> data out and the table include less then 100K rows.
>
> How can I improve these actions so that data inserted to the database
> by the first process will immediately be seen by the puller process?
> I appreciate your help.
>
Take a look at how your transactions are running.
Another possible option (if you don't mind reading data that may be
changing) is to have the second process ignore locking. Take a look at the
(NOLOCK) query hint.
Rick Sawtell
MCT, MCSD, MCDBA
|