Snapshot replication

• Snapshot replication takes a snapshot of current data; the snapshot is used to initialize and to replace data on a subscriber
• Create a compressed snapshot file when saving snapshots to removable media or transferring them across the network
• Compressed snapshot file must be stored in an alternate location; the file cannot be stored in the default location

Transactional replication

• Transactional replication uses transactions to distribute changes; typically used in a server-to-server environment

Replication security

• For increased security, store the snapshot folder in a UNC share on the distributor
• Encrypt the connections between replication servers
• Only grant the necessary permissions to agents
• Grant the Snapshot Agent Write permission to the snapshot folder; grant the Windows accounts for the Distribution Agent Read permission to the snapshot folder
• Server subscriptions are assigned a priority value; client subscriptions use the priority value of the publisher
• Server with highest priority value will win when conflict detections occur
• Replication Monitor is used to monitor replication between SQL servers

Improve replication performance

• By minimizing the retention period for transactions and history, they will not be stored as long on the distributor; doing this reduces the amount of disk space being used
• Set column-level tracking if bandwidth between the publisher and subscriber is limited
• Add more memory to distributor
• Use multi-processor computers

• OPENXML allows access to XML data as though it is a relational rowset
• Must call sp_xml_preparedocument before you can write queries against an XML document by using OPENXML
• Use the WITH clause to specify a schema when using OPENXML
• You can generate data in XML format by using a SELECT statement with the FOR XML argument

Implement an HTTP endpoint

• An endpoint is a service that can listen for requests
• In order for SQL Server to listen on HTTP for SOAP requests, an HTTP endpoint must first be created. Only available under Windows Server 2003 and Windows XP with SP2
• Use the CREATE ENDPOINT statement with the AS HTTP argument to create an HTTP endpoint. It creates a new Web service and defines methods exposed by the endpoint
• Make sure that endpoint connect permissions are limited to specific users and groups

Implement Service Broker components

• Must include the WITH TRUSTWORTHY ON argument when creating the database; this will allow two databases running on the
• same SQL Server to communicate
• Use the CREATE SERVICE statement to create a new service

1. A queue must be created before you can create a new service
2. The queue is used to store messages

• Use the CREATE CONTRACT statement to create a contract between two services

Import and export data from a file

• Switch to bulk-logged recovery when performing bulk operations to prevent the transaction log from running out of space or growing too large
• The bcp utility is used to perform bulk imports and exports

1. Export data from a table to a data file
2. Bulk export data from a query
3. Bulk import data from a data file into a table

• The BULK INSERT statement provides the fastest way to import data in a text file into a database table
• SSIS enables you to move data between heterogeneous systems (fx. to/from Oracle)

Reverting from snapshot

1. Both the original database and the snapshot to be restored are unavailable during the process
2. Drop database snapshots other than the one being restored by issuing the DROP DATABASE statement
3. Issue the RESTORE DATABASE statement with the FROM DATABASE_SNAPSHOT clause

Configure monitoring

• Create alerts that will fire when log shipping operations fail
• Use SSMS to specify a monitor server
• History Retention period determines how long you want to retain a record of your log shipping history
• Query history tables on the monitor server to obtain the most recent log shipping status information

• Database mirroring is a software-based solution for increasing database availability; provides instantaneous failover
• Both servers must be running the same edition of SQL Server 2005
• Mirror server hosts mirrored copy of database

1. Requires sufficient disk space for the mirrored database
2. Principal database must be restored by specifying the same database name with NORECOVERY
3. Transaction log files must also be applied by using the WITH NORECOVERY option

Create endpoints

• Each server instance can only have one database endpoint; endpoints must be created on the principal, mirror, and witness server
• Verify that an endpoint does not exist before creating one
• Use the CREATE ENDPOINT statemen

Specify database partners

• Principal server serves the database to clients
• Mirror server maintains a copy of the database and acts as a standby server
• Use the ALTER DATABASE with the SET PARTNER option to configure database partners
• A witness server is required for high-safety mode with automatic failover – it verifies whether the principal server is up and functioning

Specify a witness server

• Use the ALTER DATABASE with the SET WITNESS option to specify a witness server

Database mirroring supports two operating modes: high-safety and high-performance

High-safety mode

• Uses synchronous operations; committed transactions are committed on both servers
• This is the default mode when there is a witness server
• When a session begins, mirror server synchronizes mirror database with principal database; a committed transaction is committed on both partners once databases are synchronized
• Increase in transaction latency

High-performance mode

• Runs asynchronously
• Principal server commits transactions without waiting for mirror server to write them to disk
• Minimizes transaction latency

Configuring SQL Server to encrypt data

• Configure the database engine to use a certificate
• Set the ForceEncryption option to Yes
• Restart the server

Using IPSec to encrypt data requires no SQL administration

Authentication mode determines how users authenticate to SQL Server

Windows Authentication Mode

• Uses Kerberos security protocol
• Users connect by using their Windows user accounts
• This is the recommended authentication mode

Mixed Mode (Windows Authentication or SQL Server Authentication)

• Users connect by using their Windows user accounts or SQL logins
• Select this authentication mode if you need to support legacy applications

1. Uses SMTP to send mail to users
2. Database Mail must be enabled; this feature is disabled by default
3. Use the Database Mail Configuration Wizard to enable, configure, and manage Database Mail

Database recovery model

Full Recovery Model

• Supports transaction log backups
• Transactions in logs are not removed until they have been backed up
• Recovery can be as recent as the most recent transaction log backup or to a specific point in time

Simple Recovery Model

• Does not support transaction log backups
• Minimizes administrative overhead
• Data can only be restored from the last backup
• Changes since the most recent backup are lost

Bulk-logged

• Supports transaction log backups
• Switch to bulk-logged recovery model when performing bulk operations such as index creation
• Reduces log space consumption
• Does not support point-in-time recovery

• Use the SQL Server 2005 Upgrade Advisor to identify issues before upgrading
• SCC runs as part of the Setup utility to identify conditions that may prevent the installation of SQL Server
• Hardware requirements for Standard and Enterprise editions

1. Pentium III-compatible processor 600 MHz (1 GHz or higher recommended)
2. 512-MB RAM (1 GB or more recommended)
3. 1.6 GB disk space on the system partition

• o Software requirements

1. Supported operating system (Windows Server 2003, Windows XP Professional, Windows 2000 Server)
2. Internet Explorer 6.0 SP1 or later
3. IIS 5.0 or later (required for Reporting Services)
4. ASP.NET 2.0 (required for Reporting Services)

Upgrade to SQL Server 2005

• SP3/SP3a is required to upgrade from SQL Server 2000 to SQL Server 2005
• SP4 is required to upgrade from SQL Server 7.0
• An In-place upgrade is an automated process that upgrades the existing instance to a new instance
• A side-by-side migration installs a new instance

1. SQL Server 2005 is installed along side the previous version
2. Database is detached from old instance and reattached to new instance

Create an instance

• An .ini file can be used to automate installation
• A computer can only host one default instance; multiple named instances are supported
• The default instance name is MSSQLSERVER
• A named instance cannot contain the terms Default or MSSQLSERVER

He opens the Measure Up database and tells us to look at the answers. “Don’t mind the question”, he says, “just look at the answers. Then remove those that do not make sense or cannot be done and you’ll be very likely to have the correct answer.”

At first we are not really sure what to think. After all, we have been cramming like crazy, reading the questions for hints and loopholes, trying to remember to not get caught in clever traps – but… after a while we get it. He is right. Just read the answers… in 9 out of 10 you can actually answer correctly without reading the mile-long text before it. And in fact, if you only read the answers, you don’t get caught in traps…