More in Database Security

  • scary ghoul
    Oct 31, 2013
    blog

    SQL Injection: Something Really Scary 1

    As far as I'm concerned we'll likely always have SQL Injection around to haunt us. Even though this attack vector has been well-publicized and well-documented for well over a decade (and then some), failure to account for it continues to pop all the time—even in catastrophic places....More
  • Sep 30, 2013
    blog

    SQL Server Authentication on Internet Facing Servers

    If you’ve got a SQL Server that's publicly facing, make sure you've done everything you can to make it as secure as possible....More
  • Dec 18, 2012
    blog

    SQL Server and Anti-Virus

    Every once in a while, one of my SQL Server Consulting clients asks me for my opinions about running Anti-Virus on production SQL Servers. And, amazingly enough, I actually (personally feel and) argue that anti-virus really shouldn’t be run in production data centers....More
  • computer keyboard with red backup key
    Jan 2, 2012
    blog

    Off-Box Backups and Luke-Warm Standby Servers, Part III

    Just having copies of your SQL Server backups in secondary/remote locations is not a disaster recovery plan....More
  • standby button
    Dec 23, 2011
    blog

    Off-Box Backups and Luke-Warm Standby Servers – Part II 1

    Following up on my previous post, when it comes to the need to create off-box backups, there are really only two (well, three) main reasons you’d want to do Off-Box Backups: Three Primary Reasons for Off-Box Backups First: Redundancy. As I pointed out in my last post: If you’re only keeping backups and data on the same server or hardware, then you’re DOING IT WRONG....More
  • screenshot of Back Up Database - SSV3
    Dec 13, 2011
    blog

    Off-Box Backups and Luke-Warm Standby Servers – Part I

    SQL Server’s RESTORE statement is insanely powerful. Not only because of the obvious fact that it can be handy in a disaster (when you have regular backups in place), but because it’s also so incredibly versatile....More
  • Sep 30, 2011
    blog

    Staying Safe from the Coming Storm

    Hackers have been taking advantage of Graphical Processing Units (GPUs or Video Cards) for some time now to leverage their ‘massively parallel’ processing power as a way to much more efficiently attempt password cracking. To that end, it’s no surprise that hackers can use modern GPUs to generate literally billions of password ‘guesses’ per second....More
  • Boxer with red boxing gloves
    Feb 20, 2011
    blog

    Dynamic SQL vs. OPTION (RECOMPILE)

    Is it better to use OPTION (RECOMPILE) rather than dynamic SQL? Both options are likely to recompile each time, and forcing recompilation with OPTION (RECOMPILE) doesn’t have the security implications of dynamic string execution....More

From the Blogs
Jul 6, 2015
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 28: Additional Options for Tackling Jobs Failover

Throughout this series of posts I’ve taken a somewhat pessimistic view of how SQL Server Agent jobs are managed within most organizations – meaning that most of the code and examples I’ve provided up until this point were based on assumptions about how CHANGE to jobs is managed. That pessimism, to date, has come in two forms:...More
Jul 1, 2015
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 27: Options and Concerns for More Advanced Deployments

In this series of posts I’ve called out some of the concerns related to SQL Server AlwaysOn Availability Groups and their interaction with SQL Server Agent jobs – both in the form of Batch Jobs (see post #3) and backups....More
Jun 10, 2015
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 26: Using Master Servers for Job Administration

When I initially decided to write about AlwaysOn Availability Groups and SQL Server Jobs, I knew I’d have a bunch of different posts on a variety of different topics. To that end, I initially planned on this series of posts being comprised of 3 main parts:...More
SQL Server Pro Forums

Get answers to questions, share tips, and engage with the SQL Server community in our Forums.

Sponsored Introduction Continue on to (or wait seconds) ×