Heh... "Computing Revolution". I call it the "Dust Revolution" because data and code is just like dust... it accumulates on horizontal surfaces (and sometimes sticks to vertical surfaces in the form of cobwebs). The bigger the surface, the more dust there is. Very much like a bad drug habit, it's self-perpetuating and the more you use it, the more you need it and the more you do it. A lot of programmers have forgotten how or never learned to "dust" things off. 😀
The really cool part is that it's been beneficial to us old farts in many ways. I was the big kid on the block way back when I bought my first computer. It was an OHIO scientific computer and I had a whopping 8 KILO bytes (twice as much as my friends had) and BASIC in ROM along with a cassette drive interface so I could store my programs on tape and easily retrieve them. It was amazing what I could do on that machine especially when I connected it to external devices.
I went through it all... I remember the incredible upgrade I was able to do on one of my machines from 512K of RAM to a whopping 640K of RAM and had a 40MB hard card installed (it HAD to be partitioned because DOS couldn't handle drives more than 30MB at the time.
I remember my first 1GB drive. It cost me $1,000 USD plus I had to buy the SCSI interface card to use it. I was sure that I'd die of old age before I ever filled up such a drive. I also got my first 9600 Baud modem card at the same time.
Now I have single column non-clustered indexes that are more than 50 times that size. I also have a reasonably recent laptop with 6-core i7's threaded to 12, 32GB of RAM, a 2GB harddrive, and 2GB of high performance SSDs (reminds me of a RAM drive but certainly much better).
Performance challenged code and very large databases continue to grow, mostly because a lot of people are on the hardware drug. The cool part is that as more nearly useless data grows, so does the technology to store it and retrieve it quickly. Communications between computers has also increased (imagine a 9600 Baud connection nowadays... I actually started with a 300 baud modem).
The self-perpetuating drug of trying to use hardware to make our code faster and keeping everything has forced the hardware industry to get better and better and, as it does, more and more computational "dust" settles requiring still better hardware.
The good part about all of that is that people that DO write good, high-performance code are in demand, especially when it comes to data and databases. And, we don't necessarily need to use or even learn all the bright-shinny new stuff that frequently lasts about as long as a flash in a pan.
A lot of that new stuff is created just because people don't "dust" any more. They also don't know how to keep from creating lots of "dust" when they design a database or write code to use it 😀
Some ask me what I do for a living... I sometimes tell them "I'm the cleaning lady... but I don't do Windows". 😀
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
"Change is inevitable... change for the better is not".
"Dear Lord... I'm a DBA so please give me patience because, if you give me strength, I'm going to need bail money too!"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)