Re: Locking in SQL Server and Oracle
From: wei xiao[MS] (weix_at_online.microsoft.com)
Date: 02/17/05
- Next message: DBADave: "Re: Can't delete filegroup, even though it is empty"
- Previous message: DBADave: "Re: Can't delete filegroup, even though it is empty"
- In reply to: Jeffrey Roughgarden: "Locking in SQL Server and Oracle"
- Next in thread: Galen Boyer: "Re: Locking in SQL Server and Oracle"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 16 Feb 2005 18:13:31 -0800
I am glad you would like to stay with SQL Server :-)
In SQL Server 2005 beta 2, there is a new feature called "snapshot
isolation". This new feature reduces blocking and deadlocks a lot. Only
updates require a lock. Please see books online and this article for more
details.
http://www.microsoft.com/technet/prodtechnol/sql/2005/SQL05B.mspx
As for lock escalation, here is a way to disable that:
http://support.microsoft.com/default.aspx?scid=kb;en-us;323630&sd=tech
So if you want to, you can have effectively a row-locking only database with
SQL Server 2005 beta 2. There are still some advantages with lock escalation
in some cases. So we would like the user to have a choice.
-- Wei Xiao [MSFT] SQL Server Storage Engine Development http://weblogs.asp.net/weix This posting is provided "AS IS" with no warranties, and confers no rights. "Jeffrey Roughgarden" <JeffreyRoughgarden@discussions.microsoft.com> wrote in message news:56C0B915-E545-4689-9B95-FE8CE268DC10@microsoft.com... > I am an MCDBA and MCSD in charge of several large PeopleSoft databases. I > recently attended a 5-day Oracle 9i DBA Fundamentals 1 class to ascertain how > hard it would be to convert to Oracle during our next PeopleSoft upgrade. I > had thought that since databases are databases, tables are tables, and SQL is > an ANSI standard, it really would not be that different doing Oracle. Well, I > was wrong. Oracle is so dramatically different from SQL Server (and awkward > and complex) that we decided to carry on with SQL Server. > > That said, I was impressed by one feature of Oracle, namely the fact that it > uses row-level locks exclusively. Clearly, this reduces the liklihood of > blocking and deadlocking significantly. I had thought that Microsoft does > escalated locks because it was infeasible to do row locks, but apparently > not. Oracle runs as well as SQL Server in spite of the overhead it incurrs > managing more locks. > > I am curious why Microsoft does not adopt row-locking exclusively now that > Oracle has shown it can be done.
- Next message: DBADave: "Re: Can't delete filegroup, even though it is empty"
- Previous message: DBADave: "Re: Can't delete filegroup, even though it is empty"
- In reply to: Jeffrey Roughgarden: "Locking in SQL Server and Oracle"
- Next in thread: Galen Boyer: "Re: Locking in SQL Server and Oracle"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|