Answer by Grant Fritchey
It doesn't say what version of SQL Server you're dealing with, but you could use Extended Events instead of a server-side trace. They're much more lightweight and less likely to cause issues. Any...
View ArticleAnswer by Håkan Winther
You are probably having differentiering ansi settings between the asp.net and management studio. Try to change exact_abort setting in management studio. Maybe I missunderstood the question, but if you...
View ArticleAnswer by KenJ
I'm dropping in a day late but, if you are seeing lots of UDF statements (unexpected?) within the procedure then you are likely catching the SP:StmtStarting and/or SP:StmtCompleting events within your...
View ArticleAnswer by Jeff Moden
@tomgough79 Ok... once again, I realize that I'm responding to an older thread... Folks have solved the performance issue associated with the use of SQL Profiler but what have you done to resolve the...
View ArticleAnswer by Grant Fritchey
It doesn't say what version of SQL Server you're dealing with, but you could use Extended Events instead of a server-side trace. They're much more lightweight and less likely to cause issues. Any...
View ArticleAnswer by Håkan Winther
You are probably having differentiering ansi settings between the asp.net and management studio. Try to change exact_abort setting in management studio. Maybe I missunderstood the question, but if you...
View ArticleAnswer by KenJ
I'm dropping in a day late but, if you are seeing lots of UDF statements (unexpected?) within the procedure then you are likely catching the SP:StmtStarting and/or SP:StmtCompleting events within your...
View ArticleAnswer by Jeff Moden
@tomgough79 Ok... once again, I realize that I'm responding to an older thread... Folks have solved the performance issue associated with the use of SQL Profiler but what have you done to resolve the...
View Article
