When disk I/O is no longer a problem, it comes to CPU and network I/O... To reduce the CPU load (and disk I/O) you could e.g. tune your queries /...

Even after several minutes of thinking, I can't really anything I know about indexing flag as only nice-to-have. Ok, maybe you could just skip the whole in-memory-table stuff with its...

theoretical you could have added one more file to the filegroup and used

DBCC SHRINKFILE (N'<original file>' , EMPTYFILE)

to move all data into the new files (will be evenly distributed in...

When your 500 GB database would use multiple filegroups (and the bigger tables are ideally partitioned into different FGs too), then you would be able to do a partial restore...

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 6 years 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 6 years, 5 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...