Forum Replies Created

Viewing 15 posts - 196 through 210 (of 218 total)

  • RE: True or False

    Great question.

    But the version should have been specified. In SQL 2000 you can see the execution plan even for encrypted procs. Although that would probably have been a dead giveaway...

  • RE: More of computed columns

    Good question!

    I was pretty sure that the first create would fail since the operator ^ isn't described in BOL under arithmetic operators. It never occured to me that it could...

  • RE: Incremental additions

    Oleg Netchaev (10/29/2010)


    Oh well, I lost a precious point on this one. The statement in question

    select @a =+ @b-2

    looked so ridiculous that it made me think...

  • RE: Incremental additions

    Carlo Romagnano (10/29/2010)


    I think the question author tried to confuse us with the syntax for compound operators

    I think the question author CONFUSED himself with the syntax for compound operators,...

  • RE: Enable Broker Service

    I realized there was probably a 50% risk of getting it wrong which I did. :crying:

    Interestingly in BOL it wasn't specified whether assigning a new identifier with NEW_BROKER actually enabled...

  • RE: Activity Monitor Permission

    Good question!

    Maybe I shouldn't admit it, but Activity Monitor is something I had completely missed. DOH!

  • RE: Are all rounds created equal

    Hugo Kornelis (10/13/2010)


    It is your client software that converts this to a character representation so that you can see it on your screen. The client software chooses to represent these...

  • RE: Design

    MHilsher (9/24/2010)


    Rune,

    I've got some similar situations in a database that I'm working with and found that the alternative seems to be just as bad. We've created functions to get...

  • RE: Design

    jeff.mason (9/24/2010)


    As far as NULLs go, I have to say NULL is a good thing for some DATE columns. If you have, say, a StartDate and an EndDate column,...

  • RE: Design

    sjimmo (9/24/2010)


    Hugo Kornelis (9/24/2010)

    --------------------------------------------------------------------------------

    if the table is used in replication, ..., SQL Server requires that a surrogate key with the UNIQUEIDENTIFIER data type is also present in the table.

    I...

  • RE: Design

    Hugo Kornelis (9/24/2010)


    The more I think about this, the more I disagree with the notion that multiple identifier columns is a design flaw.

    Agreed. And the SQL standards agree too, if...

  • RE: Design

    Hugo Kornelis (9/24/2010)


    See the reply by Toreador to see why the distinction between zero-length string and NULL can be very important.

    As to the GUI - though I'd never call the...

  • RE: Design

    Toreador (9/24/2010)


    Rune Bivrin (9/24/2010)


    However, looking the table in the question I'd probably remove the NULL-ability on the cell phone numbers. Nullable VARCHAR often doesn't make sense. Particularly when they are...

  • RE: Design

    Hugo Kornelis (9/23/2010)


    Third bullet:

    "A table should avoid nullable columns."

    No. A table should avoid unnecessary nullable columns. When values may be missing in a column, making the column nullable is actually...

  • RE: Deprecated Features

    While I agree that errors aren't good, I didn't really notice them in this question. I looked up "deprecated features" in BOL, and found a reference to sys.dm_os_performance_counters. Matching that...

Viewing 15 posts - 196 through 210 (of 218 total)