After all these years of using Quest LiteSpeed for my backups in my InfoWorld lab, I've made the decision to switch to Hyperbac Well, after all these years of using Quest LiteSpeed for my backups in my InfoWorld lab, I’ve made the decision to switch to Hyperbac. I just don’t need the centralized repository in my lab, and I do enough demos that having native SQL syntax for my backups is worth something to me. So LiteSpeed is out and Hyperbac is in.So far I’m loving it too. All of my backup files are smaller than they were with LiteSpeed and it’s a nice, robust tool. For those of you who don’t know anything about Hyperbac you can watch my video on the topic. The video is actually about a really cool extra piece of functionality that you get with Hyperbac. You can compress BCP both out of and into the DB without having to manually manage the operation. Hyperbac just compresses it and decompresses it without any management from you.There used to be a day when LiteSpeed was the only one I would consider for my DB backups. Now, with the team being more corporate, and a LOT less responsive than they used to be, Hyperbac is a good choice for me now. I’ve never gone more than just a couple hrs without getting a reply from the Hyperbac guys. You might say I’m enjoying the same access to that team that I used to get with the LiteSpeed guys. I really think LiteSpeed has fallen into the Quest cloud and it’s almost impossible to get through it. Even knowing any of the devs is hard these days, and getting anyone to make any changes is next to impossible. I thought that when Quest spun off the SQL Server business unit that they would be more agile and respond to things quicker, but that hasn’t proven to be the case… at least not to me anyway. From here they seem just as bloated and out of touch with their users as everyone else at Quest. It’s just a shame. Anyway though… if you haven’t seen Hyperbac go check it out. You won’t be sorry. Databases