bonjour ,
j'ai une trace qui enregiste dans une table et declenché à partir de sql profiler de mon instance local mais qui interroge un serveur de production ( elle trace toute les requetes de 5 users sur une base de prod). Est ce que cette trace non stop peut affectée la performance du serveur de prod svp ?
si oui comment je peut tracer l'activité de certaines personnes sans alourdir ?
Merci
I have a trace which saves in a table and is triggered from sql profiler of my local instance but which queries a production server (it traces all the requests of 5 users on a prod database). Can this non-stop trace affect the performance of the prod server please?
if so how can I trace the activity of certain people without weighing it down?
Tracing does have its overheads yes.
Depending where your running the actual trace from will depends also on the overhead.
If your running profiler locally to monitor a remote server then the overhead is not as bad to running profiler locally and monitoring locally.
But you really shouldn’t be using SQL profiler or SQL trace these days. They have both been added to the depreciated list and will be removed when Microsoft get round to it (if ever).
Use extended events instead these are much more lightweight than any trace or profiler will be.
merci pour votre retour :) justement mon profilr est chargé de mon serveur local mais interroge un serveur de production assez lourd déja !
It's only a matter of time till profiler / trace is removed so then your going to have to use extended events, so may as well make the change now.
16 People are following this question.
