SQL Server creating two records sometimes

  • Hi,
    I do not know if this is the place to post the question.
    We recently upgraded from SQL Server 2008 Enterprise to 2016 Enterprise.and from Cold Fusion 11 Enterprise to Cold Fusion 2016 Enterprise.
    When the form is submitted, the information is inserted into the database. Sometimes two records are created in the database. But the form was submitted once. This did not happen under 2008.
    The table has the identity option enabled.
    The application does not call any stored procedures or other processes.
    The non production environments are using SQL Server 2016 Standard Edition.
    Can not replicate the issue in the non production environments.

    Thanks,

    Mike

  • Setup a trace using profiler and see what's causing it.

    Alex S
  • Sounds like a Cold Fusion action upon click issue and registering multiple false entries. I believe some cold fusion upgrades are more prone to this behavior. And I think you can write more code to work around it or simply click slowly and not double pump.

    Are issue was resolved on the CF side and to not all phantom clicks/taps.

  • SQL_Chris - Wednesday, November 21, 2018 12:01 AM

    Sounds like a Cold Fusion action upon click issue and registering multiple false entries. I believe some cold fusion upgrades are more prone to this behavior. And I think you can write more code to work around it or simply click slowly and not double pump.Are issue was resolved on the CF side and to not all phantom clicks/taps.

    Code has been put in place to prevent double clicks.
    You mentioned some cold fusion upgrades are more prone to this behavior.
    Do you have any information on the cold fusion upgrades? I have not found anything.

    Mike

  • Sorry, I don’t have any specifics of a CF upgrade other than we pulled in a consultant during an upgrade a few years ago that helped refine the configuration after upgrade and point out code inefficiency that needed rewrites but again that was all CF related and not database. A sql profiler (I would rather use a server side trace/extended events) will simply confirm or prove the application is sending duplicates to the database.

    Either way I’m confident it’s an application/code issue and not a database issue.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply