ARTIST(ArtistID, LastName, FirstName, Gender, YearofBirth, Address, PhoneNumber, Email, ArtistType)
NEWSITEM(NewsItemID, Source, Content)
ARTISTNEWS(ArtistID, NewsItemID, Date)
ArtistID references ARTIST(ArtistID)
NewsItemID references NEWSITEM(NewsItemID)
CONTRACTEDARTIST(ArtistID, AManagerID)
ArtistID references ARTIST(ArtistID)
AManagerID references ARTISTMANAGER(AManagerID)
SAMPLE(SampleID, SampleContent, ArtistID)
ArtistID references ARTIST(ArtistID)
PROSPECTIVEARTIST(ArtistID)
ArtistID references ARTIST(ArtistID)
RECOMMENDATION(RecommendationID, Summary, QualityEvaluation, Original, ReceivedDate, CreatedDate, ArtistID, SourceID)
ArtistID references PROSPECTIVEARTIST(ArtistID)
SourceID references SOURCE(SourceID)
SOURCE(SourceID, Name, Type, Quality)
ARTISTCOMMITMENT(ACommitmentID, StartDate, StartTime, EndDate, EndTime, ArtistID, CommitmentType)
ArtistID references CONTRACTEDARTIST(ArtistID)
PERSONALC(ACommitmentID, Firmness)
ACommitmentID references ARTCOMMITMENT(ACommitmentID)
PERFORMANCERELATEDC(ACommitmentID, Category, EventID)
ACommitmentID references ARTCOMMITMENT(ACommitmentID)
EventID references EVENT(EventID)
CONTRACT(ContractID, StartDate, EndDate, RoyaltyPercentage, Terms, ArtistID)
ArtistID references CONTRACTEDARTIST(ArtistID)
EXPENSE(ExpenseID, Description, Amount, AccountNbr, ExpenseType)
ARTMGREXPENSE(ExpenseID, AManagerID)
ExpenseID references EXPENSE(ExpenseID)
AManagerID references ARTISTMANAGER(AManagerID)
ARTISTEXPENSE(ExpenseID, ArtistID)
ExpenseID references EXPENSE(ExpenseID)
ArtistID references CONTRACTEDARTIST(ArtistID)
ARTISTMANAGER(AManagerID, LastName, FirstName)
ADMIN(AdminID, LastName, FirstName, AManagerID)
AManagerID references ARTISTMANAGER(AManagerID)
ARTISTPAYMENT(APaymentID, Date, Amount, AdminID, ArtistID)
AdminID references ADMIN(AdminID)
ArtistID references CONTRACTEDARTIST(ArtistID)
VENUE(VenueID, Name, Address, Country)
CUSTOMER(CustomerID, Name, Address)
CUSTOMERPAYMENT(CPaymentID, Date, Amount, CustomerID)
CustomerID references CUSTOMER(CustomerID)
EVENT(EventID, EventDescription, Date, Time, VenueID, CustomerID)
VenueID references VENUE(VenueID)
CustomerID references CUSTOMER(CustomerID)
AGREEMENT(AgreementNbr, Date, GrossAmount, AtSourceTaxWithheld, Terms, EventID, ContractID)
EventID references EVENT(EventID)
ContractID references CONTRACT(ContractID)
INVOICE(InvoiceNbr, Date, Total)
INVOICEPAYMENT(InvoiceNbr, PaymentID, Amount)
InvoiceNbr references INVOICE(InvoiceNbr)
PaymentID references CUSTOMERPAYMENT(CPaymentID)
SELECT LastName, FirstName
FROM Artist a
WHERE ArtistID = ……. ;
Answer is as follows :
As we know that Index in SQL are used to speed up searching in database.
So for given query, the WHERE clause is used on unique attribute of table Artist i.e. Artist_Id.
So in this case we should not have any duplicate value in that column, so that the searching get easy.
According to Primary key values, we should use Cluster indexing method because it efficiently working on key values or non-duplicate values.
So Cluster Index with unique attribute column is used for such purpose. In case of cluster index B Tree searching is used.
if there is any query please ask in comments..
ARTIST(ArtistID, LastName, FirstName, Gender, YearofBirth, Address, PhoneNumber, Email, ArtistType) NEWSITEM(NewsItemID, Source, Content) ARTISTNEWS(ArtistID, NewsItemID, Date) ...
Write an SQL query against the Chinook Database v1.4. Each query
must run successfully using DB Browser for SQLite. Create the exact
query below. Must use sub query. I saw that a
similar solution for this question used IF and CONCAT functions
which do not work and return errors. If it is possible to use the
CASE function in place of IF that would be greatly appreciated.
Also I really hate to ask but if it could be organized neatly...
This is about database system. Thank you.
Question B1 Create a Crow's Foot ERD with the business rules described below. Write all appropriate connectivities and cardinalities in the ERD. A music store would like to develop a database to manage information about the CDs, or vinyl collection, the customers and transactions information. It stores the relationships between artists, albums, tracks, customers and transactions. Here is the list of requirements for the database: The collection consists of albums. An album is...