Right - but only the checksum column is keyed. With the number of collisions in checksum I would think you would hit a point of maximum entropy in index fragmentation...

Refresh schedule availability is based on the license level of PowerBI, but it can be refreshed manually more frequently.

I would question what utility refreshing that frequently actually has for your...

I am skeptical that pre-fragmenting the index to 20% fragmentation with the 80% fill-factor is preferable to a relatively small amount of fragmentation that would result from changes to checksum...

Yeah, an active status is easy when there are only two status, but more difficult when there are multiple active and inactive status each.

Got it worked out though, little messy...

I hadn't considered that. I will definitely have duplicates of natural keys that exist in different statuses while some of the status should be able to duplicate and Active statuses...

The cluster and listeners are definitely stored in AD, you only need to join a new node for SQL to pull the configuration into itself. If you are having to...

I can only comment theoretically as I don't have access to an AAG currently, but the AAG configuration I believe is all stored in AD.

I would 100% recommend against trying...

>> ... joining hundreds of millions or billions of rows, dealing with big Cartesian products or when involving things like column store indexes. I've experienced it myself extracting data...

That got posted before I intended.

Natural keys for relational references within the DB are always bad. Natural keys can change which destroys referential integrity, they can't survive data corrections, they...

Use of natural keys for table relations will not be tolerated in my databases.

<<

Hidden from you? Like pointer chains in non-relational databases, like Total, Image, IDMS, IMS, etc.? Did you ever work with C? One of the first rules was never do pointer...

I agree that you should only store attributes as numeric types if you plan on doing math on them, but if you are using only surrogate keys as...

Interesting thought on the primary key using char. I agree that you should only store attributes as numeric types if you plan on doing math on them, but if you...

Ok I like the EntityPK name, it seems really obvious now, don't know why I didn't think of it.

There would only be one surrogate key and the one natural 'key.'...

Correct - I didn't mean to say I would be using natural keys.

Every table will have a surrogate key that no user will be allowed to see or use and...