SQLRockstar

Facts are facts. What you have pointed out here is that words can have different meanings (very true) and that a fallacy is not a fact (also true).

I will agree that it is the case that certain facts as we know them today may cease to be facts in the future. For example, it was once believe to be a fact that the Sun revolved around the Earth.

Thanks for reading!

That's flippin' HUGE! If the Universe is about 13b years old, then this thing is essentially as about 1/3 the age of the Universe itself.

Thanks!

Great question. I suppose that is why people just feel the need to consume more...because they don't know how much they need.

With food it is easier to measure a proper intake. That's not the same with data. As a result, business will always want more. Most internal IT departments won't be able to keep up over time. As a result, the business looks outside.

So, if you are clinging to the idea that there will always be a need for a traditional DBA, you are wrong. Our roles are changing, right before our eyes.

Nice rebuttal to my post from earlier today...

I think there is a special level of hell for people who use nested views across linked servers hundreds of miles apart and demand that the DBA team give them sub-second response times despite limitations put upon them by things like the speed of light.

...or, I could use "mvw" to designate a new type of object...

I agree, the client shouldn't care about the data being a table or a view. But as a DBA, if I need to quickly find a solution to a problem, the use of a prefix can be a benefit.

There are costs and risks for all design choices. If you are working with a system that is growing and prone to the need of denormalizing frequently then perhaps using a prefix isn't the right choice.

But not every system has that issue. I see more cases these days of smaller databases...think "one database per customer" type of architecture. Denormalization isn't an issue often, and prefixes seem to work just fine.

Only when you don't use prefixes that are somewhat standard.

At the end of the day, however, consistency is key. For example, you used a capital letter to distinguish the start of a word, making it easier for me to understand what you were saying.

Fair point. But how much time have I wasted trying to root out a performance problem caused by nested views disguising themselves as tables?

The tools have been failing us. Using a prefix is a way to get around those failings.