databases

my first direct experience with databases was in the late 1980s or early 1990s, when i got a “job”, “working” for this… guy…

i don’t remember his name — possibly “henry” — but i remember his attitudes: he was always right, nothing he thought of had ever been thought of before, he was the richest, smartest, trendiest, most “on-top-of-it” dude that ever hit the face of the planet, and GAWD HELP YOU if you EVER got in his way.

needless to say, the “job” didn’t last long. it started with him demonstrating how generous he was, by buying me a disk caddy, so that i would have somewhere to keep all of the disks i was going to accumulate working for him. then he started asking me about computers. at the time, i was NOT a “computer geek”, nor did i want to be one (my father was one of the original “computer geeks” and i DID NOT want to be like my father), but i knew about computers because i had been working as a typesetter for a few years. he asked me what i didn’t know about computers, and one of the first things out of my mouth was “databases”, so he signed me up for a week of training with “FileMaker”…

what i learned was a bunch of recycled stuff from my already ample knowledge of microslut word and excel, with a bunch of “hypercard-like” stuff which i sort of vaguely understood (but nobody i knew used hypercard for anything, so i never really knew what i had missed until years later), and, at the same time i was doing this training, i was helping this… guy… clean out his house, because he was going through a divorce, or some awful shit like that, and he, basically, had to move EVERYTHING that was “his”, out of one house and into another, that was a few houses down the street…

which is where i learned that his “rich” persona was heavily financed by several HUNDRED overdrawn credit cards — he had been using one credit card to pay off another credit card, and when he ran out of credit cards, he would just start up a new one, and use it to pay off the previous ones… FOR YEARS… — at which point i decided that working for this guy might not be such a good idea, if i wanted to get paid.

quite apart from the fact that working for him was REALLY annoying…

so, ultimately, i spent a week learning really complex software that i never got to use for anything, and that was it, until i got my job at software.com, testing email servers, in 2001.

and, for all of my work with databases at software.com/openwave, i still don’t have a really solid grasp of what they are… where they “live”, what they do, how they work… anything… all i know is that, under the right set of circumstances, you can give “commands” to a database, and it will perform certain functions with a variety of different “objects”, the outcomes of which can be used in a multitude of different ways, depending on what is contained in your database.

i get the impression that databases are a lot like the world wide web, in that they both have a lot of objects (web sites) that are linked together in a somewhat-haphazard, but definitely organised way.

so, you can imagine that it was something of a surprise when, the other morning, i woke up, checked my email, and discovered two somewhat alarming notices. the first was warning me that i had used up 90% of my disk space on my server, and the other was warning me that a “table” on my main database was malfunctioning… or something… and collecting 251 GB worth of data… which, somehow, was NOT showing up in my cPanel, which says “Disk Usage 18.43 GB / 292.97 GB”…

and, of course, it happened on a sunday, when nobody’s in the office, and on mothers day, when even fewer people are in the office, and during a PANDEMIC… 😒

so, first thing this morning, after waking up to a broken heat pump, and a wife who wrenched her back, i wrote to my web designer, who said, oh yeah, we’ve seen this kind of thing before, it’ll cost between $200 and $500 to fix it…

and I DON’T EVEN KNOW WHAT’S WRONG… 😖

One thought on “databases”

Comments are closed.