GEEQL Turns Left at Albuquerque!


I’m delighted and still a bit surprised to have been selected to speak at SQL Saturday 358, in Albuquerque, New Mexico, where, if you’re a Bugs Bunny fan, you’ll know that somewhere, somehow, you’ll just HAVE to take a left turn… ­

And when you do, turn left here and join us.  Take a look at the schedule - there’s a boatload of awesome people converging on Albuquerque to share their knowledge with you.

This will be my fifth SQL Saturday and my second one as a speaker (first one was #337 in Portland) and I’m not sure who learned more – the folks listening or me speaking, but it was an enough of an experience to get me to want to do it again, and share and improve some of the lessons I’ve gathered over the years.

So, what will we talk about?

We’ll talk about how communication affects us daily, how it can be the easiest thing to do, and the hardest thing to do well, how who you talk to determines what you talk about, and how you do it – and all in a way that’s designed to show you how to move ahead, both in and outside of your career.

We’ll talk about…

Simple stuff – (When to say what) but in a way that’s easy to understand (using the Titanic as an example)

And complicated stuff (did you realize that men and women communicate differently? – and that both ways are valid?)

And by the time we’re done, we’ll all have laughed a bit, commiserated a bit, but most of all, we’ll all have learned something.

Looking forward to seeing you there!

Leave a comment

Posted by on January 29, 2015 in Uncategorized


T-SQL Tuesday #60– Something New Learned


So – as I write this, it’s the Monday evening after Summit

Emotions are still fresh, but my mind still trying to double-clutch its way back to thinking about how to apply all the things I’ve learned and I’ve been struggling to find words to answer the question asked for this one, but I think it was narrowed down to one tweet that we’ll get to in a moment.

Like many of you, while I work around a lot of people, and work with people, most of the work I do is fairly solitary. I don’t often get a chance to learn with or just relax and chat with folks outside of work who are fighting the same battles, have similar goals, and are struggling with similar  issues.

I’d been working quite a few overtime hours, plus getting ready for my first presentation in a long time for SQLSaturday 337, so I was a little frazzled coming into Summit14, and was, frankly, looking forward to what I’ve taken to calling “Summer camp for Geeks”.

Take the best thing you can remember from any summer camp you’ve ever been to. (For me, regardless of the camp, it’s the camaraderie – so let’s go with that).

Take that camaraderie – and add to it the concept of a support group. Oh, for those who haven’t been part of a support group, let’s just go to our old friend Wikipedia, which states, in part:

In a support group, members provide each other with various types of help, usually nonprofessional and nonmaterial, for a particular shared, usually burdensome, characteristic. Members with the same issues can come together for sharing coping strategies, to feel more empowered and for a sense of community. The help may take the form of providing and evaluating relevant information, relating personal experiences, listening to and accepting others’ experiences, providing sympathetic understanding and establishing social networks.

Wait – let’s look at those last two sentences again one at a time…

“Members with the same issues can come together for sharing coping strategies, to feel more empowered and for a sense of community.”

Uh – yeah – there’s 5,000 of us from all over the planet, most of us working in pretty solitary kinds of positions, where it’s often hard to talk about the issues we’re facing, often because we’re the only ones in the company facing them. Interestingly, we’re often introverts, which means at some level, we’re okay with the whole “working by ourselves” thing. But it is nice to know you’re not the only one out there trying to invent this particular wheel, or shove this particular boulder up a hill… Again… (see Sisyphus). That brings us to the second of the two sentences:

“The help may take the form of providing and evaluating relevant information, relating personal experiences, listening to and accepting others’ experiences, providing sympathetic understanding and establishing social networks.”

Just read that again… I know, it’s likely the third time… Right – then look at the picture of the community zone below from the tweet by Neil Hambly (B|T)

I was just stunned at the simplicity of Neil’s comment, “This what #sqlhelp is like in the flesh Many folks just in the community zone waiting to help others”

Just from this shot, I see Kevin Kline (B|T) chatting with someone on the floor on the left. Wendy Pastrick (B|T) is chatting with someone about dead center. I think that might be Grant Fritchey (B|T) there in one of the blue shirts in the background. I know for sure there was at least one SQUEEEE! (B|T) there. ;-)

I know there are other folks I didn’t get a chance to meet or can’t recognize in this shot – but I was in the same spot that Neil was when he took that picture and saw the same thing.

And heard the same thing.

