Featured Article(s)
Troubleshooting SQL Server 2005 Analysis Services problems (Part 1)
In this article, Alexander Chigrik explains some problems that you can have when you work with SQL Server 2005 Analysis Services. He also tells how you can resolve these problems.
Interesting Trend… Injection Forcing Looks at Other Issues
I’ve been seeing an intriguing trend of late – that of people discovering they’ve become the victim of Injection, then starting to dig into their systems to find out what else they may be missing administration/security/optimization-wise. It’s been a real wake up call for several people to-date. They started with the pretty common situation of having a departmental database that grew and became a key part of their infrastructure.
Then, along comes SQL Injection.
There are a number of different injection attack types happening right now, with more on the near horizon I’m sure. As people grow these systems, make them available on an internet site or just generally get more exposure and traffic, the injection attacks become more likely.
This isn’t about injection however, it’s about the discovery process people are going through. If this is you, yes. Start with the injection coding updates so you can be protected. While you’re in there, take a look at your maintenance plans, backups, jobs… just look around. You don’t actually have to do much – just look over security, users, jobs and such. Look to understand what’s there, and stay on top of it going forward so you can keep an eye out for issues that impact your installation. It’s the next step as an accidental DBA. 🙂
Featured White Paper(s)
Protecting Microsoft SQL Server
Although SQL Server offers options for database protection and recovery, none of them is intended to provide a complete disas… (read more)
Top Five Database Vulnerabilities Plaguing Federal Agencies
Data breaches and accidental data exposure whether due to human error, as the result of insider espionage, or attacks by hac… (read more)