Forum Replies Created

Viewing 15 posts - 136 through 150 (of 233 total)

  • RE: Dropping Audit Sessions

    Not quite sure I agree with the answer. There is a difference between what I must do and what I should do. According to the quoted article you do not...


    Just because you're right doesn't mean everybody else is wrong.

  • RE: SQL 2016 COMPRESS

    Nice! Learned something new today.


    Just because you're right doesn't mean everybody else is wrong.

  • RE: Trailing

    barry.mcconnell (10/11/2016)


    Interestingly, if you examine Information Schema Columns, the table only has 3 columns.

    I'd be a lot more surprised if there were more columns than that. Without a name or...


    Just because you're right doesn't mean everybody else is wrong.

  • RE: Trailing

    Ed Wagner (10/11/2016)


    Okay, that's a little weird. Microsoft has updated the language to allow syntactically incorrect SQL based on popular habits. I see why they did it, but...


    Just because you're right doesn't mean everybody else is wrong.

  • RE: Trailing

    This is a quite uesful anomaly. It allows for easy cut'n'paste between table creation scripts, without worrying about deleting any trailing commas or having commas between constraints.


    Just because you're right doesn't mean everybody else is wrong.

  • RE: Running External Scripts

    Nice'n'easy!

    Funny part in the docs:

    [ @language = ] 'language'

    Can be any supported language that has been registered by using xxx. language is sysname.

    Valid values are 'R'.

    How do I invoke xxx?:-P


    Just because you're right doesn't mean everybody else is wrong.

  • RE: Comparing with NULL

    Nice question, but the correct answer is as usual: "It depends". In this case on the setting of ANSI_NULLS.


    Just because you're right doesn't mean everybody else is wrong.

  • RE: Complex foreign key

    Good question, but a small nit-pick:

    "The syntax of the batch is correct" is not really an output of the batch, but the conclusion of the parser. That message doesn't appear...


    Just because you're right doesn't mean everybody else is wrong.

  • RE: Updating a View with CHECK

    shaneoneillis (9/15/2016)


    Interesting how it fails with no error, thanks Steve!

    Disregarding the fact that it doesn't, of course...:-P


    Just because you're right doesn't mean everybody else is wrong.

  • RE: Updating a View with CHECK

    Mighty (9/15/2016)


    +1

    Reading this question, it seems logical to assume that there is a record with id 2.

    And also assume that it's original value for the HireDate falls within the CHECK...


    Just because you're right doesn't mean everybody else is wrong.

  • RE: Updating a View with CHECK

    Magnus Ahlkvist (9/15/2016)


    I don't Think the correct answer is correct.

    When I try to update a view (defined using WITH CHECK OPTION) with a value which makes the row fall outside...


    Just because you're right doesn't mean everybody else is wrong.

  • RE: Union Date/Time Data Types

    In addition to the previous, the padding has changed on SQL 2016. It will pad with 0000, 3333 or 6667, depending on the value of the DATETIME. I suppose that...


    Just because you're right doesn't mean everybody else is wrong.

  • RE: Rounding Rules

    And once again, Steve's proof-reading skills prove somewhat lackadaisical 😛


    Just because you're right doesn't mean everybody else is wrong.

  • RE: TRUNCATE and ROLLBACK

    And time to get coffee 🙁


    Just because you're right doesn't mean everybody else is wrong.

  • RE: Stretch Database Datatype Limitations

    Steve has too much on his hands.


    Just because you're right doesn't mean everybody else is wrong.

Viewing 15 posts - 136 through 150 (of 233 total)