Earn a 20% Return on Your Training Investment
If you’re looking for an easy way to manage your training budget and you want to maximize those funds, then invest in a Springhouse Training Savings Account.
It’s easy – for every $5,000 you deposit into your Springhouse account, you will receive an additional $1,000 in training credits.
That’s a 20% return on your investment! Use the funds to pay for ANY classes* taken with Springhouse (end-user, technical, open-enrollment or private).
*Terms and Conditions apply. See Web site for details.
Posted via email from Springhouse - Ready. Set. Train!
SQL Server 2008 Auditing
In an era of increasingly concern regarding regulations and their impact in the production environment, auditing is one of the most important topics. And, SQL Server 2008 introduces a new SQL Server Audit feature. This post will not cover all the details of it, but it will give you an opportunity to taste it.
In a very simple way audit is about WHAT to log and WHERE to log. So, with that in mind, let’s define the three most import audit objects in SQL Server 2008:
- Server Audit: defines WHERE the audit data should go. You can choose among file, Windows Security Log, and Windows Application Log.
- Server Audit Specification: defines WHICH server instance actions should be audited.
- Database Audit Specification: defines WHICH database actions should be audited.
Let’s do it!! In this post we will use SQL Server Management Studio to create an example, keep in mind that you can also use Transact-SQL to create these objects.
Let’s start with a new Server Audit:
- Open SQL Server Management Studio, connect to your server, and expand the Security.
- Right-click Audits and select New Audit…
- On Create Audit dialog box (figure 1) note that I have Queue delay is equals to 0, configuring the audit to be synchronous. You can leave the default value of 1000 (1000 milliseconds) for an asynchronous option and to lessen performance impact.
- Click OK.
- Right-click the new Audit object and Enable it.
Now that we know where the audit data will go, let’s create a Database Audit Specification.
- Expand the database you want to create an audit specification on.
- Expand Security and right-click New Database Audit Specification.
- Configure the Audit to be audit object created previously, and add some actions. (see figure 2)
Figure 2
- Click OK, and do not forget to enable it.
The steps to create a Server Audit Specification are almost the same.
Now that you have everything configured you can test it. And, to see the audit data you can use:
In a just few steps we created an audit solution. To know more about auditing:
- Join us @ ISACA Philadelphia Chapter this Tuesday, November 11th, 2009.
- Attended one of our classes: 6158 and 6231
- http://msdn.microsoft.com/en-us/library/dd392015.aspx
- Post an question.
