question: potential db lock up with Sybase SQL 'select' statement that takes long time to execute ....
here it is although almost irrelevant to my question:
"select a, b, c, d, SUM(e) as f from A where a = '080429' and appl b = 'something' and d = 111111
group by a, b ,c, d
So the question is with Sybase (and I don't have the version but am using 3.11 drivers), as with the usual readers/writers problem with lock outs in multi threading programming will Sybase then lock out all other users for the entire duration of my SQL statement that wish to perform a SQL write on table 'A' of my SQL above for the entire duration of my 'select' command above which is being executed ?
Or is Sybase a bit smarter than that ..?
remember my SQL above will be ran on the client side i.e. not a stored procedure whereas other user's SQL WILL be typically ran on stored procs.
(tbh: I think I know the answer already as I've seen the result on old SQL server once before).
here it is although almost irrelevant to my question:
"select a, b, c, d, SUM(e) as f from A where a = '080429' and appl b = 'something' and d = 111111
group by a, b ,c, d
So the question is with Sybase (and I don't have the version but am using 3.11 drivers), as with the usual readers/writers problem with lock outs in multi threading programming will Sybase then lock out all other users for the entire duration of my SQL statement that wish to perform a SQL write on table 'A' of my SQL above for the entire duration of my 'select' command above which is being executed ?
Or is Sybase a bit smarter than that ..?
remember my SQL above will be ran on the client side i.e. not a stored procedure whereas other user's SQL WILL be typically ran on stored procs.
(tbh: I think I know the answer already as I've seen the result on old SQL server once before).
Comment