I have three: 1.) Over 1 million lines of T-SQL that ran the entire application. VBScript backend that was a light wrapper around calls to the database. I was

I have three: 1.) Over 1 million lines of T-SQL that ran the entire application. VBScript backend that was a light wrapper around calls to the database. I was working on that system last year. 2.) ETL process done completely in SQL. When requirements changed instead of using existing columns they would create a new column using the same name but purposely misspelled. For example 'Member Responsibility' would be 'Member Responsability' and the original column would be ignored. 3.) Company used Entity Framework for database access. When somebody was running unit tests they ended up dropping a production database. Luckily it was a database with low volume of writes so backups were not very out of date.