I have enabled SQL tracing in my Load test Run Settings. I can successfully connect to the data source. The problem is with the SQL Trace Directory. I have created a share on a separate machine that both the SQL server to be traced and my local machine (running the load test) have access to. When I attempt to run the load test, I always get an error stating "Error occurred running test. (Computer localmachine) The trace file could not be created in the specified directory (L:\LoadTest). Make sure the directory exists and is writable by the SQL Server installation to be traced". Drive L: is mapped to both the local and SQL server machines and contains a LoadTest directory.
Any ideas on how to fix the problem
Is it related to "SQL privileges needed to perform SQL tracing" (which I read from this page - http://msdn.microsoft.com/vstudio/teamsystem/reference/technotes/testing/adv_features.aspx) and if so how do I setup the SQL privileges
How do I get SQL Tracing to work in a Load test.
JinMaster
Sean,
Yes, this worked
, the trace data was successfully created when I used a local directory on the SQL server being profiled.
Thanks for the reply.
Colin.
Will Colbert
Colin,
Please try the following. Change the trace directory to be a local directory on the SQL Sever machine than you are profiling. The main reason that the controller or vs machine needs access to the trace file is to delete it. So if you choose a local directory and it works, then you would just start accumulating trace files.
Please try this out and let me know it it works.