Search:

Just Google "SQL Server Table Indexing" there is lots of information on the subject.

In a hospital setting, you are going to accumulate a lot of records over time, you should create indexes on the table columns that you use a lot in joins and in your where clauses to improve query...

Then my reccomendations stand. I would create an insert trigger on the customer table that on insert, creates a record in the orders table using the primary key value from the newly created customer...

Normally, the way these things work is...

Customer logs in - during the authentication you go to the database and get the customer information.

Customer wants to create a new order - you use...

First, I would recommend that you have a primary key column on all of your tables. This allows for deeper nested referencing as I demonstrated above and also primary keys are automatically created...

The way this is normally accomplished is using Foreign Key constraints in the database e.g.

Customers
customerID: (generated by database as primary key identity)
Name: Mr. Random
Pass:...