Forum Replies Created

Viewing 15 posts - 1 through 15 (of 36 total)

  • RE: SSC Clinic: Finding the rogue query

    tolga.kurkcuoglu (9/13/2012)


    from the name of the table, I guess there is a considerable amount of records in it.

    It looks like it, unneccessarily, computes the dateadd function for each row.

    you might...

  • RE: Never, Ever Use Clustered Indexes

    patrickmcginnis59 (6/21/2012)


    I freely admit that I'd like to be biased toward portability in the general case, but that it would take additional effort to materialize that bias in specific efforts.

    I...

  • RE: Never, Ever Use Clustered Indexes

    patrickmcginnis59 (5/31/2012)


    Grant Fritchey (5/31/2012)

    I'm with you. Fast enough is fast enough.

    But, I remember when a friend of mine (wish I could say I did this) spotted a problematic query in...

  • RE: Never, Ever Use Clustered Indexes

    Grant Fritchey (5/31/2012)


    The message may have been unclear, again apologies, but you're wrong that this is common knowledge. Tons and tons of developers and plenty of DBAs still believe in...

  • RE: Find Customers Who Bought "A" and "B" But Not "C" (SQL Spackle)

    Berl (3/30/2012)


    Although CPU time difference is not very great, the difference is much bigger for the elapsed time.

    Elapsed time includes wait time and is not a good measure of...

  • RE: Twist in ISNULL function

    Possibly easier is to use COALESCE, which doesn't have this problem. COALESCE is also more flexible.

  • RE: Query plan issues after 2000 -> 2008R2 migration

    Syed Jahanzaib Bin hassan (7/12/2011)


    Change the compatibility mode to 100 and rebuild the indexes and update the stats also,did you ?

    I haven't tried that - change compatibility to 100, indexes/runstats,...

  • RE: NoSQL is Not the Answer

    Eric M Russell (3/21/2011)


    I'm not interested in an academic point of view about SQL; it's their job to constantly argue anything. As a professional database developer, an actual practitioner, what...

  • RE: Could not continue scan with NOLOCK due to data movement

    bob mazzo (3/17/2011)


    Thank you for your response.

    I have been considering changing the READ UNCOMMITTED TO READ COMMITTED (which I understand to be the Sql Server default).

    I only put the UNCOMMITTED...

  • RE: Could not continue scan with NOLOCK due to data movement

    Am I missing something here?

    The fundamental problem is running at READ UNCOMMITTED. No READ UNCOMMITTED, no problem.

    If you're getting this error, you a reading uncommitted transactions.

    Also, a thought:

    FROM filter_list flst,...

  • RE: Tuning Locks

    I'm with Kevin on this one.

    If you're running SQL Server out of lock space, your problem isn't a lack of memory, it's that you're running something that takes and...

  • RE: NoSQL is Not the Answer

    It just occurred to me that NoSQL may, in fact, be the answer. The problem is that few people advocating it understand the question.

  • RE: NoSQL is Not the Answer

    The primary trouble I've seen with the NoSQL movement so far is that a large portion of those who are migrating to it are using it because they don't understand...

  • RE: Creating a comma-separated list (SQL Spackle)

    This is useful. I only have to do this once in a while, and I've been using clumsier methods.

  • RE: Sorting Months By Number (SQL Spackle)

    I don't know why people would mark this article down, but people are funny sometimes.

    Even though I probably won't use this technique (I can't think of a time when I've...

Viewing 15 posts - 1 through 15 (of 36 total)