Editorials

Data Breaches and Lawsuits

New Show Posted – Watch Here
SQLonCall: Manager or Leader? Where do you find good managers, how do you help them get started, etc. We take a look at the pros and cons of technical vs non-technical managers and a lot more.

> Watch The Show Here

SQL Connections: Orlando, FL
Looking for the best in-person conference for learning about SQL Server, how to administer and manage it? Check out SQL Server Connections in Orlando Florida. They’ll have a huge assortment of advanced, technical sessions that will get you the help you need. SSWUG will have a track of speakers as well, talking about lessons-learned in the field and a lot more. Check it out here.

TJX Class Action Lawsuit
I’ll be talking about this more on tomorrow’s show, but in case you missed it, you need to know about this. I noticed in the papers on Sunday that there is a class-action lawsuit being filed against TJX. These are the folks that had the very large data breach at a significant number of locations – information was compromised, data was stolen, etc. I’m not downplaying what happened, but the summary of the issues is readily available elsewhere.

What caught my attention is the fact that a class action lawsuit is being filed for a data breach case in the first place. If the company was negligent, didn’t do things it knew about and should have been doing, yep, they need to be accountable. If not, I’m not so sure. But, even THAT’s not the point of this editorial.

The real point here is that it’s getting, and going to continue to get, more important than ever to make sure you’re taking good care of your systems. Security, access, controls, analysis tools, recovery tools and procedures – all of these are critical and need to be considered in your work with databases. If you’re looking for budget rationalization from the boss for the tools you need, consider showing them the information about the class action lawsuits for data loss. I think that might help free up some funds.

Be conscious of best practices, sure. But more than that, understand the best practices and guidelines – understand the issues they’re trying to resolve and try to take a step back and consider other things that may be just as influenced. For example, if you’re trying to encrypt your database connections between your web server and the database server, but you also have other devices talking to your database, it should set off a red flag that *those* connections should also be encrypted, protected and secure.

Take time to stop, think and set a plan of action that is a comprehensive as you can make it. Then review it again later to see what you may have overlooked.

Featured White Paper(s)
10 Steps to a Successful Modernization Project, Legacy Database or Application Upgrade
The goal of a modernization project is to transform aging applications to more-modern architectures while preserving the busi… (read more)

Troubleshooting SQL 2005 – Opening a Database Administrator’s Toolbox
This white paper guides you through troubleshooting using some of SQL 2005’s built-in features to diagnose issues with your d… (read more)