Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

With a test migration from 2000 to 2008R2 Express, one function from the client application fails silently. I'd like to find out what SQL is running and why it fails.

I think I would have attacked this with the profiler in 2000 (not sure)? However this tool is absent from the Express Edition.

Is it possible to do what I want without any tool, eg just with T-SQL, and how would I go about it?

share|improve this question
Is the function wrapped in other code? – gbn Oct 12 '11 at 16:29
Yes - we don't even have the source (sorry by 'function' I meant a 'function' of the application not a db function) – Jack Douglas Oct 12 '11 at 16:31
up vote 3 down vote accepted

You'll need a profiler of some variety if the call is wrapped up.

One of:

share|improve this answer
I can't work out - is it a trial version or is it open source? – Jack Douglas Oct 12 '11 at 16:51
My mistake: I didn't say "one of". I can't comment on the 3rd party tool. – gbn Oct 12 '11 at 16:53

I believe that in SQL Server Express, just because you don't have the SQL Server Profiler application you are still able to use the Trace objects.

Please reference this to show an explanation of all the stored procs and functions that you can and need to use:

share|improve this answer
Thanks. I assume these "trace objects" are what SQL Profiler and the 3rd party equivalent uses? – Jack Douglas Oct 13 '11 at 14:58

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.