SQL Server 2012开发者指南：从入门到高级

5星 · 超过95%的资源需积分: 9 112 浏览量更新于2024-07-26 2 收藏 16.25MB PDF 举报

《入门SQL Server 2012 for Developers, 第3版》是一本由Apress出版的专业教程，专为那些希望成为数据库开发人员或已经在这一领域起步的人设计。该书旨在提供全面的指导，帮助读者掌握Microsoft SQL Server 2012的核心技术和最佳实践。本书结构清晰，内容涵盖了SQL Server 2012开发过程中的各个关键环节，从安装与概述开始，逐步深入到数据库的设计、创建、管理和维护。作者以实用的角度出发，确保读者能够理解和应用这些技术。在第一部分（第1章），读者会学习SQL Server 2012的基本介绍和安装流程，以便对系统有初步认识。随后的章节（第2章）介绍了SQL Server Management Studio (SSMS)，这是管理和操作数据库的重要工具。第3章至第15章着重于数据库的构建和管理，包括数据库设计原则、创建和组织数据表（第5章）、索引的创建与数据库建模（第6章）、数据安全与合规性（第4章）、事务处理（第9章）、数据的插入、删除与更新（第10章）、视图的构建（第11章）、存储过程、函数和权限管理（第12章）、有效编码基础（第13章）、高级T-SQL语言及调试技巧（第14章）以及触发器的应用（第15章）。在第16章，作者探讨了如何通过编程语言（如C#、VB.NET等）与SQL Server进行连接，这对于将SQL Server集成到实际项目中的开发者来说至关重要。最后，附录提供了详尽的索引，方便读者快速查找特定主题。本书不仅适合初学者系统地学习SQL Server 2012，也适合有一定经验的开发者查阅和提升技能。《Beginning SQL Server 2012 for Developers》是一本实用且全面的教程，它不仅传授理论知识，还提供了实际操作的示例，帮助读者迅速掌握并应用于开发实践中。随着技术的不断发展，尽管SQL Server 2012已不再是最新的版本，但书中介绍的基本概念和技能对于理解后续版本仍具有参考价值。

CHAPTER 1  OVERVIEW AND INSTALLATION

• Reporting Services: There are three different features for this service. One feature is

installed for each SQL Server instance, and then two options are installed once

and can be used by any installed instance on the server. Reporting Services allows

reports to be produced from SQL Server instead of using third-party tools such as

Crystal Reports. It is used by both SQL Server and Analysis Services.

• Data Quality Client: This is the client tool that allows you or users to inspect the

data within your database for data quality. You can inspect your data for

duplication and quality from a reference database using the client tool to inspect

the results.

• SQL Server Data Tools: When you want to analyze data using analysis-based

services, then you can use this GUI to interact with your database. This used to be

called Business Intelligence Development Studio.

• Client Tools Connectivity: Some of these tools sit on the client machine and

provide the graphical interface to SQL Server, while others sit on the client and

work with SQL Server via tools such as Visual Studio, Excel, third-party tools and

utilities such as iSQL, and a basic command prompt tool. Client Tools

Connectivity is the option you would package up for rollout to developers to sit on

their machines.

• Integration Services: This is a very powerful tool as it allows you to build packages

of processes to complete actions, such as importing data from other data sources

and manipulating the data. You will see Integration Services in action in Chapter 7

when you look at building a backup maintenance plan.

• Client Tools Backwards Compatibility: Previous versions of SQL Server used

different tools and methods to access data from the client tools. This option will

install these tools so that if you are accessing—as an example—Integration

Services on a SQL Server 2005 database that was called DTS, then you will be able

to do this.

• Client Tools SDK: This is a software development kit for client tools that Microsoft

uses.

• Documentation Components: This is the help system. If you need more

information, clarification, or extra detail on any area of SQL Server, then this is the

area to turn to.

• Management Tools: The basic option will install the components required for this

book. There will be a graphical interface called Management Studio as well as the

ability to write SQL at the command prompt. The complete option expands

Management Studio to have the ability to interact with Reporting Services and

Integration Services, as well as installing tools to help in performance monitoring

of your SQL Server. You would tend to deploy the complete set to developers and

the basic set to those dedicated to supporting a system, who need only to run

queries against your data to solve production problems, and to retrieve and

execute ad hoc queries.

• Distributed Replay Controller: Distributed replay allows for workloads to be

distributed over one or more clients to try to simulate a real-life workload on SQL

Server. This option is the controller of the replay.

CHAPTER 1  OVERVIEW AND INSTALLATION

• Distributed Replay Client: This is the client software that would be used on one or

more clients to send through a distributed replay of SQL Server actions to the

controller. You would install this on each client that you want to partake in the

replay.

