Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
SamC
White Water Yakist
3467 Posts |
 Posted - 2003-07-15 : 20:21:28
|
| I'd be interested in reading any contributions on how Profiler analysis led to a better understanding of server or database operation.Sam |
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2003-07-15 : 21:03:18
|
| I love profiler. It rocks.I use it mainly as a debugging tool, it's a fantastic way to see what is actually getting passed to SQL Server as well as a way to rerun the queries and procs to see what the output was.I also use it to track down performance problems, let a process run then go in and see what is causing you problems.Damian |
 |
|
|
SamC
White Water Yakist
3467 Posts |
Posted - 2003-07-15 : 21:41:58
|
| Damian,What kind of problems have you been able to find ?Sam |
|
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2003-07-15 : 23:06:36
|
| It makes it easy to identify any procs which are running slowly in the course of normal operation. It also allows you to see which procs are high usage. There is not a huge amount of point spending time to get a few milliseconds more out of a query that is run once a day, but if there is one that is being called constantly then it is a good candidate for tuning. This is basically how the index tuning wizard decides what to index.Essentially, it gived you a window into what your system is doing to help decide where to place your performance tuning efforts.Damian |
|
|
|
SamC
White Water Yakist
3467 Posts |
Posted - 2003-07-16 : 08:39:02
|
| Profiler shows the SQL generated by ASP and .NET ADO. Using Profiler (last last night) I was able to determine that a failing .NET procedure's ADO was correctly building a stored procedure request. I double checked the stored procedure and found an aggregated column had not been named. Profiler didn't point at the problem, but it led me to the souce in much less time than .NET.Sam |
|
|
|
setbasedisthetruepath
Used SQL Salesman
992 Posts |
Posted - 2003-07-16 : 09:59:04
|
| That's the one missing feature of ADO.NET, IMO - when using Command and Parameter objects to make a stored procedure call, you cannot view the sql statement generated.Jonathan{0} |
|
|
|
graz
Chief SQLTeam Crack Dealer
4149 Posts |
Posted - 2003-07-16 : 11:25:36
|
| I work with packaged software quite a bit. I use profiler for a couple of different activities. I use it to get a feel for how the package uses the database. When populating a page/screen does it send multiple queries or one big one? Does it use stored procedures or straight SQL? How often does it login? Does it use server side cursors?I also use it to trouble shoot particular functions or screens. What tables does it touch? How does it use them? What procedures call other procedures, etc.It's a really great way to insert yourself between the application and SQL Server and see what goes on.===============================================Creating tomorrow's legacy systems today.One crisis at a time. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-07-16 : 12:15:05
|
| I also use Profiler for debugging purposes. I also use it to see what queries aren't performing well (duration is high). I don't use the index tuning wizard that much any more, but I sometimes do just to see what it would recommend. For those applications that do not use stored procedures, there aren't that many of them but a couple do exist, I check to see whether or not they are doing SELECT * or other things that aren't recommended. I then am able to let them know what they need to change and also remind them about stored procedures.Tara |
|
|
|
|
|
|
|
|
Discussion thread on Profiler