Forum Replies Created

Viewing 15 posts - 496 through 510 (of 1,353 total)

  • RE: The Politics of SQL Security

    I'm with you on all things but the 1433 port. I could easily be convinced, but could someone explain that more or point me to a source that can....

  • RE: Using reserved words as column names

    I agree, can't stand brackets. To the point that when I have SSMS script something out, I remove them.

    Yeah, same here. Brackets are heinous. That's another great thing about SQL...

  • RE: Opinions on triggers

    I would say to use triggers to maintain audit information and to support low-level data integrity that cannot be done via the more standard methods. Some others have been...

  • RE: On formatting SQL code

    Readability matters nearly as much as accuracy and performance.

    Agree with the comments and the others along this line. Phil's comments that it may look silly with a simple statement...

  • RE: On-Time, or Not

    It would be wonderful to be able to work a normal 9 to 5 schedule, but most issues occur when everyone else from the office is sleeping, so I get...

  • RE: On-Time, or Not

    When I was in the military a saying I often encountered was "if you're not five minutes early, you're ten minutes late." Point was to be on-time. Especially...

  • RE: Large Table Design Best Practices

    E.g. run a query to get the average length of comments provided. LEN('') is 0 which reduces the average length; LEN(NULL) is NULL and is not included in the average....

  • RE: Large Table Design Best Practices

    A blank string does not mean that it is known that there is no value; a blank string means that it is known that there is a value, and that...

  • RE: Large Table Design Best Practices

    Does not this suggest that legal entities should be in a different table instead of mixing legal and moral persons ?

    As always, it depends. But in this case...

  • RE: Large Table Design Best Practices

    RonKyle (3/4/2016)

    No issues here. I of course know a date data type can be NULL. My only issue, and one for which there is no solution in an OLTP environment,...

  • RE: Large Table Design Best Practices

    RonKyle (3/4/2016)

    I don't have a Closed column in the simplified design, but a Closed Date. Ideally this would be blank if the order is Open because the date doesn't exist,...

  • RE: Large Table Design Best Practices

    For your example, only 'Work Order Status' and 'Technician Assigned' could be normalized out in a standard structure. My question is simple. Why not? One of the many purposes of...

  • RE: Large Table Design Best Practices

    I have to agree with Sean and Grant. You can get great performance out of a normalized structure and the integrity is there in the design. Moving the integrity to...

  • RE: Large Table Design Best Practices

    That column cannot be made NOT NULL in the design because you can't enter that data when the first part is created. How do you enforce the NOT NULL...

  • RE: Large Table Design Best Practices

    The biggest challenge of using a single table for this is that the integrity checks would have to be moved to the application.

    I've used these kinds of accumulated snapshot...

Viewing 15 posts - 496 through 510 (of 1,353 total)