Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>A tool like you describe, that tried to analyze your data and metadata and advise you of <em>possible</em> non-normalized structure, would give <strong>wrong suggestions</strong> so frequently that it would make Clippy, the Microsoft assistant seem like an indispensable writer's aid.</p> <p><img src="https://i.stack.imgur.com/pOsPS.png" alt="enter image description here"></p> <p>The process of normalization involves mapping software requirements to a logical data model. An analysis tool cannot know your data requirements any better than you do. So it can't infer from an incorrect database design which parts of it are wrong.</p> <p>I understand you have qualified the question and you have limited expectations for the tool's capability. But you would want it to be useful for ordinary, everyday tasks -- but it would not be reliable even for the most simple cases.</p> <p>Compare to static code analysis tools. Suppose you write an application and deliver it to your client, and the client says "why can't I send email from this app?" How would a static code analysis tool tell you that you omitted a desired feature? It can't know those requirements.</p> <p>Likewise, how would a database normalization analysis tool know whether it's appropriate for the <code>UserAccount</code> table to have a single <code>MobilePhoneNumber</code> attribute, or if it would be more appropriate to separate phone numbers into another table so a single user could have multiple phones listed?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload