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 54 (538 total posts) < 1 second(s)
  • re: PDW Concept on NUMA

    it has been a long time since I have looked at PDW, is it APS now? I lost interest when they went 7.2K HDD only. I think MS has become dominated by marketing types who become enamored with paper specifications, in this case, the size of the database, rather than how it is used. I am of the opinion that there are situations in which we want massive ...
    Posted to Joe Chang (Weblog) by jchang on January 7, 2016
  • re: SSD Form Factor and interface

    My opinion is that the cloud is a response to IT infrastructure practices. Too many buy gold bricked systems, mandate standard configurations that do not suit databases etc, implement procedures that obstruct the ability to do information technology. There have times I have spent several weeks trying to negotiate with the infrastructure team on ...
    Posted to Joe Chang (Weblog) by jchang on December 29, 2015
  • re: Data Tales #5: The Case of the Rogue Index

    hello Greg Not that I think it is a smart idea to disable row locks willy nilly, but if you want to speculate why, in my slide from CMG2004, slides 50-53 http://www.qdpma.com/ppt/QuantitativePerformanceAnalysis_CMG2004.ppt in query performance of the key lookup operation versus rows, there is a major collapse in the neighbor of 3000-5000 ...
    Posted to Greg Low (The Bit Bucket: IDisposable) (Weblog) by jchang on December 17, 2015
  • re: Computers without ECC memory are crap - no exceptions

    thanks donaldvc, I will read this when I get a chance. That ECC for single/double bit errors is necessary has be known for a long time. From a quick skim, I think this article is stressing the importance of correlated multi-bit errors, given the organization and high density of DRAM. My comments will be a the bottom of the main post.
    Posted to Joe Chang (Weblog) by jchang on December 10, 2015
  • re: SSD Form Factor and interface

    Good question. Sorry about the long winded answer, but life is complicated. I do agree with shared storage concept in HDD days, having a common pool of HDD so that each host can access the aggregate IOPS capability when needed. This and managing the complex storage system alone would have justified a good profit margin. But storage felt the ...
    Posted to Joe Chang (Weblog) by jchang on December 7, 2015
  • re: Join and Query hints – serious DBAs need to learn this

    (Santa?) Claus: Sommarskog is a stud! 4.8 When OPTION (RECOMPILE) Hurts You and people say I am over analytical, heck I'm a hip shooter by comparison. Cartman: nice,
    Posted to Joe Chang (Weblog) by jchang on December 4, 2015
  • re: Join and Query hints – serious DBAs need to learn this

    If you want to say that if the recompile cost is low, then use the OPTION(RECOMPILE) because it is simplest, then that's fine. I do not agree that this works best in all but the highest throughput system, 1-2%. I have seen compile issues sink what I consider middle-high systems, perhaps in the 10% range. I recall one site where they were at 2000 ...
    Posted to Joe Chang (Weblog) by jchang on December 3, 2015
  • re: Join and Query hints – serious DBAs need to learn this

    OPTION (RECOMPILE) does work for the multiple optional SARG or catch-all per Gail. I tested it on 2008R2 SP3. statement recompile was introduced in 2005, but I am not when it worked for this issue. I recall hearing people discuss this and that there were issues in the beginning. If you already have code like this, this is the easiest fix, but I ...
    Posted to Joe Chang (Weblog) by jchang on December 2, 2015
  • re: Join and Query hints – serious DBAs need to learn this

    you are only claiming that OPTION(RECOMPILE) generates the correct plan. My assertion is that with any degree of query complexity, but where there are highly selective search arguments the recompile will cost more than the execute, regardless of whether the OPTION(RECOMPILE) produces the correct plan
    Posted to Joe Chang (Weblog) by jchang on December 2, 2015
  • re: Join and Query hints – serious DBAs need to learn this

    ok, I have a big complex stored proc, WITH RECOMPILE at the proc level will really suck versus statement level OPTION(RECOMPILE) which could be much smaller than the whole procedure, depending on the situation. So, the situation still applies if the query execution time is expected to be less than statement recompile, you would like to reuse ...
    Posted to Joe Chang (Weblog) by jchang on December 2, 2015
1 2 3 4 5 Next > ... Last »
Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement