lock problem

[ersatz]

Hello,

I am in charge with the administration of a sql database (I am in charge since a few days and I’ll start a course in a couple of weeks).
Presently they make tests and we have a problem.
I do not know if it’s an application related problem or a sql setup problem.
There are several users who work at the same time, simultaneously. If one user makes changes in the data base (adding or retrieving data) and then leaves, when the other users wants to make changes as well they are not able to do so as the table is locked.
It’s like the first user ``commit`` command, is not done and something is waiting after this.
Do you have any idea where the problem is?
Thank you in advance for your kind help, I wait for your advice.
I forgot to tell you that we have a web application and we use a connection pooling with IIS.

 

[nigelrivett]

It's almost certainly an application problem.
And it sounds like you are in trouble

>> we have a web application and we use a connection pooling with IIS
From what you dexcribe it is holding connections so won't be pooling.

Another possibility is that someone has implemented logical record locking but made a mistake.

======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.

 

[ersatz]

Hi,

Just to say you that I solved the problem. They changed the MS sql driver with a BEA's WebLogic Driver and now all work very well.

Thanks anyway.
Joanne