dimanche 8 février 2009 09:56So the new AdventureWorks is an ultra normalized database and the concept is completely new to me and I have a question about how it would work. My understanding is the BusinessEntityID is the primary key for EVERY possible person the company deals with, and the table PERSONS.PERSONS is the table with all the actual information that is associated with a particular BusinessEntityID. Correct me if I am wrong.
My question is how is the BusinessEntityID created? Is it automatically generated when a new person is made? Or are the BusinessEntityID's premade (in this case there are 27000 or so records) and whenever a new person is made you have to assign them a BusinessEntityID that is availabe.
Toutes les réponses
lundi 9 février 2009 23:12Howdy, adamus1986. I wouldn't call it "ultra"-normalized. There are still some candidates for normalization... ;-)
BusinessEntityID is easy; it's an IDENTITY that's created when you create a new record. It was designed to showcase some of the new features of Entity Framework (such as inheritance); unfortunately, EF doesn't yet support all of SQL Server 2008's data types so we can't publish the EF samples that take advantage of the new design.
Creating a new Person.BusinessEntity is the first step in creating a new retail customer, employee, store, vendor, etc.
Does that help?