Business needs and human factors ought to take priority when designing keys for a table. When you take those requirements

December 27, 2018 at 11:44 am

#2017438

I find it strange that we still see articles like this discussing "primary" keys. In SQL Server in most (or all?) circumstances there is no real difference between a key...

If you want to capture data at order level then you should capture enough information to identify individual orders: an order number for example. If there are no attributes of...

Brandie Tarvin (10/30/2015)I have to disagree with the notion that a natural key is a requirement for any table. There are plenty of things in the real world (comics among...

A problem here is that Brandie has set out to describe in this article how NOT to design a database but unfortunately some people will miss the significance of that...

Hi carrieathomer,

Be assured that there's absolutely nothing wrong with your requirement. Alphanumeric identifiers are extremely common, partly because they are so much easier for humans to use than numeric-only identifiers....

It's possible to do two inserts in a single statement like this:

INSERT INTO dbo.table_b (empid, epsal)

SELECT empid, epsal

FROM

(

MERGE INTO dbo.table_a

USING...

Alexander Suprun (12/22/2014)

Are you saying that having a big composite primary key on multiple varchar columns which also has to be used in other tables for referential integrity has absolutely...

No, a "record number" / surrogate key is not necessary in all cases. Adding such a column to every table offers no general advantage in terms of performance. Surrogate keys...

You don't appear to be violating any Normal Form here....

The last word on this: www.baarf.com[/url]

Jeff Moden (10/20/2014)

I guess I don't understand the problems people are having with temporal data. Type 2 SCDs are easy to setup, implement, and use. As with certain...

One of the problems with bundling different entity types into one table is that you may have to make some compromises with integrity constraints - or incur a certain amount...

ratneshsinghparihar-1130833 (8/6/2014)

Thanks for your feedback .

My intention is not to replace the RDBMS with a no-sql database .

I put down some aspects (logs , locking , two phase commit...