SQL Server 2008 displays data it should not

StackOverflow https://stackoverflow.com/questions/11152546

Question

I have a really strange problem with SQL Server 2008. We have an e-commerce cart ASPDOTNETSTOREFRONT and we set the product category to UNPUBLISHED(via the carts admin section), and in the database record is set as 0 which is correct.

We refresh the page and the category is gone from the webpage.

All day yesterday the category wasnt showing and then today the category is now showing in the page and in the admin section and database its set to un-published. It makes no logical sense whats so ever!

The server has a C:\ is 25GB and only has 100MB free space! and the OS is loaded onto it with SQL Server but the websites are hosted on the D:\ which has 500GB of free space.

What can i do to investigate this further? (Please migrate this if its in the wrong stack website but i think programmers would maybe experiance something similar so might have a solution)

Was it helpful?

Solution 2

The problem was because the XML package entity.grid.xml.config didnt contain the following:

<xsl:choose>                      
<xsl:when test="Published=1">
<xsl:call-template name="SubCatCell">
<xsl:with-param name="scName" select="$scName" />
</xsl:call-template>
</xsl:when>

The sub category is now checking if its published, if it IS, then show it.

OTHER TIPS

The categories of the products disappeared most likely because you set those products as unpublished. In regards to the website not viewing the updates in real-time, this is the weird stuff with ASP.Net, sometimes saving the web.config file without making any changes to it, updates the website cache and views the changes.. I know, it's weird. Otherwise, you may need to press reset cache button in the storefront admin.

I would use SQL Profiler to check what sql queries are run by the ASP.Net application. If sql server is actually returning data that it should not, then investigate data in the tables. If SQL server is not returning the data, but it is displayed, then the problem is with cache somewhere: either with storefront or with your browser.

It is most probably happens due to the caching feature in IIS, server or browser if it is a web-app. You basically, need to make your checks in severeal places:

  • By querying the database, where new record creation may still reference values from front-end application
  • Caching in client and server sides
  • Use SQL profiler and Fiddler for web-application
Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top