Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server Auditing - Part 1


SQL Server Auditing - Part 1

Author
Message
K. Brian Kelley
K. Brian Kelley
Keeper of the Duck
Keeper of the Duck (7.4K reputation)

Group: Moderators
Points: 7432 Visits: 1917
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/bkelley/sqlserverauditingpart1.asp

K. Brian Kelley
@‌kbriankelley
cppwiz
cppwiz
SSC Veteran
SSC Veteran (210 reputation)SSC Veteran (210 reputation)SSC Veteran (210 reputation)SSC Veteran (210 reputation)SSC Veteran (210 reputation)SSC Veteran (210 reputation)SSC Veteran (210 reputation)SSC Veteran (210 reputation)

Group: General Forum Members
Points: 210 Visits: 470
Excellent article - well done. I especially liked the screen prints with the red outline showing the important part of the display. I'm looking forward to Part Two...



hoo-t
hoo-t
Right there with Babe
Right there with Babe (765 reputation)Right there with Babe (765 reputation)Right there with Babe (765 reputation)Right there with Babe (765 reputation)Right there with Babe (765 reputation)Right there with Babe (765 reputation)Right there with Babe (765 reputation)Right there with Babe (765 reputation)

Group: General Forum Members
Points: 765 Visits: 19

Not an hour before I read this article, I was staring at a script in query analyzer, trying to figure out how I was going to import the current SQL error log into my table. The script has been staring back at me for a couple of days. After reading this article, I'm back on track! Thanks for a great article!

Steve





K. Brian Kelley
K. Brian Kelley
Keeper of the Duck
Keeper of the Duck (7.4K reputation)

Group: Moderators
Points: 7432 Visits: 1917
Glad that snippet of code was helpful.

K. Brian Kelley
@‌kbriankelley
Mike Schmidt
Mike Schmidt
Grasshopper
Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)

Group: General Forum Members
Points: 15 Visits: 83
Thank you -- well written.


Regards,

Mike
Emelie Clarin
Emelie Clarin
Grasshopper
Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)

Group: General Forum Members
Points: 11 Visits: 2
Thank you for this article. Very timely since I am right now creating a document that includes sql server auditing.
jacob sebastian
jacob sebastian
Mr or Mrs. 500
Mr or Mrs. 500 (588 reputation)Mr or Mrs. 500 (588 reputation)Mr or Mrs. 500 (588 reputation)Mr or Mrs. 500 (588 reputation)Mr or Mrs. 500 (588 reputation)Mr or Mrs. 500 (588 reputation)Mr or Mrs. 500 (588 reputation)Mr or Mrs. 500 (588 reputation)

Group: General Forum Members
Points: 588 Visits: 2523

Very helpful information!



.
scout
scout
Old Hand
Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)

Group: General Forum Members
Points: 322 Visits: 8

Hi.

Only a little humble suggestion: to read/write configuration settings into the Windows Registry, Enterprise Manager uses xp_instance_regread and xp_instance_regwrite, that are the same as xp_regread and xp_regwrite, except already focused on the actual instance...

For those who want to SQL for the current instance, they are easier to use.

Note: You can profile (SQL Profiler) the activity of E.M.

Bye,

Daniele.





Hans Birndaila
Hans Birndaila
Grasshopper
Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)

Group: General Forum Members
Points: 20 Visits: 1
Hi.

This is my first post to this forum, so please excuse me if I'm doing wrong.
And excuse my poor english, I am german.

First of all great thanks for your article. Been great help...
and sounding a good idea, so I added some more code and I'd ike to share the results with you.

1st: I used exactly the code provided in the article for creating the base table, only renaming the table from #errorlog to sk_errorlog according to our programming rules.

2nd: I built a second table as follows:

------------tbl-----------------

CREATE TABLE [sk_errorlog2] (
[rowID] [int] IDENTITY (1, 1) NOT NULL ,
[datum] [varchar] (10) COLLATE Latin1_General_CI_AS NULL , -- datum is german for date
[textRow] [varchar] (4000) COLLATE Latin1_General_CI_AS NULL ,
[uhrzeit] [varchar] (10) COLLATE Latin1_General_CI_AS NULL , -- uhrzeit is german for time
[kategorie] [varchar] (100) COLLATE Latin1_General_CI_AS NULL -- same for category
) ON [PRIMARY]
GO

--------------------------------

I will add colums like "servername" or similar later on when using it for multiple servers.
This table is meant to be a permanent depository for all sql-logs in my environment (only 5 sql-servers here)

3rd: I created some sp's for updating the second table
here is the first for inserting new rows:

----------------------SP1-----------------------
CREATE PROCEDURE [dbo].[sp_sk_errorlog]

AS

insert into sk_errorlog2 (textrow)
(
select

RTRIM(a.textrow) + COALESCE (b.textrow,'') as textrow

FROM
(
SELECT
*
FROM
sk_errorlog
WHERE
continuationrow=0
) as A

LEFT OUTER JOIN

(
SELECT
*
FROM
sk_errorlog
WHERE
continuationrow=1
) as B
ON
A.rowID = B.rowID - 1


where ( RTRIM(a.textrow) + COALESCE (b.textrow,'')
not in (select textrow from sk_errorlog2)
and a.continuationrow=0
)

)
GO
-------------------------------------------------------



the second sp will separate some values from the textrow:

-----------------sp2-------------------------
CREATE PROCEDURE [dbo].[sp_sk_errorlog_update]

AS
-----Check your collation/datetime settings here!-----
update sk_errorlog2 set datum =
(
select (case when (left (textrow,2) = '20') then left (textrow,10)
else null end)
)
,

uhrzeit =(
case ( right (left (textrow,12),1) )
when '0' then right ((left (textrow,19)),8)
when '1' then right ((left (textrow,19)),8)
when '2' then right ((left (textrow,19)),8)
else null
end
)
,
kategorie =(
case
----check for language settings here, e.g.: fehler is german for error!
----Here you can put the messages into categories, I started with the following
when textrow like '%[F,f]ehler%' or textrow like '[F,f]ehler%' then 'error'
when textrow like '%backup%' and textrow like '%datenbankprotokoll%' then 'protokoll'
when textrow like '%backup%' then 'backup'
when textrow like '%server%' then 'server'
when textrow like '%logon%' then 'logon'
else 'sonstiges'
end
)
where datum is null
----------------------------------------


/*
NOTE: the following 3 MS standard entries are the only ones without datetime information ( at least here :-)

May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

*/


So now you should have some information in a better queryable form than directly from xp_readerrorlog.

Now use the gui you like best for creating some "management dashboard" where you can list the events separated by time and category.

Looking foward to part 2 and

Keep on coding!

SK
Wayne West
Wayne West
SSCommitted
SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)

Group: General Forum Members
Points: 1672 Visits: 3694
Very cool, I definitely need to implement this. I have two servers that go through a ridiculous amount of logins every day, so this will be good to help monitor them more effectively.

I've also taken to forcing the error log to cycle every two weeks, syncing with our pay period. At 11:59pm Sunday night, I have a scheduled job that runs a sp_cycle_errorlog to keep the logs a bit more tidy.


Thanks!

-----
Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search