Hi all,
I am wanting to have a look at the local procesure of an out of the box report but can't seem to locate it. I'm new to SQL and the 'backend' of things. The window type is "System Window".
Thanks in advance for you help,
Natasha
Natasha -
Often the easiest way to find what procedure is being called for a standard report is by running SQL profiler and finding it that way. Sometimes they are also included in the Tessitura Standard Reports pbl which you can download from TASK if you don't have it on your system.
HTH,
Heather
Ok thanks so much .
I logged into TASK and search everywhere for the pbl but couldn't find it anywhere. I'm not sure how to run SQL profiler but I'll try and figure it out.
Thanks again,
Hi Natasha -
Usually the .pbl is part of the general release download. If you are on version 10 you'd go to the Version Upgrade and Patches area, click in the Tessitura Version 10 General Release and look for TessituraStandardReports100.zip. You probably already have this downloaded to your system somewhere, most people will keep it in their reports folder on their Tessitura drive, I just wasn't sure what your setup looked like.
As for profiler, it's part of the SQL tools and just depends on your access to those and the SQL database. It will usually be in the SQL program folder (on your start menu) under Performance Tools. It just depends on your organization as to whether you have this - it is a standard SQL tool, but not everyone has access to them.
There's a short TCast about how to use it that I'd recommend:
http://www.tessituranetwork.com/network/Learning/Webinars%20Archive/IT/Introduction%20to%20SQL%20Server%20Profiler%20tcast.aspx
Hi Natasha,
This link provides a good overview of using SQL Profiler specifically for trapping what stored procedure an application is calling.
http://4rapiddev.com/sql-server/how-to-check-which-stored-procedures-or-sql-commands-are-running-on-sql-server/
The article above doesn't mention this, but if you are just trying to trap SQL code or a stored procedure called, then you can trim down the number of events by using the Tuning template. It's also a good idea to add a filter that just looks at the impresario database. You can also specifically filter on a specific user or SPID; however, I would suggest keeping the number of filters down while you are learning how to use it. (If you use it against a test database and there isn't much activity going on in your database, you won't need too many filters anyway.)
Another tip... Get SQL Profiler configured, but don't click Run until you are right at the point of executing the report. Once you are ready to start the report, click Run to start profiler, run the report, then pause profiler. That will make it easier looking at the results.
Also, if you have a test environment, it's better to use that environment for stuff like this just so that you do not impact the performance on your live environment.
I hope this helps!
David