Louis Davidson - Pro SQL Server Relational Database Design and Implementation
Here you can read online Louis Davidson - Pro SQL Server Relational Database Design and Implementation full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. year: 2016, publisher: Apress, genre: Romance novel. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:
Romance novel
Science fiction
Adventure
Detective
Science
History
Home and family
Prose
Art
Politics
Computer
Non-fiction
Religion
Business
Children
Humor
Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.
- Book:Pro SQL Server Relational Database Design and Implementation
- Author:
- Publisher:Apress
- Genre:
- Year:2016
- Rating:4 / 5
- Favourites:Add to favourites
- Your mark:
Pro SQL Server Relational Database Design and Implementation: summary, description and annotation
We offer to read an annotation, description, summary or preface (depends on what the author of the book "Pro SQL Server Relational Database Design and Implementation" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.
Learn effective and scalable database design techniques in a SQL Server 2016 and higher environment. This book is revised to cover in-memory online transaction processing, temporal data storage, row-level security, durability enhancements, and other design-related features that are new or changed in SQL Server 2016. Designing an effective and scalable database using SQL Server is a task requiring skills that have been around for forty years coupled with technology that is constantly changing. Pro SQL Server Relational Database Design and Implementation covers everything from design logic that business users will understand, all the way to the physical implementation of design in a SQL Server database. Grounded in best practices and a solid understanding of the underlying theory, Louis Davidson shows how to get it right in SQL Server database design and lay a solid groundwork for the future use of valuable business data. The pace of change in relational database management systems has been tremendous these past few years. Whereas in the past it was enough to think about optimizing data residing on spinning hard drives, today one also must consider solid-state storage as well as data that are constantly held in memory and never written to disk at all except as a backup. Furthermore, there is a trend toward hybrid cloud and on-premise database configurations as well a move toward preconfigured appliances. Pro SQL Server Relational Database Design and Implementation guides in the understanding of these massive changes and in their application toward sound database design. Gives a solid foundation in best practices and relational theory Covers the latest implementation features in SQL Server 2016 Helps you master in-memory OLTP and use it effectively Takes you from conceptual design to an effective, physical implementation What You Will Learn Develop conceptual models of client data using interviews and client documentation Recognize and apply common database design patterns Normalize data models to enhance scalability and the long term use of valuable data Translate conceptual models into highperforming SQL Server databases Secure and protect data integrity as part of meeting regulatory requirements Create effective indexing to speed query performance Who This Book Is For Programmers and database administrators of all types who want to use SQL Server to store data. The book is especially useful to those wanting to learn the very latest design features in SQL Server 2016, features that include an improved approach to in-memory OLTP, durability enhancements, temporal data support, and more. Chapters on fundamental concepts, the language of database modeling, SQL implementation, and of course, the normalization process, lay a solid groundwork for readers who are just entering the field of database design. More advanced chapters serve the seasoned veteran by tackling the very latest in physical implementation features that SQL Server has to offer. The book has been carefully revised to cover all the design-related features that are new in SQL Server 2016.
Louis Davidson: author's other books
Who wrote Pro SQL Server Relational Database Design and Implementation? Find out the surname, the name of the author of the book and a list of all author's works by series.
Louis Davidson
Vieira Robert
Dmitri Korotkevitch
Gethyn Ellis
Jan L. Harrington
Rachel Clements
Pro SQL Server Relational Database Design and Implementation — read online for free the complete book (whole text) full work
Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "Pro SQL Server Relational Database Design and Implementation" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.
Light
Font size:
↓
↑
Reset
Interval:
↓
↑
Bookmark:
Make
Louis Davidson 2016
Louis Davidson and Jessica Moss Pro SQL Server Relational Database Design and Implementation 10.1007/978-1-4842-1973-7_11. The Fundamentals
Louis Davidson 1 and Jessica Moss 2
(1)
Antioch, Tennessee, USA
(2)
Mechanicsville, Virginia, USA
Electronic supplementary material
The online version of this chapter (doi: 10.1007/978-1-4842-1973-7_1 ) contains supplementary material, which is available to authorized users.
Success is neither magical nor mysterious. Success is the natural consequence of consistently applying the basic fundamentals.
Jim Rohn, American entrepreneur and motivational speaker
I have a lovehate relationship with fundamentals. The easier the task seems to be, the less enjoyable I seem to find it, at least unless I already have a love for the topic at some level. In elementary school, there were fun classes, like recess and lunch for example. But when handwriting class came around, very few kids really liked it, and most of those who did just loved the taste of the pencil lead. But handwriting class was an important part of childhood educational development. Without it, you wouldnt be able to write on a white board, and without that skill, could you actually stay employed as a programmer? I know I personally am addicted to the smell of whiteboard marker, which might explain more than my vocation.
Much like handwriting was an essential skill for life, database design has its own set of skills that you need to get under your belt. While database design is not a hard skill to learn, it is not exactly a completely obvious one either. In many ways, the fact that it isnt a hard skill makes it difficult to master. Databases are being designed all of the time by people of limited understanding of what makes one good. Administrative assistants build databases using Excel, kids make inventories of their video games on a sheet of paper, and newbie programmers build databases with all sorts of database management tools, and rarely are any of the designs and implementations 100% wrong. The problem is that in almost every case the design produced is fundamentally flawed, causing future modifications to be very painful. When you are finished with this book, you should be able to design databases that reduce the effects of many of the common fundamental blunders. If a journey of a million miles starts with a single step, the first step in the process of designing quality databases is understanding why databases are designed the way they are, and this requires us to cover the fundamentals.
I know this topic may bore you, but would you drive on a bridge designed by an engineer who did not understand physics? Or would you get on a plane designed by someone who didnt understand the fundamentals of flight? Sounds quite absurd, right? So, would you want to store your important data in a database designed by someone who didnt understand the basics of database design?
The first five chapters of this book are devoted to the fundamental tasks of relational database design and preparing your mind for the task at hand: implementing a relational database. The topics wont be particularly difficult in nature, and I will do my best to keep the discussion at the laymans level, and not delve so deeply that you punch me if you pass me in the hall at the PASS Summit ( www.sqlpass.org ).
For this chapter, we will start out looking at basic background topics that are very useful.
- History : Where did all of this relational database stuff come from? In this section I will present some history, largely based on Codds 12 Rules as an explanation for why the RDBMS (Relational Database Management System) is what it is.
- Relational data structures : This section will provide introductions of some of the fundamental database objects, including the database itself, as well as tables, columns, and keys. These objects are likely familiar to you, but there are some common misunderstandings in their usage that can make the difference between a mediocre design and a high-class, professional one.
- Relationships between entities : We will briefly survey the different types of relationships that can exist between the relational data structures introduced in the relational data structures section.
- Dependencies : The concept of dependencies between values and how they shape the process of designing databases later in the book will be discussed.
- Relational programming : This section will cover the differences between procedural programming using C# or VB (Visual Basic) and relational programming using SQL (Structured Query Language).
- Database design phases : This section provides an overview of the major phases of relational database design: conceptual/logical, physical, and storage. For time and budgetary reasons, you might be tempted to skip the first database design phase and move straight to the physical implementation phase. However, skipping any or all of these phases can lead to an incomplete or incorrect design, as well as one that does not support high-performance querying and reporting.
At a minimum, this chapter on fundamentals should get us to a place where we have a set of common terms and concepts to use throughout this book when discussing and describing relational databases. Throughout my years of reading and research, Ive noticed that lack of agreed-upon terminology is one of the biggest issues in the database community. Academics have one (well, ten) set(s) of terms to mean the same thing as we people who actually develop code. Sometimes multiple different words are used to mean one concept, but worst case, one word means multiple things. Tradespeople (like myself, and probably you the reader) have their own terminology, and it is usually used very sloppily. I am not immune to sloppy terminology myself when chatting about databases, but in this book I do my best to stick to a single set of terms. Some might say that this is all semantics, and semantics arent worth arguing about, but honestly, they are the only thing worth arguing about. Agreeing to disagree is fine if two parties understand one another, but the true problems in life tend to arise when people are in complete agreement about an idea but disagree on the terms used to describe it.
Taking a Brief Jaunt Through History
No matter what country you hail from, there is, no doubt, a point in history when your nation began. In the United States, that beginning came with the Declaration of Independence, followed by the Constitution of the United States (and the ten amendments known as the Bill of Rights). These documents are deeply ingrained in the experience of any good citizen of the United States. Similarly, we have three documents that are largely considered the start of relational databases.
In 1979, Edgar F. Codd, who worked for the IBM Research Laboratory at the time, wrote a paper entitled A Relational Model of Data for Large Shared Data Banks, which was printed in Communications of the ACM (ACM is the Association for Computing Machinery [ www.acm.org ]). In this 11-page paper, Codd introduces a revolutionary idea for how to break the physical barriers of the types of databases in use at that time. Then, most database systems were very structure oriented, requiring a lot of knowledge of how the data was organized in the storage. For example, to use indexes in the database, specific choices would be made, like only indexing one key, or if multiple indexes existed, the user was required to know the name of the index to use it in a query.
As most any programmer knows, one of the fundamental tenets of good programming is to attempt low coupling of computer subsystems, and needing to know about the internal structure of the data storage was obviously counterproductive. If you wanted to change or drop an index, the software and queries that used the database would also need to be changed. The first half of Codds relational model paper introduced a set of constructs that would be the basis of what we know as a relational database. Concepts such as tables, columns, keys (primary and candidate), indexes, and even an early form of normalization are included. The second half of the paper introduced set-based logic, including joins. This paper was pretty much the database declaration of storage independence.
Light
Font size:
↓
↑
Reset
Interval:
↓
↑
Bookmark:
Make
Similar books «Pro SQL Server Relational Database Design and Implementation»
Look at similar books to Pro SQL Server Relational Database Design and Implementation. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.
Vieira Robert
Dmitri Korotkevitch
Gethyn Ellis
Jan L. Harrington
Rachel Clements
Reviews about «Pro SQL Server Relational Database Design and Implementation»
Discussion, reviews of the book Pro SQL Server Relational Database Design and Implementation and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.