THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |

Search

You searched for the word(s):
Showing page 1 of 52 (519 total posts) < 1 second(s)
  • re: Clustering every SQL Server instance

    Greg; I might have misunderstood you, but you seem to see a dichotomy between &quot;convenience of support staff&quot; vs. &quot;user experience&quot;. I happen to think making the life of the support staff easier enhances the user experience. In addition, if we don't consider the impact on user experience, the convenience of the support staff ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on February 22, 2012
  • Clustering every SQL Server instance

    You may disagree, but I believe it is a good practice to cluster all the SQL Server instances. That is, even when you plan to run a SQL Server instance on a single machine, you should install it in a single node cluster. The primary advantage is that you only need a single standard SQL Server build instead of one for the stand alone and one for ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on February 10, 2012
  • re: Performance impact: the cost of NUMA remote memory access

    As mentioned, I was interested in the worst case scenario. For that, I didn't want any other resource bottleneck that may obscure the impact of remote memory access. For instance, if SQL Server has to wait for a page to be retrieved from disk, that would be an eternity compared to retrieving a page from a remote node, and in such as scenario you ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on February 1, 2012
  • re: Performance impact: the cost of NUMA remote memory access

    Thanks Greg! I actually also tried OLTP workloads (e.g. TPC-C) in the same test setup, and didn't see any difference at all. It's more intutive with OLTP than with reporting in that the time it takes to get a page from another node accounts for an extremely small fraction of the total response time in an OLTP query. But for a reporting workload ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on February 1, 2012
  • re: Performance impact: the cost of NUMA remote memory access

    You can't disable NUMA at the hardware level. However, many machines have a BIOS setting that allows node interleaving, which effectively presents memory as if it were on a SMP machine. By default, this setting is disabled, and I don't know any real-world scenario where disabling NUMA at BIOS provides a performance advantage. But I have not played ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on January 31, 2012
  • Performance impact: the cost of NUMA remote memory access

    These days if you get a new server-class machine to run SQL Server, you can almost be 100% sure that itll be running on NUMA hardware. The recent AMD Opteron and Intel Nehalem-based processors are all built on some form of NUMA architecture. The current consensus is that as the number of processors grows, their shared memory bus can easily get ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on January 30, 2012
  • No respect: NUMA affinity meets query parallelism

    What happens when NUMA affinity meets query parallelism? It gets no respect! SQL Server allows you to affinitize a TCP port to a specific NUMA node or a group of NUMA nodes. Books Online has an article on How to: Map TCP/IP ports to NUMA Nodes. And this BOL article discusses various NUMA affinity scenarios. Recently, I have been playing with ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on January 28, 2012
  • T-SQL stored procedure for finding/replacing strings in a text file. Really?

    I know people have been doing all sorts of things with T-SQL, and I have absolutely no issue with people trying to push the limit of what T-SQL can do, or what you can use it to accomplish, especially when its for demonstration or pedagogical purposes, or as an intellectual exercise. But then I bumped into an article on writing a T-SQL stored ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on January 27, 2012
  • re: Performance impact: SQL2008 R2 audit and trace

    Greg; It's actually quite arguable whether the audit setup and the trace setup I tested are in fact similar. And I'm ready to concede that the test was kind of 'rigged' in favor of the audit setup. Just I wanted to get a feel for some sort of worst case scenario. I'm repeating the test with the trace setup using one of the security audit event, ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on January 25, 2012
  • Performance impact: SQL2008 R2 audit and trace

    We are told that SQL Server 2008 R2 Audit (and SQL Server 2008 Audit) has much less performance overhead than SQL Trace when we try to capture the same information. Knowing how SQL Server R2 Audit is implemented (i.e. on top of the extended events infrastructure), Ive always taken that as a given and never bothered to check it out. Recently, I ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on January 24, 2012
1 2 3 4 5 Next > ... Last »
Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement