User-1940569877 posted
thanks Terry, i appreciate the response.
i had already read the thread you reference in my research. i had also enabled ODS caching to test the property and it did indeed stop the double SELECT.
however, i have inherited a poorly engineered application and server memory is already burdened enough (session state); so this is not a fix for me.
there's also still no explanation as to why the ODS is SELECTing twice. i don't agree with your statement "you don't need to worry about the performance issue." my demonstration clearly shows the DB getting hit twice. if this page is requested
10,000 times a day, the DB is getting hit 20,000 times - for no reason.