15 Signs to Identify Bad DBA
They think it is bug in SQL Server when two NULL values compared with each other but SQL Server does not say they equal to each other.
They do not rename the trigger name thinking it will not work after it is rename.
They are looking for difference between Index Scan or Table Scan on Google.
They reinstall the SQL Server if they forget the password of SA login.
They use model database for testing their script.
They believe compiled stored procedure is production ready.
They prefix all stored procedures with ‘sp_’ to be consistent with MS naming convention.
They believe it is best to use stored procedure to move million records across database.
They index all the fields in database to improve the performance.
They believe that adding a foreign key constraint with the ‘Enforce Relationship’ checkbox unchecked is best way to apply relationships as it ensures relationships with ‘constraint errors’ while modifying the data.
They believe SELECT * is better than including all the columns name in SELECT as SQL has to read less syntax.
They believe Rules are better than Constraints and try to convert all constraints to rules.
They add new column in four steps : Create a new table, Copy all the data over, Drop the old table, Rename the new table.
They believe there is bug with SQL Server that it auto creates Clustered Index every time Primary Key is created on table.
They think this article is not funny or disagree with at least 5 of the points above.
Note: Please consider this post as humor, when I started to learn about SQL many years ago I disagreed with all of the above points.
Reference : Pinal Dave (https://blog.sqlauthority.com), Web-Article
