Forum Replies Created

Viewing 15 posts - 2,926 through 2,940 (of 3,348 total)

  • RE: Solving the "Running Total" & "Ordinal Rank" Problems (Rewritten)

    Paul White (2/4/2010)


    Hi Hugo,

    You overlooked my post which addressed the 'problem'. It was quite long, so I'm quite shocked that you missed it 😉

    Guilty as charged 😉 I...

  • RE: Solving the "Running Total" & "Ordinal Rank" Problems (Rewritten)

    Hi Jeff,

    As indicated in my previous message, I somehow lost sight of this discussion. Sorry for my sudden disappearance from this topic.

    First, thank you for optimizing my alternative running totals...

  • RE: Solving the "Running Total" & "Ordinal Rank" Problems (Rewritten)

    Condorman (11/14/2009)


    Really interesting discussion guys. I do have one complaint about Hugo's alternative method, though.

    Here in the relevant bit from Hugo's code.

    INSERT INTO @Results(AccountID, Date, TransactionDetailID, Amount,

    ...

  • RE: Comparing a hash

    john.arnott (2/3/2010)


    The real problem is that REPLICATE uses the same input as output data type, which in this case has an 8000-byte limit, and that longer values are truncated.

    I...

  • RE: Comparing a hash

    a hash which treats two different strings as identical is a a serious failure.

    No, it's not. Collisions in a hash are by design. After all, the possible number of different...

  • RE: Comparing a hash

    vk-kirov (2/1/2010)


    Hugo Kornelis (2/1/2010)


    the result of the HASHBYTES algorithm now exceeds 8000 bytes

    No, it doesn't 🙂 The SHA-1 algorithm always produces 160-bit output, here is the proof: http://en.wikipedia.org/wiki/SHA#Comparison_of_SHA_functions.

    The warning is...

  • RE: Comparing a hash

    Nice question. But the explanation is incorrect.

    There is no 8000 byte limit on REPLICATE. But there is one on the VARCHAR data type, and since 'A' is considered to be...

  • RE: Query cost

    vk-kirov (1/27/2010)


    Carlo Romagnano (1/27/2010)


    FROM BOL:

    Including an extremely large number of values (many thousands) in an IN clause can consume resources and return errors 8623 or 8632.

    This may happen only...

  • RE: Query cost

    If I critisize a QotD, I always try to maintain a positive tone. Especially since, after having submitted some of my own, I know how hard it is to create...

  • RE: Declarative Data Integrity

    Thanks, Bitbucket!

    And thanks for submitting the QotD as well. I have submitted a few of my own, so I know how much energy goes into it - and how, despite...

  • RE: Declarative Data Integrity

    Thanks, Kelsey. You write exactly what I intended to write, but in a much nicer tone.

    Bitbucket, if my post came across too harsh, I apologise for the tone.

  • RE: Declarative Data Integrity

    bitbucket-25253 (1/25/2010)


    Hugo Kornelis

    Not a good explanation, though

    Ditto for Kelsey Thornton

    Did you click on the supporting documentation link to read the full explanation?

    Did you read what I actually wrote?

    The explanation says...

  • RE: Declarative Data Integrity

    Mauve (1/25/2010)


    I responded with the correct answer (2, 1, 0) but was marked Wrong!

    BTW, the code will only run under SQL Server 2008, which wasn't stated. And it will...

  • RE: Declarative Data Integrity

    WayneS (1/24/2010)


    Edit: I also curious... how much are cascading updates/deletes used in a production environment? Personally, I've never seen it actually used, so I'm curious as to how much it...

  • RE: Declarative Data Integrity

    Good question.

    Not a good explanation, though.

    "The constriaints prevent some inserts and deletes from occurring." - I did not run the code, but I am pretty sure that all inserts succeed,...

Viewing 15 posts - 2,926 through 2,940 (of 3,348 total)