InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comFri, 24 May 2013 03:01:07 GMT20http://www.sqlservercentral.com/Forums/Topic1399047-2893-1.aspx[quote][b]David Paskiet (12/20/2012)[/b][hr]There has to be an easier way! I am all ears and open to a better way![/quote]See the kb article referenced in the article I mentioned.Fri, 21 Dec 2012 00:37:55 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1399047-2893-1.aspxI found the issue using the checkDB function with data purity which is what caused me to post. What I could not do was identify the rows themselves in the normal fashion that i do. Instead I jumped through hoops and did the RBAR thing trying to find the actual rows. I pretty much opened the table and looked at each row (70K rows) using the GUI rather than a simple query. There has to be an easier way! I am all ears and open to a better way!Thu, 20 Dec 2012 20:13:21 GMTDavid Paskiethttp://www.sqlservercentral.com/Forums/Topic1399047-2893-1.aspxRun CheckDB with the Data_Purity option. For Resolving the error, see the section in this article on data purity errors and the kb article it links to.[url]http://www.sqlservercentral.com/articles/65804/[/url]Thu, 20 Dec 2012 12:23:39 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1399047-2893-1.aspxWhat is the datatype of the column containing the bad data?If it is not a DATE, DATETIME, DATETYPE2, or SMALLDATETIME datatype, what it the format of the data?If you really suspect database corruption, have you run DBCC CHECKDB against that database?[code="sql"]DBCC CHECKDB ( MyDatabase )WITH NO_INFOMSGS, EXTENDED_LOGICAL_CHECKS, DATA_PURITY;[/code]Thu, 20 Dec 2012 10:51:59 GMTMichael Valentine Joneshttp://www.sqlservercentral.com/Forums/Topic1399047-2893-1.aspxGuys:Some how an invalid or corrupt data ended up in the system. Presumably this happened when the database was upgraded from a legacy system. I know that in the old systems a bulk load process would allow bad dates to come in. It was a bug that was ignored by the dev team. I am trying to identify the rows in order to identify/correct the data but am having absolutely NO luck. I cant convert it nor does the isdate function work without error'ing out. Any suggestions? I am out of options.Thanks!Thu, 20 Dec 2012 10:15:29 GMTDavid Paskiet