Me too! I've been at my current position for 9 months. One major system is an access application where the database was ported to SQL 2000 about 4 years ago. The application, still within Access, is a total nightmare (currently being re-designed/rewritten in Java but won't be live for 6 months). Since I've been here, I, with direction from the user community, have developed probably 20 or so queries that are run each morning on the SQL Server Agent to trap for invalid/incomplete data. This data is ultimately retreived and presented via the web to our clients and we want to be sure our data is as accurate possible. We have probably been in violation of our SLAs for quite some time - IMO - but are slowly getting back within our obligations. Very simply, a case where business outgrew the current system capabilities and feeble, past attempts have not been 100% reliable (which has led to "out with the old, in with the new (ME!)"). The best we can do until the rewrite is complete and live is to attempt to cleanse our data and present the best end-results within our current constraints. It may not be the absolute correct approach but, short-term, it's the best we can do with what we've got. My only saving grace is that management understands and can deal with it until June, 2009.