Schedule a trace file in SQL Profiler
-
Hello All, I am trying to schedule to run a trace file, around 12:30am to 1:00am. Our client is sending us some data, that we need to analyze. With that said, i can see we can set an "Enable Trace stop time", on the file, but not able to find an option to set the begin time? Is there a way we can do this in the SQL Profiler? Thanks!
-
Hello All, I am trying to schedule to run a trace file, around 12:30am to 1:00am. Our client is sending us some data, that we need to analyze. With that said, i can see we can set an "Enable Trace stop time", on the file, but not able to find an option to set the begin time? Is there a way we can do this in the SQL Profiler? Thanks!
Schedule Traces | Microsoft Docs[^] sp_trace_setstatus (Transact-SQL) | Microsoft Docs[^] How to create a SQL Server trace file, schedule it to run, and analyze the trace file results? | www.handsonsqlserver.com[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Hello All, I am trying to schedule to run a trace file, around 12:30am to 1:00am. Our client is sending us some data, that we need to analyze. With that said, i can see we can set an "Enable Trace stop time", on the file, but not able to find an option to set the begin time? Is there a way we can do this in the SQL Profiler? Thanks!
-
VK19 wrote:
Our client is sending us some data, that we need to analyze.
Why would you need to schedule this? Is the 'client' putting the data directly into the database?
-
Not sure that answers the question. Is the client themselves directly putting data into your database? Or do they send you 'something" (file, stream, etc) which is then processed by your (company) code and that process itself puts the data in the database? Or could be that your code is pulling something from the client, processing it, and then putting it in the database.
-
Not sure that answers the question. Is the client themselves directly putting data into your database? Or do they send you 'something" (file, stream, etc) which is then processed by your (company) code and that process itself puts the data in the database? Or could be that your code is pulling something from the client, processing it, and then putting it in the database.
-
Sorry - the second option, wherein the client sends us a file, with test cases. Apparently one test case at a time. Our company then processes this test case and inserts into our database. thanks!!
So then you can do the following 1. Keep the file 2.During the day run the same process/processes on that in a development environment. 3.Profile the applications and turn on tracing every where you can. 4. Analyze the results. 5. Update as needed based on 4 including the possibility of modify the process/processes to provide addition trace data so you can further refine and define future problems.
