We want to share a story that happened on one of our projects on New Year's Eve. The essence of the project is that it automates the work of doctors in medical institutions. During the patient's visit, the doctor records information on a dictaphone, then the audio recording is transcribed. After the transcription process - i.e. making audio recordings into text - a medical document is compiled according to relevant standards and sent back to the clinic, from which the audio recording came, where the sending doctor receives it, checks and confirms. After passing the mandatory checks, the document ...
3r3182. 3r3-31. How to start the SQL profiler trace when the problem needs to be caught from 3:00 to 3:30 in the morning? This can be done using server-side tracing, but this is extremely inconvenient. It is not difficult, but uncomfortable, and always lazy. Finally, I decided to automate this once and for all. Like this:
3r3182. Jenkins here, by the way, is completely optional and serves only as an interface to invoke the script with the necessary parameters: