Forum Replies Created

Viewing 7 posts - 1 through 7 (of 7 total)

  • RE: A real doozie!

    Mike01, we're past that now. It was two rouge rows in the Gender column that were making SQL unhappy. The grand mystery was that SQL was evaluating the entire column...

  • RE: A real doozie!

    That sounds plausible and it's what I have been thinking of as well. The execution plan is simply different for each approach. It's different enough that, as you state, the...

  • RE: A real doozie!

    Good point Jeff. In this case, I didn't have any trailing spaces but your point is well taken. LEN indeed doesn't count trailing spaces. In this file, the gender column...

  • RE: A real doozie!

    Success! Yet, the mystery continues as I do not feel satisfied with WHY this happens in T-SQL.

    When I ran this, in an attempt to modify the Gender column:
    alter...

  • RE: A real doozie!

    Ok. Just for kicks, I will move that column somewhere else, drop it, recreate it to char(1), restore, and give it a go again. Still, it doesn't make sense that...

  • RE: A real doozie!

    Here are the column definitions of anything I believe is relevant.

    NAME_MASTER

  • RE: Collecting SQL Server 2000/2005/2008 baseline

    Jorge Serres (5/18/2014)


    Just change column physical_memory_in_bytes with [physical_memory_kb/1048.576]!! otherwise it'll generate some blood!:-D

    I am running SQL Server Enterprise 2012 SP1. I just changed the line in the quote above and...

  • Viewing 7 posts - 1 through 7 (of 7 total)