• SQL Client Connectivity SDK: SQL Native Client provides the ability to connect to

SQL Server with some limitation to the functionality available from development

systems. In general, from .NET and other similar languages, you would connect to

SQL Server using the SQL Server ADO.NET library. If you are accessing SQL Server

from a COM-based language such as the C or C++ programming languages, then

you would look to install this option.

• Master Data Services (MDS): If you have multiple servers used within your

organization for different data repositories, for example, one database for clients,

one database for orders, another database for delivery information, then by using

MDS you can bring the data together in one master data hub. Each of the

databases has a valid use in its own right and does belong as a separate entity;

however, an organization’s management or decision-makers may need to see the

whole picture to assess how the company is performing.

Of these components, Replication, Full-Text Searching, Analysis Services, SQL Server Data Tools,

and Master Data Services fall outside the scope of this book, and I touch upon Integration Services only

as mentioned.

 Note At this point, SQL Server no longer has the option to install the sample databases. You can download the

samples from www.codeplex.com/SqlServerSamples.

Naming the Instance

After a final check that nothing will block the installation via the Install Rules check, you are ready to

start defining the the options selected earlier.

It is possible to install SQL Server more than once on one computer. This could happen when you

have a powerful server and it has enough resources such as memory and processor to cope with two or

three different applications running. ISPs will have this setup when you request SQL Server, as this is

their and your cheapest option and allows SQL Server to be easily maintained by them. These different

applications may be required to have their own SQL Server databases. Each install is called an instance.

You are now at the stage that you can name the instance of the install. Each instance must have a unique

name attached to it, although “no name,” known as a default instance, is also classified as a unique

name.

Naming instances is important as the first step to organizing your environments. For example, you

may have an instance for development, another instance for system testing, and finally one for user

testing. It is bad practice to share production server hardware with anything but production databases. If

you share your hardware, and if you have a rogue development action that occurs and crashes the

server, you will stop production from running. Although you would have to make this decision at the

start of the install process you are currently going through, it is a useful second reminder here when

naming the instance to give some indication of what environment it is for. I tend to use DEV1, STG1,

CHAPTER 1  OVERVIEW AND INSTALLATION

ability to run services with no user-based account logged in to Windows is the behavior that is required

for SQL Server. SQL Server needs to use a system-based Windows account.

Nothing can run on Windows without having some sort of login. If you do log in to the computer

with your Windows account while working through this book, you can use this Windows user ID for SQL

Server to also log in and start the required services. However, if you have your SQL Server running on a

separate machine such as a server in a specialized server room, at your client’s location, or at your ISP,

then you will not be around to log on to that machine every time SQL Server is required. In that

situation, it is necessary to use a Windows service account, which is similar to how your virus checker

runs without being logged in with your own account.

Each built-in service account has special rights and privileges within Windows, and therefore

choosing the correct service account for the correct SQL Server service is important. If you are on a

network domain, not normally found in the home environment, then it is possible for the domain

administrator to create domain accounts that can be used as service accounts, and this is the option to

choose when there is a network domain. For the moment, although not the best option within a

production environment, you will use the built-in service accounts. In a networked environment, it is

best to create new service accounts for SQL Server.

You will look at service accounts in more detail toward the end of the chapter. The options you see

in Figure 1-7 will install SQL Server with a low-level set of privileges, and Figure 1-7 also shows more

services than you would see if you chose the options in Figure 1-5. The extra services are included if you

did choose more options to install.

You can always change which accounts are used to run SQL Server later. You will notice that SQL

Server Browser service is disabled. If you install SQL Server on a remote computer such as a server, then

you may opt to enable this service so that client computers can search and browse for your SQL Server

installation rather than having to know the exact computer name and instance. ISPs are unlikely to

switch this service on, as they will give any users the SQL Server server name; however, corporations are

likely to have this service running so that you can find SQL Server instances within the network. For the

book, switch this service to automatically start.

Click Next to continue with the install.

剩余713页未读，继续阅读

rettychen

粉丝: 1
资源: 21

SQL Server 2012开发者指南：从入门到高级

Apress Beginning SQL Server 2012 for Developers 3rd Edition

Murach’s SQL Server 2012 for Developers .part1

Beginning SQL Server 2008 for Developers

Beginning SQL Server 2008 for Developers.pdf

Beginning SQL Server 2008 for Developers From Novice to Professional

Apress - Beginning SQL Server 2008 for Developers (Jul 2008)

Apress - Beginning Sql Server 2005 For Developers {From Novice To Professional

Beginning SQL Server for Developers

Murach’s SQL Server 2012 for Developers. part2

apress.Beginning.SQL.Server.2012.for.Developers.3rd.Edition.May.2012

最新资源