SQl Server log files

Question

SQl Server log files

fizzleme

SSCertifiable

Points: 6906
More actions
January 14, 2010 at 2:39 pm

#138115

I have a user who needs to read the SQL server log files. What permissions are required please? I don't want to give him the farm.
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply

Gail Shaw SSC Guru Points: 1004494 More actions · Answer 1

Which log files? Error log?

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

fizzleme SSCertifiable Points: 6906 More actions · Answer 2

Not the error log. The standard SQL log files.

When the snows fall and the white winds blow,The lone wolf dies but the pack survives.

Once you've accepted your flaws, no one can use them against you.

José.Cruz Right there with Babe Points: 722 More actions · Answer 3

Hi there,

Those log files available under "Management-> SQL Server Logs", under SSMS?

To be able to read these logs the user must be a member of the securityadmin and sysadmin role, and needs to have permission on the msdb DataBase.

José Cruz

Gail Shaw SSC Guru Points: 1004494 More actions · Answer 4

fizzleme (1/14/2010)
Not the error log. The standard SQL log files.

The 'standard SQL log file' is the error log.

Visible in SSMS, gives details on login failures, startup messages, etc. That one?

If you're thinking of something else, please be specific.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

fizzleme SSCertifiable Points: 6906 More actions · Answer 5

Yes, that error log. If I give my co-developer securityadmin rights, will that be sufficient to read the logs?

When the snows fall and the white winds blow,The lone wolf dies but the pack survives.

Once you've accepted your flaws, no one can use them against you.

fizzleme SSCertifiable Points: 6906 More actions · Answer 6

I found the answer. All that is needed is securityadmin rights.

When the snows fall and the white winds blow,The lone wolf dies but the pack survives.

Once you've accepted your flaws, no one can use them against you.

Shawn Melton SSC-Insane Points: 24675 More actions · Answer 7

fizzleme (1/21/2010)
I found the answer. All that is needed is securityadmin rights.

FYI: that role will allow them to do more than just read the logs.

Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton

SD1999 Hall of Fame Points: 3140 More actions · Answer 8

why not just create a share for D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG folder

and give him access to the phisical file that he can open with notepad

this way u don't have to give him a security admin perm which is very powerfull

fizzleme SSCertifiable Points: 6906 More actions · Answer 9

That is a reasonable idea. I will consider it.

I am also trying to find a way to give someone rights to the event viewer on windows 2003 server without local admin rights. ideas?

When the snows fall and the white winds blow,The lone wolf dies but the pack survives.

Once you've accepted your flaws, no one can use them against you.

ascottjamieson Newbie Points: 1 More actions · Answer 10

ascottjamieson

Newbie

Points: 1

January 24, 2010 at 6:35 am

#1107903

you could publish the log file in a web page

fizzleme SSCertifiable Points: 6906 More actions · Answer 11

Yes, but I don't have access to our web server.

When the snows fall and the white winds blow,The lone wolf dies but the pack survives.

Once you've accepted your flaws, no one can use them against you.