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?

  • 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

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

One of:

| 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
  • 1
    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: http://msdn.microsoft.com/en-us/library/ms191006.aspx

| 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 clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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