We have BAQs that work for a while, and then they start giving bad data. When can open a new baq and write it exactly as the original and get different data, but correct data. Anyone experience this before?
No, I haven’t seen this. What BAQs are you seeing these results in? Are they all custom BAQs? What kinds of data are coming back? What results do you expect and what are you getting?
define “bad data”?
2 Likes
These are custom BAQ. Some I wrote, most are form others. It really weird and intermittent. The data is right one moment, then a week or month later, its showing something way off. Rewrite it in a new BAQ, exactly the same, and get the correct data. Just weird.
@Olga “bad data” to me is data that doesn’t make sense, for my company, in the baq. In one case, the job calculated field was way off. When recreated in a new BAQ, named something different, it pulled correctly.
when you rewrite it, does the SQL version that shows on the front page look exactly the same?
I didn’t think to check that. Next time it happens, I will check and see. I am wanting to say yes, as it is built the exact same, graphically. But, you do have an excellent point.
Would a stale execution plan do this? Maybe on the next bad data issue add the option recompile to see if it saves rewriting.
Just yesterday saw an example related to @timshuwy 's comment. Wrote a very simple BAQ looking for where data was stored among a few tables, deleted one of the tables from the graphical view, and when looking at the SQL version still showed a join to the deleted table.