tag:blogger.com,1999:blog-8951904624959546499.post6562316082381502283..comments2024-02-22T05:36:59.121-05:00Comments on Test This Blog - Eric Jacobson's Software Testing Blog: Run a SQL Trace To Look Behind The CurtainEric Jacobsonhttp://www.blogger.com/profile/08216361684596485033noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-8951904624959546499.post-10244252511689235162011-08-10T22:13:18.966-04:002011-08-10T22:13:18.966-04:00Great stuff Eric, I'm going to have to poke ar...Great stuff Eric, I'm going to have to poke around with SQL Profiler to see if that can help narrow down user data issues on some of my sites!gMasnicahttps://www.blogger.com/profile/17322470410579466327noreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-53695758713830217502011-07-29T14:16:13.374-04:002011-07-29T14:16:13.374-04:00I started using SQL Profiler today because if this...I started using SQL Profiler today because if this post. Thanks Eric!Geordie Keitthttp://tester.geordiekeitt.comnoreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-43248683253695137672011-07-27T12:31:21.610-04:002011-07-27T12:31:21.610-04:00Thanks for the corrections, idontlikegluefoo. I a...Thanks for the corrections, idontlikegluefoo. I applied most of them. <br /><br />Yes, I should hire Laura. In fact, I have an open position on my BI team. If you're interested let me know, Laura.Eric Jacobsonhttps://www.blogger.com/profile/08216361684596485033noreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-44630635452903878812011-07-26T22:22:10.670-04:002011-07-26T22:22:10.670-04:00You spelled "DB" as "BD" at th...You spelled "DB" as "BD" at the end of the 2nd paragraph. Also forgot to mention the name of the tool for tracing is called "SQL Profiler". And you also used a semicolon more than once in your post (only max of one is allowed in a post per MLA).<br /><br />I like how your name for programmers "Prog" is one character off from my real name. <br /><br />I also like Laura's comment about how she debugs as much as possible for the devs. Hire her on our team!<br /><br />Although I don't think it's necessary to do so but is much appreciated and does show a tester going over and beyond the call of duty, but I do see how doing so might be useful in certain instances to look at SQL (or any code for that matter) as you can find flaws that may lead you to think of a test that could cause the feature to fail otherwise. <br /><br />ie. if all your tests passed but then you look at the SQL and you notice an INNER JOIN to a table to lookup data to display in the grid, however said lookup data may not always be required/provided relative to the parent table being joined against. <br /><br />So the INNER JOIN would fail when the non required child record data isn't set. The fix would be to do a LEFT OUTER JOIN to allow nulls for the missing child record data, the INNER JOIN would just fail to return the parent record altogether if the child record doesn't exist. This is a common SQL join bug.idontlikegluefoonoreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-75064660624099517412011-07-26T14:40:47.043-04:002011-07-26T14:40:47.043-04:00I use SQL all the time! I always debug as much as ...I use SQL all the time! I always debug as much as possible for the devs.Laurahttps://www.blogger.com/profile/14429520970502586265noreply@blogger.com