June 18, 2008 at 2:22 pm
SQL2005 sp2
I've set up a trace to write to a centralized location. I've granted the necessary permissions to the SQL service account to the target location and the trace file does get created and written to. However, the file does not inherit the permissions associated with the folder it's being written to.
I created a job that writes a output log to that same location and that files inherits permissions correctly. I've also manually created a file using the service account and that also inherits permissions.
Is there something special about how trace files are written?
June 18, 2008 at 3:13 pm
Giorgio Maglia (6/18/2008)
SQL2005 sp2I've set up a trace to write to a centralized location. I've granted the necessary permissions to the SQL service account to the target location and the trace file does get created and written to. However, the file does not inherit the permissions associated with the folder it's being written to.
Do you get the same issues if you run the service account under your login?
June 18, 2008 at 5:12 pm
This is a prod server. I can't change the service account. I did notice that the default trace files don't inherit from the LOG folder. Is this a 2005 securtiy enhancement?
June 19, 2008 at 1:19 pm
June 20, 2008 at 5:03 am
Thanks for the reply. Are your default trace files exhibiting the same behavior? Any thoughts as to what in windows securtiy could be causing this? Policy?
June 26, 2008 at 9:01 pm
June 26, 2008 at 9:57 pm
[font="Verdana"]Hi,
In SQL 2005 when you run a trace in background, a new trace will be created and the permission for this trace file is set only to SQL Service account only and it won't inherit the permission from folder.
You can create a job to copy that trace file to some other folder (where you have privilege) then the privileges will be inherited to the trace files also.[/font]
Regards..Vidhya Sagar
SQL-Articles
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply