If you read the blog post, the hypothesis was "integers are easier...

she then concludes that these results should all but put the nail in the coffin on integers vs naturals keys.  This is NOT a valid conclusion to draw....

I hope not...

• This reply was modified 5 years, 7 months ago by  Gail Shaw.

Probably a damaged database file. It's one of the things that can go wrong when you detach a corrupt database.

Yay.

Um, so what are those points redeemable for again? 🙂

No, with the exception that the primary key is unique and your other index is not.

Other than that, they'll work identically.

Which is completely irrelevant, as neither of the queries given in the OP...

Run 1, because the index is useless. Indexes are for reducing the rows read, they have no value at all when you don't have a where clause filtering the rows.

Physical stats returns data about the physical layout of the index in the file, but the other two are memory-only and hence not included in a backup and cleared when...

Can't help you with the memory, but disabling the cores in the BIOS is not apparently sufficient to reduce licensing. Create a VM and license that, or remove cores (physically).

The...

Or use TRY-CATCH for error handling.

No need to check @@Error, no need for SET @ErrMsg = OBJECT_NAME(@@procid) (use ERROR_PROCEDURE()), no need for GOTOs

BEGIN TRY

INSERT Whatever ...

....

END TRY

BEGIN CATCH

SELECT ERROR_NUMBER(), ERROR_MESSAGE(),...

I like using sa as the database owner. Since sa already has all permissions, you can't accidentally give extra permissions by doing so. It's not escalating any privileges, it's not...

Indexes aren't going to help here, because the server is not having any problems.

System.OutOfMemoryException is a .net error. The client tool that you're running this query from is...

Logins, no. Permissions, yes, so that you can apply that script after doing the refresh.