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?