This courses also exists in English Click-here
Demande d'informations
Microsoft SQL Server 2005(Les descriptifs suivants sont en anglais, mais les cours peuvent être
donnés en anglais ou en français)
Enterprise Data Management
In today's connected world, data and the systems that manage that data must
always be secure yet available to users. With SQL Server 2005, users and IT
professionals across your organization will benefit from reduced application
downtime, increased scalability and performance, and tight yet flexible security
controls. SQL Server 2005 also includes many new and improved capabilities to
help make your IT staff more productive. SQL Server 2005 includes key
enhancements to enterprise data management in the following areas:
| • |
Manageability
|
| • |
Availability
|
| • |
Scalability
|
| • |
Security
|
Manageability
SQL Server 2005 makes it simpler and easier to deploy, manage, and optimize
enterprise data and analytical applications. As an enterprise data management
platform, it provides a single management console that enables data
administrators anywhere in your organization to monitor, manage, and tune all of
the databases and associated services across your enterprise. It provides an
extensible management infrastructure that can be easily programmed by using SQL
Management Objects, enabling users to customize and extend their management
environment and independent software vendors (ISVs) to build additional tools
and functionality to further extend the capabilities that come out of the box.
SQL Server Management Studio
SQL Server 2005 simplifies management by providing one integrated management
console to monitor and manage the SQL Server relational database, as well as
Integration Services, Analysis Services, Reporting Services, Notification
Services, and SQL Server Mobile Edition across large numbers of distributed
servers and databases. Database administrators can perform several tasks at the
same time, such as authoring and executing a query, viewing server objects,
managing an object, monitoring system activity, and viewing online help. SQL
Server Management Studio hosts a development environment for authoring, editing,
and managing scripts and stored procedures using Transact-SQL, Multidimensional
Expressions, XML for Analysis, and SQL Server Mobile Edition. Management Studio
is readily integrated with source control. Management Studio also hosts tools
for scheduling SQL Server Agent jobs and managing maintenance plans to automate
daily maintenance and operation tasks. The integration of management and
authoring in a single tool coupled with the ability to manage all types of
servers provides enhanced productivity for database administrators.
SQL Server 2005 exposes more than 70 new measures of internal database
performance and resource usage, ranging from memory, locking, and scheduling to
transactions and network and disk I/O. These dynamic management views (DMVs)
provide greater transparency and visibility into the database and a powerful
infrastructure for proactive monitoring of database health and performance.
SQL Management Objects
SQL Management Objects (SMO) is a new set of programming objects that exposes
all of the management functionality of the SQL Server database. In fact,
Management Studio was built with SQL Management Objects. SMO is implemented as a
Microsoft .NET Framework assembly. You can use SMO to automate common SQL Server
administrative tasks, such as programmatically retrieving configuration
settings, creating new databases, applying Transact-SQL scripts, creating SQL
Server Agent jobs, and scheduling backups. The SMO object model is a more
secure, reliable, and scalable replacement for Distributed Management Objects
(DMO), which was included with earlier versions of SQL Server.
Availability
Investments in high-availability technologies, additional backup and restore
capabilities, and replication enhancements enable enterprises to build and
deploy highly available applications. Innovative high-availability features such
as database mirroring, failover clustering, database snapshots, and enhanced
online operations will minimize downtime and help to ensure that critical
enterprise systems remain accessible. This section reviews these enhancements in
greater detail.
Database Mirroring
Database mirroring allows continuous streaming of the transaction log from a
source server to a single destination server. In the event of a failure of the
primary system, applications can immediately reconnect to the database on the
secondary server. The secondary instance detects failure of the primary server
within seconds and accepts database connections immediately. Database mirroring
works on standard server hardware and requires no special storage or
controllers. Figure 1 shows the basic configuration of database mirroring.
Figure 1 Basic Configuration of Database Mirroring
Failover Clustering
Failover clustering is a high-availability solution that exploits Microsoft
Windows Clustering Services to create fault-tolerant virtual servers that
provide fast failover in the event of a database server failure. In SQL Server
2005, support for failover clustering has been extended to SQL Server Analysis
Services, Notification Services, and SQL Server replication. The maximum number
of cluster nodes has been increased to eight. SQL Server failover clustering is
now a complete fault-tolerant server solution.
|
Automatic failover
|
Yes
|
Yes
|
|
Transparent client redirection
|
Yes, auto-redirect
|
Yes, reconnect to same IP
|
|
Impact on overall throughput
|
Minimal to no impact
|
No impact
|
|
Zero work loss
|
Yes
|
Yes
|
|
Requires certified hardware
|
No
|
Yes
|
|
Provides redundant data
|
Yes
|
No
|
Database Snapshots
SQL Server 2005 introduces the ability for database administrators to create
instant, read-only views of a database. This database snapshot provides a stable
view without the time or storage overhead of creating a complete copy of the
database. As the primary database diverges from the snapshot, the snapshot adds
its own copy of pages as they are modified. As a result, the snapshot may be
used to quickly recover from an accidental change to a database by simply
reapplying the original pages from the snapshot to the primary database.
Fast Recovery
SQL Server 2005 improves the availability of SQL Server databases with a new
and faster recovery option. Users can reconnect to a recovering database after
the transaction log has been rolled forward. Earlier versions of SQL Server
required users to wait until incomplete transactions had rolled back, even if
the users did not need to access the affected parts of the database.
Dedicated Administrator Connection
SQL Server 2005 introduces a dedicated administrator connection (DAC) to
access a running server even if the server is not responding or is otherwise
unavailable. This enables you to execute diagnostic functions or Transact-SQL
statements so you can troubleshoot problems on a server. The connection is
activated by members of the sysadmin fixed server role and is only available
through the SQLCMD command prompt tool either locally or from a remote computer.
Online Operations (Index Operations and Restore)
The ability to create, rebuild, or drop an index online is an enhanced
feature of SQL Server 2005 that augments the indexing capabilities of earlier
versions of SQL Server. The online index option allows concurrent modifications
(updates, deletes, and inserts) to the underlying table or clustered index data
and any associated indexes during index data definition language (DDL)
execution. With support for online index operations, you can add indexes without
interfering with access to tables or other existing indexes. Additionally, the
server workload allows index operations to take advantage of parallel
processing. SQL Server 2005 also introduces the ability to perform a restore
operation while an instance of SQL Server is running. Online restoration
capabilities improve the availability of SQL Server because only the data that
is being restored is unavailable. The rest of the database remains online and
available. Earlier versions of SQL Server require that you bring a database
offline before you restore the database.
Replication
Replication is designed to increase data availability by distributing the
data across multiple database servers. Availability is increased by allowing
applications to scale out the SQL Server read workload across databases. SQL
Server 2005 offers enhanced replication using a new peer-to-peer model that
provides a new topology in which databases can be synchronized transactionally
with any identical peer database.
Scalability
Scalability advancements such as table partitioning, snapshot isolation, and
64-bit support enable you to build and deploy your most demanding applications
using SQL Server 2005. The partitioning of large tables and indexes
significantly enhances query performance against very large databases.
Table and Index Partitioning
Table and index partitioning eases the management of large databases by
facilitating the management of the database in smaller, more manageable chunks.
While the concept of partitioning data across tables, databases, and servers is
not new to the world of databases, SQL Server 2005 provides a new capability for
the partitioning of tables across filegroups in a database. Horizontal
partitioning allows for the division of a table into smaller groupings based on
a partitioning scheme. Table partitioning is designed for very large databases,
from hundreds of gigabytes to terabytes and beyond.
Snapshot Isolation
After data is copied, transformed, and archived to an analysis-oriented
database, it must be maintained and/or rebuilt periodically. Users certainly
benefit from looking at a transactionally consistent version of the database;
however, the version of the data that they are viewing is no longer current. It
can take many hours to build and index the data and that might not be what the
user really needs. This is where snapshot isolation is helpful. The snapshot
isolation level allows users to access the last row that was committed by using
a transactionally consistent view of the database. This new isolation level
provides the following benefits:
| • |
Increased data availability for read-only applications.
|
| • |
Nonblocking read operations allowed in an online transaction
processing (OLTP) environment.
|
| • |
Automatic mandatory conflict detection for write transactions.
|
| • |
Simplified migration of applications from Oracle to SQL Server.
|
Replication Monitor
With its intuitive user interface and wealth of data metrics, Replication
Monitor is a tool that sets a new standard for ease of use in managing complex
data replication operations.
Support for 64-bit System Itanium 2 and x64
Optimized for the Intel Itanium processor, SQL Server (64-bit) takes
advantage of advanced memory addressing capabilities for essential resources
such as buffer pools, caches, and sort heaps, reducing the need to perform
multiple I/O operations to bring data in and out of memory from disk. Greater
processing capacity without the penalties of I/O latency opens the door to new
levels of application scalability. Windows Server 2003 x64 provides high
performance for both 32-bit and 64-bit applications on the same system. The
underlying architecture is based on 64-bit extensions to the industry-standard
x86 instruction set, allowing today's 32-bit applications to run natively on x64
processors. At the same time, new 64-bit applications are executed in 64-bit
mode, which processes more data per clock cycle, allows greater access to
memory, and speeds numeric calculations. The result is a platform that takes
advantage of the existing wealth of 32-bit applications while also providing a
smooth migration path to 64-bit computing.
Security
SQL Server 2005 makes significant enhancements to the security model of the
database platform, with the intention of providing more precise and flexible
control to enable tighter security of the data. Microsoft has made a
considerable investment in a number of features to provide a high level of
security for your enterprise data including the following:
| • |
Enforcing policies for SQL Server login passwords in the
authentication space.
|
| • |
Providing for more granularity in terms of specifying permissions at
various scopes in the authorization space.
|
| • |
Allowing for the separation of owners and schemas in the security
management space.
|
|