Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2006-03-09 : 08:47:48
|
| Joao writes "Hi,I have 10 environments of up to 10 clients to one data server(MSDE 2000 SP4), accessing data through concurrent transactions over OLEDB.Each operation on each transaction is using lock, so they will access by order of processing.the problem is that in two of those environments, the data server had some situations of nolock.I thought, when it first occured, that it was a problem of low resources(PENTIUM 1.6Ghz 512MbRam), and that was the answer of SQL Server because of the dynamic lock. I've changed this configuration to specific limitation of locks, and other configurations, but it continnued until the substitution of that machine(PENTIUM 3.6Mhz 2GMbRam). Recently, I've installed a new environment, and the data server (P4 3.0Ghz 1GbRam)started doing the same thing. Those situations occur rarely.Can anyone help me?? Could it be some hardware conflict??? Antivirus??Windows XP???The main question is: "When or why does SQL Server ignore the need of locking transaction statements??"" |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2006-03-09 : 11:52:54
|
| I have no idea what you are talking about. You need to give us more information as to what problem you are trying to solve. what is a dynamic lock? What "specific limitation of locks, and other configurations" have you made?What problem are you trying to solve?-ec |
 |
|
|
|
|
|
Locking problem in MSDE 2000 SP4