Stored procedures aren’t always a favorite choice from developers. And, to add to the confusion, there are numerous ways that a client application can make
In addition to the SQL Server 2008 Database Infrastructure and Scalability content that Paul and I delivered for SQL Server 2008, our colleague Bob Beachemin
When SQL Server 2008 was in beta, Paul and I worked on a project to create content that would "jumpstart" folks in learning and working
In my last post: Little Bobby Tables, SQL Injection and EXECUTE AS, I wanted to highlight how to avoid SQL Injection when using EXEC. A few
OK, I know many of you have seen this before (an oldie, but a goodie!): (image from xkcd.com, with “copy and share” license described here: License)
I've always been concerned with security and I've always stressed the importance of auditing the REAL user context not just the current user (see this
DDL Triggers were a new feature of SQL Server 2005 and while seemingly simple, they are very powerful. DDL Triggers allow you to trap an
Instant Initialization is a new feature of SQL Server 2005 that is based on an NTFS feature that was added to Windows XP (and therefore
Today Michele and I were chatting about Security. She’s focused a lot on it these days and is chatting with everyone about their best practices…
After a group of RDs started chatting about stored procedures I finally felt like I could join in. Often they talk about .Net and client
With training and consulting from SQLskills, you’ll be able to solve big problems, elevate your team’s capacity, and take control of your data career.