And it was people simply wanting to help others who were going down the same path. People would come to that blue carpet and be welcomed in. They’d reach out for help, and there was someone in there, reaching back. Understand, there were folks just starting their careers in there mixed right in with folks who were pillars of the SQL community, there were beginners, MVP’s, and MCM’s, and all were reaching out to each other to help.

That help took all forms. Sometimes, someone just needed to talk something out. Other times, it was a deep conversation. Often there was laughter, and what became known as #sqlhugs as those of us who’d emailed or tweeted with others for years finally got to meet them face to face. In the shot, you see people talking with each other, you see people on their laptops while on support calls during the conference itself (it was obvious on some, you could hear one side of the conversation, “…Okay, now click ‘next’…”)

And for some, just like Neil said, it was #sqlhelp in the flesh.

If you’re not familiar with the #sqlhelp hashtag – click on that one on the left there – it’ll take you to the post Brent Ozar (B|T) put out on his blog to explain how it works, with the opening line: “You’ve got questions, we’ve got answers.”

And at summit – sqlhelp wasn’t just something we typed.

We got to see some of the people behind it (that’s be all of us)

We got to meet them.

And we got to experience that camaraderie of summer camp and the warm embrace of a support group.

We got to hear the laughter behind an LOL as someone got a joke, or got to actually see, talk to, and listen to the folks behind it.

And over time, what became clear to me is that while I’ve used #sqlhelp in the past and monitor it in the present, #sqlhelp isn’t just some search engine that spits out answers like ones and zeroes. . It’s real people, with real experience (and real questions), again, some just starting out, some, like I said, pillars of the community, but who all take or make the time to get an answer for you, and then, often, check back with you to make sure you got it.

#sqlhelp is folks who care, folks who’ve reached forward to others in their careers and are now reaching back to help those who need it.

That’s one thing I learned at Summit this year. Not just in my head, but in my heart.

And in case no one’s said it out loud, it’s appreciated.


Posted by on November 11, 2014 in Uncategorized


Tags: , , , , ,

GEEQL Speaks! :-)


Hey all,

I’m honored, thrilled, and just a wee bit terrified to have been chosen to speak at the Portland SQL Saturday, November 1st.

(and I blame Julie (B | T) for this) ;-)

Many of you have read the stories I’ve written here about SQL or the stories about life on my other blog.  Well, here’s your chance to actually hear some of them with the tidbits of knowledge I’ve picked up along the way and how it all applies to life at work..

I’ve learned much over the years and it seems like it’s time to start giving back. My presentation will be about communication – and a few of the ways I’ve learned about how to do it better.

On the Agenda (barring any last minute changes) will be lessons as you see below using stories, illustrations, and examples you might not expect, but do indeed get the point across, and tell a story.

So, if you’re curious – here’s the outline I’ll be working from:

Communicating: The Various Directions

  • Across to peers/other departments
  • Up to management/leadership
  • Down to Support your directs
  • Getting the right numbers to the right people
  • Using numbers effectively (Presentations)
  • Understanding your audience
  • Using those numbers to
    • Help state your case
    • Help get what you want
    • Polish your resume
  • Communicating “Oops”
  • Sometimes, Things go wrong
  • Communication during Emergencies

And last but not least – why it’s all important.

I look forward to seeing, learning, and laughing with you there.




1 Comment

Posted by on October 28, 2014 in Uncategorized


Tags: , ,

Problem Solved: Lync Reporting issues

Awhile back we had a pretty significant series of issues with our Lync implementation that took some time to resolve. Now that it is, I thought I’d write up something for one of them to help others that have run into the same problem so that it can be fixed up once and for all.

Note: these notes come from my own personal experience with a dash of a case we had open with MSFT at the time.

Lync, for those of you who aren’t familiar with it, is Microsoft’s corporate instant messenger suite – which brings voice, (both individual and conferencing), sharing, and IM into one package. If there was ever any program I’ve ever used that’s changed how I work, this is it.  Calls, conferences, desktop sharing, all from the same app.  Truly well done.

That’s on the front end.

On the backend, however, it gets a little more involved – and for those running the app, there’s a lot of reporting that will allow you to monitor things like call quality, what the system is doing, and if there is trouble in paradise, as it were, you can use this reporting to start narrowing down the issues you’re running into, and that will help you both troubleshoot and resolve them.

And that’s the part that was giving us trouble.

It’d work for a bit, then give us weird errors, and the folks trying to troubleshoot global call/connection issues were completely blocked. So they were frustrated, and we needed to figure out how to fix it – not just this once, but fix it period.

