I totally get it. We just interviewed a guy for a Principal Database Engineer who couldn't answer correctly the first question to explain the different type of JOINs. I...

Yeah, I gave up looking for actual questions on the forums.

I hear you. It is, in some ways, but not a lot, easier, but only in the short term. In the longer term, sooner or later, someone is going to...

You can literally do anything you want, any way you want to store information.

However, I always recommend that people think about reporting and searching. Is it possible, sure, you may...

I'm confused. You said you had two columns, one rowversion and one you're going to update in some way, but you want to store it as it was rowversion? In...

Sorry, but what?

So you're storing it twice, once as the automated column value and another time as something updated, trigger or what not? I'd go with the varbinary then.

If you're using rowversion, use the rowversion data type. Can you use others? Sure. Why? What functionality will you get that you don't already have? What functionality will you lose?...

Sadly, there's not a hard and fast rule on this, other than, leaving it at 0 is generally a poor choice. Setting it to 1 is actively a bad choice....

Otherwise, for pointers, look up my name and "Database Lifecycle Management." There's a free e-book out there somewhere. It's a bit long in the tooth, but still pretty applicable on...

Those are usually combination of needs from the app married with knowledge of the model. Models are insanely helpful when developing. It's just that most places have gone so hard...

When you create an Azure SQL Database, you also get a "server." However, it's not a server like if you were running on hardware or a VM. It's simply a...

Wow! Someone actually designing a database. Cool!

There are modeling tools out there that can do a relational diagram. I work for Redgate and we sell this one. The core...

Think of a stairway like a short book, consisting of chapters. If you think this qualifies, go for it. Steve generally makes the final decision on this stuff, but it's...

As long as you're meeting compliance needs, sure, why not? I mean, I'd look to educate the heck out of them so they're not running wildly inefficient queries, cartesian joins...