Forum Replies Created

Viewing 15 posts - 31 through 45 (of 251 total)

  • RE: Database Design Follies: NULL vs. NOT NULL

    Sounds like the requirements are missing. Null requirements? However, if the data is really missing, each column might require custom treatment because of business requirements. In this...

  • RE: Database Design Follies: NULL vs. NOT NULL

    The SELECT clause can arbitrarily format the results. If it is a token, I would consider it an application token, not a database token.

    Back to an earlier question....

  • RE: Database Design Follies: NULL vs. NOT NULL

    Grasshopper, if the "null" columns are stored in separate tables (6NF?), then a join (left) to build the original table would return nulls for the missing value. I see...

  • RE: Database Design Follies: NULL vs. NOT NULL

    How about defining the null to mean that this column should exist in a separate table where there would be no record for this value? Then construct the T-SQL logic...

  • RE: Database Design Follies: NULL vs. NOT NULL

    The debate reminds me of a quote, "I'm a mathematical optimist: I deal only with positive integers."

    I'm glad I came across this discussion. 6NF with only one non-key column...

  • RE: Database Design Follies: NULL vs. NOT NULL

    roger.plowman (3/1/2016)


    ZZartin (3/1/2016)


    roger.plowman (3/1/2016)


    patrickmcginnis59 10839 (2/29/2016)


    roger.plowman (2/29/2016)


    I still don't see why relational tables can't have records for TBD, N/A, and UNK.

    If you need to know why a value is missing,...

  • RE: Database Design Follies: NULL vs. NOT NULL

    kenambrose (2/29/2016)


    [[You'll have up to 8 bits to designate just "how" the data is missing. You certainly do NOT want to store 'TBD' | 'NA' | etc. in any column(s).]]

    Oh...

  • RE: Database Design Follies: NULL vs. NOT NULL

    MadAdmin (2/29/2016)


    j-1064772 (2/29/2016)


    rstone (2/29/2016)


    I think nulls are used more often than required, but they have their place. If we start with a rule that forbids nulls in the database, then...

  • RE: Database Design Follies: NULL vs. NOT NULL

    Using a single record in a related table to define "missing" or "unknown" is an option that I have seen in use. I thought it resulted in some very...

  • RE: Database Design Follies: NULL vs. NOT NULL

    I think nulls are used more often than required, but they have their place. If we start with a rule that forbids nulls in the database, then we are doing...

  • RE: Baseline Collector Solution V2

    Robert, I look forward to the updates. Here is a script to enable the jobs and schedules after a fresh install. It might save a few clicks here...

  • RE: Baseline Collector Solution V2

    In the past, I use a tool called ClearTrace to report on the worst of the worst. (I set high limits on the trace reads or writes.) Even...

  • RE: Baseline Collector Solution V2

    Robert, I'm running your solution on my desktop. Looks good to me. Added some views for fun. Single values for average MB/sec, IOPS, and stall per database?...

  • RE: Baseline Collector Solution V2

    Thanks Robert. I've been using TYPEPERF to collect counters from several servers. It appears that if I want IO detail at the database or database file level, I...

  • RE: Usage of CTE - Trick with Dates

    Requirements often don't directly address transactions and locking. Non-functional requirements normally don't specify or limit T-SQL methods. A table that describes the preverbal "it depends" by relating requirements...

Viewing 15 posts - 31 through 45 (of 251 total)