The problem:

Lync reporting, when we got to the Monitoring Dashboard report, would often render an error like this:

What you'll get if the stored procedures haven't been run

What you’ll get if the stored procedures haven’t been run

If you can’t read the image, there are two error messages:

“Report processing stopped because too many rows in summary tables are missing in the call detail recording (CDR) database.  To resolve this issue, run dbo.RtcGenerateSummaryTables on the LcsCDR database.”

“Report processing stopped because too many rows in summary tables are missing in the Quality of Experience (QoE) database.  To resolve this issue, run dbo.RtcGenerateSummaryTables on the QoEMetrics database.”

You can find that I’m not the only one that ran into this error by just using your favorite search engine – Google, Bing, DuckDuckGo, whatever. (the results are pretty similar)

Bottom line – the error is the same: Some level of activity that’s been happening on the server is not reflected in the troubleshooting reports you want – and the error message has both good and bad parts to it.

The good: As far as error messages go, this one is surprisingly clear. Basically do what it says, and, depending on how much it has to summarize, it takes a few minutes and sums up a bunch of information that is amazingly useful in the reports our Lync team needs.

The bad: It exposes names of objects that someone might not actually want to have exposed, though people who see this are often the people who need to, so it’s a bit of a two edged sword.  The other thing is that there’s nothing to give us any indication of how often what’s mentioned in the message needs to run. I figured (as did many of the others who’ve run into this) there was some process that called this set of stored procedures at some defined period, but from what I saw in my research and what I experienced myself, that was not happening for the folks who were running into this. On a hunch, while was on a call with MSFT on a related issue, I discovered that the stored procedure referenced in the above screenshot needs to be run at least daily.

Well that’s not hard…

So my suggestions below are based on the following assumptions:

That you’ve got SQL installed on your server with SQL Agent running – this was something that seemed to be the culprit in a lot of the issues in the links above.

We depend on SQL Agent to run our automation, so it was running but the process/job/scheduler to run the needed code wasn’t there at all.  The below instructions fix that.

So I created a SQL job, and scheduled it to run once daily. Since the stored procedures are in different databases, I just wrote the execution commands (below) fully qualified, so you could do the same.

I also created some output files on the jobs just to be sure I could monitor what the jobs were doing for the first little bit, and guess what?

It worked.

Problem solved.

So – if you’re experiencing the issues described above and don’t have a job scheduled on your Lync SQL Server, do this:

  1. Create a SQL job on the SQL server that has your QoEMetrics and LcsCDR databases on it.
  2. Give the job a name that makes sense and fits your job naming conventions..
    1. I named mine: Lync Reporting Monitoring Dashboard Summary Numbers
    2. Put something like the below in the description field so that once the braincells you’re now using to solve this problem have been overwritten, you’ll still have a clue as to why you did this:
      1. LYNC – Error appears in reporting when tables haven’t been populated frequently enough. This code was missing and it is confirmed that it needed to be run daily with MSFT. It is scheduled as such. Questions? Contact <you or your SQL operations team>
    3. Click on ‘steps’
    4. Click’new’
    5. Add one step – you’ll have to name it… I named mine: RTC Generate Summary Tables – because that’s what it does.
    6. I leave the database set to master and paste the following code in.

–this code should be run daily per MSFT

EXEC      QoEMetrics.dbo.RtcGenerateSummaryTables


