Tag: syndicated

  • The Two Day Adjustment

    I made it to Cambridge and actually feel OK. I wonder how I’ll feel tomorrow, but the two day adjustment worked well. Tuesday I woke up at 5:30, and around 4:30 Wednesday before leaving for London. I flew late in the day, a 3:00 flight to Calgary, easily cleared customs and got to my plane in 30 minutes, then an hour delay while a bathroom was being fixed on the plane. Is it me or does it seem the bathrooms regularly have problems on airplanes?

    I left around 7:30 from Calgary, flying overnight and arrived around 10:30am in London. Not fresh, but fresher than I normally am on the arrival.

  • RTO in Disaster Recovery

    When you have a disaster, the time that you have to restore service is usually referred to as the RTO time. This stands for the Recovery Time Objective and it can is defined like this in Wikipedia:

    The Recovery Time Objective (RTO) is the duration of time and a service level within which a business process must be restored after a disaster (or disruption) in order to avoid unacceptable consequences associated with a break in business continuity.

    That’s a great definition, covering the term with a great set of large, geeky words. However I came up with a simpler one that conveys the same information:

    The time it takes for you to get things running to the point where someone can use them after someone notices that they aren’t.

    You can also view the RTO as the downtime or uptime level of your system. I prefer looking at the RTO as the intervals between uptime, since I think that’s a glass half full view.

    That’s the basic definition and it’s important that you determine what the RTO is for your systems in order to begin planning for the resources that you devote to disaster recovery preparation.

    This post is based on the information in my Preparation for Disaster talk.

  • How Should We Pay People?

    It’s an interesting article on how to pay people from Dan Ariely at Business Week. It’s a look at some of the issues with paying for knowledge work, or work that isn’t well defined. The short version is that you don’t want to specify too tightly what you expect people to do, but then you have to motivate them to work in the best interests of the company.

    I think this is one of the fundamental problems in management today. We still have this mentality from the blue collar factory worker and piecemeal or easily measurable work items being applied by management to knowledge workers. It doesn’t work well, and somehow we think that the hours work in some way relate to the output.

    I blame lawyers. They tend to use this model, since they often bill by the hour. However the end result, the quality of that they produce, which is usually research, isn’t easily quantified in anything other than a win or loss. That often comes down to not only the soundness of the argument or the logic, but the charisma of the lawyer. That’s not even close to the way we do business in many other industries, especially technology.

  • Recovery Models

    In SQL Server we have three basic recovery models: full, bulk-logged, and simple. By default we find that most databases use the defaults, which mean that they are in the full recovery model.

    In that case, you need to be sure that you are performing log backups, otherwise the log will grow until it reaches it’s limits, or you run out of disk space on that drive. If the log cannot record SQL Server transactions, the database cannot accept any more transactions.

    The basics of recovery models are covered nicely in this article from Gail Shaw, which includes some common myths and misconceptions out there. However for the average person, the important thing is that you understand which recovery model to pick.

    You Need Point in Time Recovery

    Point in time recovery means recovery in between the full or differential backups. Quite a few DBAs will ask customers if they really need to recover to a point in time, and get the answer that they don’t, but that’s not often the right question to ask.

    Ask your clients if the database failed at 5:00pm today, and all the work done today was lost because you restored to last night’s backup at midnight, how would they feel?

    Sometimes they’re fine with the data loss, most times they aren’t. If you need to get back to a point in time between backups, make sure you use the full recovery model.

    You Can Reload the Database

    There are some databases, usually data warehouses, that can be rebuilt from other sources. If you take a backup of your database and then load data every day that rarely changes during the day, you might not need point in time recovery. In fact, many ETL processes are not designed for this anyway, and could not restart themselves in the middle of a load if you restored to the point in time when the database had an issue.

    In this case, use the Simple recovery model.

    You are space constrained with the log

    If you run index rebuilds, or large data loads and find yourself with a transaction log that grows very large, you might want to investigate the Bulk-logged recovery model. This model is more confusing, so I don’t want to give you a general rule here. If you think you might benefit from less logging, investigate the bulk-logged recovery model, practice restores with it and make sure you fully understand the implications of using it before you set a database in this mode.