Forum Replies Created

Viewing 15 posts - 211 through 225 (of 230 total)

  • 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...

  • RE: Predict the outcome

    I couldn't find any mention of the restriction on increment either. My gut reaction was to answer "error" given that an zero increment makes no sense, but as I couldn't...

  • RE: Rowcount and multiple assignment

    Yep, I was wrong about that. And I even ran a test to verify my thought before I posted, but I managed to read the results of that test wrong....

  • RE: Rowcount and multiple assignment

    It's important to note that SET @result = cast (@@rowcount as varchar) does NOT change @@ROWCOUNT. The first 1 comes from the last INSERT #n VALUES(3).

    This is one of the...

  • RE: Cast vs. Convert

    sknox (3/8/2010)


    Rune Bivrin (3/8/2010)


    Good question, but which alternative is correct depends on how you define platform. If you define "platform" as "versions of SQL Server", then CONVERT works in every...

Viewing 15 posts - 211 through 225 (of 230 total)