Why analysing a hung SQLServer database helps Bible Translation

Our Executive Director sometimes tweets something like "Today I am helping the task of Bible Translation by writing papers for the board". (I can't find a recent example to embed.)

I just tweeted

Today I am helping the task of Bible Translation by analysing why a SQLServer database hung.
— Paul Morriss (@paulmorriss) October 17, 2012

Actually, I'm not doing that, but I'll tell you why at the end.

I thought I'd bridge the gap between the two parts of the sentence.

• The SQLServer database hung while I was adding a new linked database.
• The linked database connects to our worldwide personnel database.
• (Although we're an  autonomous UK charity, we work in partnership with many other organisations, many of whom are also called Wycliffe. We send people to many of those other organisations, so we need a common personnel database.)
• If you're working on Bible Translation then it's good to know who's working for you so you can look after them.

There are other links too:

• The SQLServer has our Raiser's Edge database on it. That's the system we use to keep track of donations and mailings.
• We send mailings to our supporters so they can hear about what's going on and pray for us.
• We need to keep track of who gave us money, so we can thank them and Gift Aid (where appropriate) their donations.
• We need to keep track of where the money's going to, so that it goes to the right place and so that we can keep to the legal principle that you have to give the money for the purpose with which it was given.
• Money pays for translators salaries, amongst other things, so the translation can happen.

If the database keeps on hanging then that stuff can't happen, so I need to find out why.

Actually, I'm not finding out why it hung, I'm writing a blog post about it. That's because one of the unstated (until now) reasons I write this blog is so that IT people can see how they can use their skills in Bible Translation!