Home Forums SQL Server 2005 T-SQL (SS2K5) "Ambiguous column name" error in one environment, not the other. RE: "Ambiguous column name" error in one environment, not the other.

  • July 29, 2015 at 10:47 am

    #1815811

    armoredeagle (7/29/2015)

    I have seen the same type of error and I agree that basically the reason is that the column INSPTYPE is specified explicitly and is also include in the *.

    I don’t know that Select * is the best way to code the query in production but one simple way to avoid the error is to change the order by to

    Order by 1

    And that version of the ORDER BY has been deprecated.