I find the answers a little bit misleading. If a column is part of another index, FK or constraint, it just can't be dropped (without dropping / changing the index,...

CHECKSUM(*) or BINARY_CHECKSUM(*) could be an option but this needs all columns in the same order and (sometimes) equal data type.

Beside of this the function may work or a good...

Forbit them to create any table in the primary filegroup, than this...

• This reply was modified 5 years, 2 months ago by  Thomas Franz.

Nice article.

My main problem with the fill factor is, that I can't set it per partition. So I have either to waste a lot of space in my old, cold...

@Carlo: so the dot in SELECT 1.test is not a whitespace or a dot as between filename and extension, but a simple decimal separator without a following decimal number as...

Jobdescription: Well, it depends 🙂

be aware, that adding dates / times only works with the DATETIME data type but not with the new (ANSI compatible) DATETIME2 (this would cause Error 8117: Operand data type...

• This reply was modified 5 years, 7 months ago by  Thomas Franz.

Just stumbled over this old question.

A possible anwere would be: try to disable the index instead of dropping it. After the switch you have to rebuild it (may take very...

I miss one important version:
If you regularly filter for Status = 5 (and not 3 or 4 or 6 or anything else) and OrderDate BETWEEN x and y, the...

The tinyint is not your problem. Sure, after changing it to smallint, you will not receive an aritmetic overflow exception, but your data will be invalid (negative). So you only...

I think a problem with synonymes (as with several other "solutions") is SourceControl. When I use them to refer to database db_prod or db_test (depending on my environement) it will...

even in this case (breaking down to daily or even hourly costs) you can not invoice more than rounded cents. So more precisition will only prevent rounding errors, if you...

Worst data types: I've seen money values, that are usually < 100 EUR be stored in DECIMAL(38,17) columns (and many percentage columns with the same declaration too).

You should / could have mentioned that an index persists the column (but only in the index itself) too.

Persisting on the table level safes you a little...