ITEC 4770 – Fall 2008
Midterm review
1. Important terms from the chapters, topics discussed during class (and on the
slides), and the topics from our lab sessions will be covered on the exam. The
items that will likely have a larger focus, especially in the short answer portion,
are detailed in the list below.
2. SQL
a. I may ask you to generate some queries. These will be similar to what you
have seen in the lab.
b. You may have to create the logical layout for some database tables based
on information given. This would include things like column names,
general data types, primary and foreign keys, etc.
c. Importance of using proper table joins.
d. Know what SQL keyword should be used for table functions (e.g.
INSERT, SELECT, DELETE, UPDATE, etc.).
e. Understand what a stored procedure is as it relates to SQL statements.
What is the syntax to create one?
f. I have given some sample tables (Student Table, Stud_Course Table,
Course Table, and Semester Table) below. You may be asked how to
access or modify data in such tables. Study the relationships among (PK,
FK). How would you use the table information to access or modify data.
Maybe create a sample database yourself with this information and try out
a few queries.
g. Understand the structure of the Employee Table below.
3. VB Data Access
a. Important System.Data.SqlClient classes (SqlConnection, SqlCommand).
Where are they used? What functions are available (ExecuteNonQuery,
ExecuteScalar, ExecuteReader). What class and command would you use
to INSERT data into a table?
b. Primary keys vs. foreign keys.
c. Which namespace(s) do we use when building a Microsoft Visual Studio
application that will communicate with SQL Server 2005
d. Understand the SqlDataReader object.
e. What is Internet Information Services (IIS)?
4. Chapter 1
a. Different application architectures (# of tiers)
i. Features of each
ii. Advantages and disadvantages
iii. Compare and contrast
1. Single, Two, and Three
2. Three vs. N
iv. Effect on database access
b. User-centric vs. Data-centric business logic. What is it? What layer(s) can
you find it used in? We talked about separating logic into user-centric and
