http://www.sqlmag.com/authors/author/author/5777798/rsscomment/5777798en-USFri, 25 May 2012 09:17:04 GMTFri, 25 May 2012 09:17:04 GMThttp://www.sqlmag.com/article/performance/64-bit-vs-32-bit-memory-management#commentsAnchorFri, 18 Jul 2008 23:04:59 GMT
Good overview and gave me the links I needed for more info.]]>DonFri, 18 Jul 2008 23:04:59 GMThttp://www.sqlmag.com/article/performance/64-bit-vs-32-bit-memory-management#commentsAnchorhttp://www.sqlmag.com/article/internals-and-architecture/minding-memory#commentsAnchorThu, 27 Mar 2008 21:28:47 GMT
32 bits : 64 bytes + 32 bytes = 96 bytes total per lock block 64 bits : 128 bytes + 64 bytes = 192 bytes total per lock block owner Kalen’s storage engine book documented this. Locks. SQL Server uses two structures to implement locking: lock blocks and lock-owner blocks. A lock block (which requires 64 bytes on 32-bit systems and 96 bytes on 64-bit systems) represents a particular resource such as a row or a page that SQL Server has locked. A lock-owner block (which requires 32 bytes on 32-bit systems and 56 bytes on 64-bit systems) represents a particular lock holder.]]>CHANGThu, 27 Mar 2008 21:28:47 GMThttp://www.sqlmag.com/article/internals-and-architecture/minding-memory#commentsAnchorhttp://www.sqlmag.com/article/performance/memory-matters#commentsAnchorTue, 15 Nov 2005 14:58:07 GMT
Great article, all mysteory about memory explained in one article. Raj Pochiraju, Microsoft]]>VenkataTue, 15 Nov 2005 14:58:07 GMThttp://www.sqlmag.com/article/performance/memory-matters#commentsAnchorhttp://www.sqlmag.com/article/performance/memory-matters#commentsAnchorTue, 08 Feb 2005 12:35:30 GMT
This has been very helpful but I have questions about the /3GB switch mentioned in the sidebar on 32/64 bit memory management. There is a lot of contradictory information going around about this switch and MSDN information seems to me a bit ambiguous. Let’s take SQL Server Enterprise addition on a dedicated Advanced Server with 4GB of physical memory. It is not clear to me exactly what the implications are for SQL Server’s dynamic memory management. Does the /3GB switch require AWE to be enabled even though we are not going to use memory beyond 4GB? Does the AWE enabled configuration switch need to be set in SQL Server? Is the /3GB switch by itself the optimum memory configuration for this scenario? Is there a downside? Regards, Kurt Survance SQL Consulting, Inc.]]>KURTTue, 08 Feb 2005 12:35:30 GMThttp://www.sqlmag.com/article/performance/memory-matters#commentsAnchor