SQL Server 2005+ users should take a look at this. It looks very promisiing.
Described as: “It would have been killer if you had recognized exactly which rows and columns were in play… and you have no ability to see what’s happening in real-time other than firing up ol’ SQL Server Management Studio and attempting to run queries before and after every action in your app. Now there is a better way.”
The best part is that it does all this WITHOUT polling and open db connections, but using SQL Server’s own in-built ability to report these changes.
What does this mean? Well, on your app, you can run action X, and see what SQL Server reports back as to the changes in the db as a result. No more manually querying tables, etc.
It looks very promising. I’ll be playing with it in the next few days, but wanted people to get a heads up as well. Let me know if you like it.
Check it @ http://lab.arc90.com/2009/02/sqlwatcher_adhoc_database_chan.php.
Arc90's New Tool: SQLWatcher
February 5, 2009
Comments on: "Arc90's New Tool: SQLWatcher" (1)
You can also use SQL Server’s OUTPUT clause in your queries for debugging. The OUTPUT clause, when used with an UPDATE, INSERT, OR DELETE will return the rows affected by the operation as a query result. It works very easily too:
DELETE FROM Table1
OUTPUT deleted.*
WHERE Value1 > 1
Personally, I find this method *extremely* useful for debugging.
http://technet.microsoft.com/en-us/library/ms177564.aspx