Why an cursor opened for a select with ORDER by does not reflect updates to the subsequent table

Question

I have set this little example of a strange behavior

    SET NOCOUNT ON;
    create table #tmp
    (id int identity (1,1),
    value int);

    insert into          


        

Answer 1

You can use the sp_describe_cursor stored procedure to view the metadata of the cursor. Doing so on your example shows the following:

ORDER BY included:

model = Insensitive (or static), concurrency = Read-Only

ORDER BY excluded:

model = Dynamic, concurrency = Optimistic

Source: http://technet.microsoft.com/en-us/library/ms173806(v=sql.105).aspx