Most of my data is processed to be displayed on the web, though in case of catastrophe I can print out the relevant data for the insurance company. My goal is to find an easier way to store, add to, edit, and access my data. My data is currently a mixed hierarchical and tabular design. From what I am seeing here, SQL is just tabular with a lot of repetition. (From the example above, I would be putting all artists' albums in one jumbled table instead of individual artists' albums tables such as "Duran Duran's albums" or "Sting's albums".) My goal is to find a data storage system which has fewer files to maintain like a music file and a movie file (my movie data is ten times more of a headache than my music data).
If you are very interested, you can crawl all over my data to see how I am storing it now. In some spots, it is a jumbled mess. Do you think my data could ever fit into SQL tables?
Thank you all for dropping by and giving me something to look at and think about.
In reply to Re: OT: SQL and me
by Lady_Aleena
in thread OT: SQL and me
by Lady_Aleena
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |