Chapter Five, "Implementing the Base Table Structure," is the first point in the database design process in which you will start building scripts to actually build database objects. This chapter covers the building of tables. Here you have taken your logical model, examined each entity, chosen your datatypes, and implemented your unique keys.
Chapter Six, "Protecting the Integrity of Your Data," is enforcing data integrity conditions in SQL Server. This means that you have now protected your database from all the bad data that is possible. Also discussed in this chapter are the various other ways that data protection can be enforced using stored procedures and client code.
Chapter Seven, "Patterns and Query Techniques," takes you beyond the basic set of techniques for table design. This chapter covers several of the common useful patterns as well as take a look at some patterns that some people will use to make things easier to implement the interface that can be very bad for your query needs.
Chapter Eight, "Securing Access to Your Data," is a high priority for every programmer. At least it should be. In this chapter, you will learn some strategies to implement data security in your system. These include employing views, triggers, encryption, and even using SQL Server Profiler.
Chapter Nine, "Table Structure and Indexing," are an important step in building high performance systems and this chapter now examines some of the basics of how data is structured in SQL Server, as well as some strategies for indexing data for better performance.
Chapter 10, "Coding for Concurrency," shows you how to maximize resource utilization among many users. You will learn several strategies for how to implement concurrency in your data access and modification code. Part of the database design and implementation process is to step beyond the structures and in this chapter you will see how.
Chapter 11, "Considering Data Access Strategies," is explored in this chapter and you will see many of the concepts and concerns of writing code that accesses SQL Server. You will learn about ad hoc SQL versus stored procedures (including all the perils and challenges of both, such as plan parameterization, performance, effort, optional parameters, SQL injection, and so on), as well as discussing whether T-SQL or CLR objects are best, including samples of the different types of objects that can be coded using the CLR.
Article comments