EXEC      LcsCDR.dbo.RtcGenerateSummaryTables


  1. If you want an output file, find your log drive and paste this in there (editing the <drivepath> below as appropriate):
    1. <drivepath>\MSSQL\Log\LyncPopulateSummaryTables_$(ESCAPE_SQUOTE(JOBID))_$(ESCAPE_SQUOTE(STEPID))_$(ESCAPE_SQUOTE(STRTDT))_$(ESCAPE_SQUOTE(STRTTM)).txt (that’s a little snippet from some of the best code I’ve seen at
  2. I scheduled mine to run at some hour when I’m asleep – and it now takes about 12 seconds to run daily.  You may want to adjust the schedule as needed for your environment
  3. Do that, and you should be able to forget about that report, and your Lync team should be able to know that it’s there every day – whenever they need it.

Take care – and good luck.


Leave a comment

Posted by on September 15, 2014 in Uncategorized


Tags: , , , , , , ,

Communication, Snapshots, and Chickens (no, really)

I saw a little note the other day about “snapshots” – which reminded me of a situation we had at work awhile back.

It seems that one of the things that’s really helpful at work is being on the same page as your colleagues/coworkers.

And the way you do that is by communicating and understanding each other – and the fact that we often use different words to mean the same thing – or sometimes, we use the same words to mean different things, can present a problem.

Allow me to explain – and of course, I’ll do it with a very non-technical story…

A number of years ago, my mom was at a church social event where they had this icebreaker kind of activity, and one of the things they were supposed to do in this one was to form groups, and they were all handed cards with the name of a farm animal on it, and they had to make the sounds of these animals, and all of the like ‘animals’ were supposed to find each other, and gather together in groups.

Mom’s group was chickens.

Chickens are chickens, right?

Because chickens – or – roosters anyway, go cock-a-doodle-doo, right?

Well… If you grew up in America, roosters go cock-a-doodle-doo.

So there were a bunch of middle aged ladies, walking around this room, flapping their arms and sounding just like a barnyard. (okay, I just checked with her – they weren’t flapping their arms, but that image is too fun to let go… so with apologies to mom, I’ll let that burn in for a moment… J )

There were cows, horses, pigs – and chickens, well, roosters.

There were cock-a-doodle-doo roosters, and then there was this one gickerigeek rooster, and –


What the heck was a gickerigeek rooster?

Well, it turns out that if you’re a chicken (well, rooster) in Germany, you go ‘gickerigeek’.

You don’t go ‘cock-a-doodle-doo’.

And because of that, all of the animals who were looking for each other, found each other.

Except this one little forlorn German chicken (well, rooster), running around the room, flapping her arms (okay, not really), making the most plaintive ‘gickerigeek’ you’ve ever heard.  Come to think of it, it’s likely the only ‘gickerigeek’ you’ve ever heard.  But the thing was, as accurate as this sound was in describing a rooster’s sound, it was a sound that no one recognized.

Eventually this got someone’s attention – and suddenly there was this entire barnyard full of little old ladies interrogating a very accurate, very fun loving, and yet, very stubborn little old lady (my mom).

They asked her what was up with this whole gickerigeek thing, and the truth came out.  It became clear to them that there are different words to mean the same thing, it just depends on where you come from, and from there on out, they knew that the sound that a rooster made in the morning was heard as ‘gickerigeek’ by some, and as ‘cock-a-doodle-doo’ by others.

I ran into something like this at work the other day, where the same word was being used to mean two radically different things.  There was this rather heavy duty discussion about snapshot backups and databases – and my take was that they were absolutely not a valid backup solution… I’m thinking of it from a SQL perspective.

The fellow I was talking to was the guy who runs our SAN – and he was thinking of the word ‘snapshot’ from a totally different perspective, that of the SAN itself. Used that way, the way he was doing it, it was indeed a valid backup solution.  Not what I would have liked, but valid nonetheless.

Problem was, we were both hearing the same sound, but those working on the hardware end of things were essentially talking English, and thinking ‘cock-a-doodle-doo, while I, working in SQL, was hearing it in German, thinking that sound only meant ‘gickerigeek’.

Interestingly, it turns out that we were both right, but it took the digital equivalent of me running around the room, flapping my arms going ‘gickerigeek’ for quite some time before we were able to clear it up.

The end result was that everyone learned why, when we were doing our hourly full snapshot backups through the SAN, and while everything else looked right, the transaction log kept getting full.  The thought was that the log file shouldn’t grow, but it did, to the point of filling up a good percentage of the drive.  Some config changes, a lot of learning and understanding, and we were ready to go, problem solved.

Moral of the story? Well, just like the rooster my mom was hearing, it was so important to discover and understand that the “rooster” we were hearing really didn’t sound the same to everyone.  All the technical smarts in the world won’t solve your problems if you can’t get on the same page, and eventually we did. It was good to have it cleared up, and it saved us hundreds of gigs of drive space as a result.

H/T to David Klee (T|B) for the spark to write this, which included a link to the technical explanation in more detail.


Posted by on January 9, 2014 in Uncategorized


Tags: , ,

Error 42d, SQL, and which kind of “Software”?

The other day we had a clustered server freak out on us.  On a four node cluster, one instance appeared to be randomly failing over constantly, never staying in one spot long enough to really do anything.  It was maddening, it was frustrating, and it was really hard to even catch up to it before it moved to another node. It also housed the database for a fairly important application.

Eventually I got the instance locked down long enough to get it to just sit still, and was able to look at the logs.

The weird thing was, while I was intently looking at the logs, I also found my mind wandering off in directions that I wouldn’t have expected – at least at that time in the morning, and with the pressure on so much – I mean, the server was just plain down and wouldn’t start.  Something was really weird, there was more than a little urgency to get things fixed, and yet my mind was wandering into places it just shouldn’t have been going right then.

Okay, Focus…

Let’s see what happen – and there again… I’m looking at problems software is causing, and ironically, it was – oh, how to put this delicately – another kind of ‘software’ that had my mind wandering.

And then I saw it – and I saw what my subconscious mind was trying to tell me… That the strange error I was seeing was a 42d.

Hmm… SQL would start, appear to run, I’d see a few lines in the errorlog – then boom, it’d failover, the one constant was that whole distracting 42d thing…

Hmm… I did some checking, and found that 42d is the hex equivalent of a logon failure.

What, so SQL can’t log on to the network itself?

No, wait, the Service Account can’t log on.

That’s a network account – and on a hunch I checked to see if for some reason that account was locked out – and sure enough, it was.

My colleagues over in AD land unlocked the account, I fired up SQL, and all was happy.


Obviously, your mileage may vary, you might be facing a totally different issue, but if you find yourself thinking about software that has nothing to do with computers, or a double barreled slingshot about the time you’re trying to troubleshoot a server down, take a look at the SQL errorlog and check with your friends over in AD (that would be ‘Active Directory’) land  to see if that service account is locked out.

If it is, either unlock it or have your AD people unlock it, and you should be all set.

So remember, 42d can apply to two different types of software… It’ll be up to you to know which one to use where.


Posted by on March 20, 2013 in Uncategorized


Tags: , , , , , ,

Big Data, Tank Engines, and Digital Junk Drawers

The other day I had to do a backup of my computer – we’d had a power spike that took out the surge protectors, my backup drive, my son’s power supply, and his main hard drive.  In 20 years, we’d never had power go out, so this was a first, and had us wanting to make sure we didn’t have to go through that again.

It was a “not fun” few days of buying new hardware, rebuilding one machine, buying UPS’s – and fixing the backup drive, but we did it, and as is often the case with these things – it got me thinking.  My computer is like a digital attic – stuff gets stored there and sometimes referenced, but honestly, often forgotten.

I thought a little more about that – and remember in one place we lived as I was growing up – there was a garage full of stuff…

I remember thinking of it as a garage full of treasures.  An old army barracks my dad owned for a while came chock full of old radios, tools, black electric fans with wire cages, a huge pile of boards that had made up the side of a couple of Northern Pacific Railways boxcars that had last carried a load of 40,000 pounds of bananas in 1929 (a little piece of paper to that effect was still tacked to one of the boards when we found it).  That ended up being two walls of my room when I was growing up,

My grampa, on the other hand, had not just a garage full, but an entire barn full of treasures – one of which was an olive drab, unused, hunk of metal, that when you looked more closely at it and did some research, was a flathead V-8 engine made by Cadillac for small tanks in World War II. (like this one).  I’m sure it was plentiful in its time – but today? It was rare, but rare doesn’t necessarily mean valuable, and being in a barn, you had to go through a lot of crap to find the treasures.  And the thing was – he’d collected so much stuff – treasures in their own time – that some of it, while still functional and serviceable, had gone completely out of date and become obsolete while it was being stored in that barn waiting to be used again.

For years after Grampa passed on, my uncle tried to get rid of that tank engine – and people kept saying how valuable it must be, but no one would take it.   Finally, he said to one interested looking fellow,

“How much will you give me for it?”

“Well, um, I don’t know….”


“What? It’s got to be worth more than that.”

“Okay, but will you pay me $50.00 for it?”

And the guy tried to back out a bit.

“A dollar? Would you pay a dollar for it?”

And of course, the fellow wouldn’t – so this extremely rare Cadillac Tank Engine wasn’t worth a dollar, because really, something is only worth as much as someone will pay for it, right?

Some time later, I remember my dad and I looking at a cluttered attic with totally different eyes.  Again, I saw treasures, relics of a bygone era, while he was sizing up how long it would take to clean the place out.  He pondered a bit, took a deep breath, and reminisced a little bit, remembering that as a kid, he’d visited an old man who had an attic like this, full of “treasures” – and the old man said to dad, “Son, it’s just stuff…”

All I saw was treasures, at the time, but he was right.

It was just stuff.

Going back to my uncle for a moment – He and I had talked about kind of a lifecycle of “stuff” – where at first  you’re willing to trade something you consider valuable for it, and initially, this “stuff” gives to you… It could be something that saves you time, or makes you money, or brings you happiness or comfort, but it gives and you get something because you have it.

Eventually it just becomes part of your life, and it’s pretty much been there as long as you can remember, but at some point, it stops giving, and the balance shifts, ever so slightly, and this what has given you so much over its lifetime begins to take.  This goes for stuff and for things, and sometimes people and relationships in your life, and it’s a signal that it’s time to move on, or let go.  Eventually, the shift is more pronounced, and just the simple act of keeping “the stuff” starts costing more money, more time, more energy, than you get out of it.  But you’re used to having it, so you hold onto it.

And it costs more.

And I kept thinking…

In fact, I took a step back, mentally, and realized as I was sitting there configuring the UPS’s I’d bought for my computers, backing up tens of thousands of photos, and I realized that in some ways, the shift, like the photography I’d learned years ago, was making the transition from analog to digital, that my computer was full of ones and zeroes, and it was costing money to keep them.

As data professionals, we talk about how important it is to keep our data safe, and the fact is, it is important, but are we keeping too much? Just like I wondered sometimes whether it was really important for my grampa to be keeping some of the things in his barn, Is it important to keep every digital picture I ever took?  If I keep them, I have to manage them, I have to make sure they’re usable, right?

Here, let me throw a digital monkey wrench into the mix.  You’ve all got digital cameras out there now, right? How do you handle it when you have upgrades of image processing software?

The reason I ask is that a number of years ago, Microsoft made a product called ‘Picture It’ – which, for its time, was pretty good, but the problem is, none of the software that came afterwards would open the files created by this product.  So now, because I have upgraded the computer and the operating system and Picture It won’t run on the new one, I have hundreds of pictures with a .mix extension that I can’t open at all unless I find a copy of Picture it 5.0.

And, apparently, our old Windows 95 box. (it’s in the basement somewhere)

That would cost me time.


A number of years ago I bought a family tree program and put a bunch of pictures in it – with all sorts of metadata in the pictures – where they were taken, and so on.  Understand these were slides and prints that had been scanned, there was no GPS data embedded in the images at all.  I couldn’t upgrade to the next version, and found that all the work I’d put into researching and getting information about the pictures that are part of my family tree – simple metadata about the pictures – was now useless – I couldn’t transfer it anywhere unless I bought the next version of the software.


That would cost me money.

And now – it brought me full circle, as I was sitting there, computers hooked into the UPS systems, backup drive slowly being filled up by backed up ones and zeroes.

It had cost me both time and money.

It had me asking a lot of questions, like, “When is it important to let something go?”  As I was sitting there – looking around, I not only realized that I had thousands of images, some of which I hadn’t seen in years, that that needed to be backed up, but also realized that my computer had turned into a digital junk drawer.

I know I keep lots of email far longer than I need to.  I have piles of CD’s I’ve forgotten about.  Heck, I have piles of floppies even – and I don’t have a machine that has a floppy drive in it anymore…


How many of you out there could raise your hand to that one?

Dragging myself away from piles of floppies, CD’s, and the two Pentium boxes I finally got rid of the other day, I find myself thinking about the stuff we do at work.

We have stuff that we have to keep for legal reasons, which means boxes have to run in isolation on outdated software, but we have to keep them that way, we can’t upgrade them.  At least that way the data is readable, and accessible. There have been situations where people got rid of tapes of very important data only to discover that they had racks and racks of tapes they couldn’t read anymore.  We keep gathering data, we keep making more databases.  They keep growing.  I know poor database design makes some of the databases I administer and manage daily get bigger – the growth chart of one of them looks like the flight path of a homesick angel, and it is seriously causing us some trouble.

At the moment, that particular app is under discussion, but the thought of wanting to keep all the data we get, in case we need it someday (words I heard growing up many times) – is a little overwhelming.

But how do we know when that someday is?

I know digital storage, like real storage, initially, is cheap – but does it count the machines that need to handle the backups? The people to maintain them? The backups themselves? The offsite storage? How much will it cost us to manage what we had, at the expense of what we have?

I don’t have all the answers yet, in fact, I’m still struggling with a lot of it myself, but this whole concept of “Big data” – it makes me wonder when, eventually, someone’s going to have the arduous task cleaning out the digital attic…


Posted by on January 9, 2013 in Uncategorized


Tags: , ,


Get every new post delivered to your Inbox.

Join 459 other followers