SQL Server 2008, SQL Server 2005, SQL Server 2003, SQL Azure, Oracle Tutorials

Change page: < 1 2 3 4 5 6 7 8 9 10 11 > | Displaying page 9 of 11, items 241 to 270 of 308.

SQL Server 2008 R2 : Implementing Data Integrity (part 3) - Using Constraints - The PRIMARY KEY Constraint, The UNIQUE Constraint, The FOREIGN KEY Referential Integrity Constraint

The PRIMARY KEY constraint is one of the key methods for ensuring entity integrity. When this constraint is defined on a table, it ensures that every row can be uniquely identified with the primary key value(s).

SQL Server 2008 R2 : Implementing Data Integrity (part 2) - Defaults

A default provides a value for a column when a value is not supplied. Defaults can be anything that evaluates to a constant, such as a constant, built-in function, or mathematical expression. Defaults are of two types: declarative and bound. The two types are functionally the same; the difference is in how they are implemented.

SQL Server 2008 R2 : Implementing Data Integrity (part 1) - Types of Data Integrity, Enforcing Data Integrity, Rules

You can use rules as another method to enforce domain integrity. Rules are similar to CHECK constraints but have some limitations. The biggest advantage when using a rule is that one rule can be bound to multiple columns or user-defined data types.

SQL Server 2008 R2 : Using Partitioned Tables (part 3) - Switching Table Partitions

One of the great features of table partitions is that they enable you to instantly swap the contents of one partition to an empty table, the contents from a partition on one table to a partition in another table, or an entire table’s contents into another table’s empty partition.

SQL Server 2008 R2 : Using Partitioned Tables (part 2) - Creating a Partitioned Table, Adding and Dropping Table Partitions

A partition function identifies values within a table that will be compared to the column on which you partition the table. As mentioned previously, it is important that you know the distribution of the data and the specific range of values in the partitioning column before you create the partition function.

SQL Server 2008 R2 : Using Partitioned Tables (part 1) - Creating a Partition Function, Creating a Partition Scheme

SQL Server 2008 R2 : Dropping Tables, Creating Temporary Tables

A temporary table is a special type of table that is automatically deleted when it is no longer used. Temporary tables have many of the same characteristics as permanent tables and are typically used as work tables that contain intermediate results.

SQL Server 2008 R2 : Modifying Tables - Using T-SQL to Modify Tables, Using Object Explorer and the Table Designer to Modify Tables, Using Database Diagrams to Modify Tables

You often need to modify database tables after you create them. Fortunately, you can use several tools to accomplish this task. These tools are the same set of tools you can use to add, modify, and delete tables: the SSMS Object Explorer, Table Designer, Database Diagram Editor, and T-SQL. The following sections touch on each of these tools but focus most heavily on the use of T-SQL.

SQL Server 2008 R2 : Defining Table Location, Defining Table Constraints

As databases scale in size, the physical location of database objects, particularly tables and indexes, becomes crucial. Consider two tables, Authors and Titles, that are always queried together.

SQL Server 2008 R2 : Defining Columns (part 2) - Column Properties

Name and data type are the most basic properties of a column, but many other properties can be defined for a column. You do not have to specify these properties to be able to create the columns, but you can use them to further refine the type of data that can be stored within a column.

SQL Server 2008 R2 : Defining Columns (part 1) - Data Types

SQL Server 2008 has an extensive list of data types to choose from, including some that are new to SQL Server 2008. New data types include date, time, datetime2, datetimeoffset, filestream, and geometry.

SQL Server 2008 R2 : Creating Tables - Using Object Explorer to Create Tables, Using Database Diagrams to Create Tables, Using T-SQL to Create Tables

SQL Server 2008 supports the creation of tables using T-SQL, the SQL Server Management Studio (SSMS) Object Explorer and the SSMS Database Diagram Editor.

SQL Server 2008 R2 : Database Backup and Restore (part 9) - Additional Backup Considerations

If the ability to quickly recover from failure is crucial to your operation, you might consider implementing a standby server. Implementing a standby server involves backing up the production server and then restoring it to the standby server, leaving it in recovery mode.

SQL Server 2008 R2 : Database Backup and Restore (part 8) - Scenarios

Restore scenarios are as varied as the backup scenarios that drive them. The number of scenarios is directly related to the types of backups taken and frequency of those backups.

SQL Server 2008 R2 : Database Backup and Restore (part 7) - Restoring Databases and Transaction Logs

A database restore allows a database or part of a database to be recovered to a state that it was in previously. This state includes the physical structure of the database, configuration options, and data contained in the database.

SQL Server 2008 R2 : Database Backup and Restore (part 6) - Backup Scenarios

Typically, several different types of backups are used in a comprehensive backup plan. These backups are often combined to produce maximum recoverability while balancing the load on the system and amount of time to recover the database. The following backup scenarios outline some of the ways SQL Server backups are used.

SQL Server 2008 R2 : Database Backup and Restore (part 5) - Backing Up the Transaction Log

As discussed, the full and bulk-logged recovery models cause transactions to be written to the database’s transaction log. These transactions should be backed up periodically for two main reasons.

SQL Server 2008 R2 : Database Backup and Restore (part 4) - Backing Up a Database

You can create backups with SQL Server 2008 by using either the SSMS or T-SQL. Some backups are supported only through T-SQL, but the vast majority can be accomplished with either tool.

SQL Server 2008 R2 : Database Backup and Restore (part 3) - Backup Devices

A backup device is used to provide a storage destination for the database backups created with SQL Server. Backups can be written to logical or physical devices. A logical device is essentially an alias to the physical device and makes it easier to refer to the device when performing database backups.

SQL Server 2008 R2 : Database Backup and Restore (part 2) - Recovery Models

The full recovery model gives you the most protection against data loss. A database set to full recovery will have all database operations written to the transactions log. These operations include insertions, updates, and deletions, as well as any other statements that change the database.

SQL Server 2008 R2 : Database Backup and Restore (part 1) - Developing a Backup and Restore Plan, Types of Backups

Developing a solid backup and restore plan for SQL Server is one of the most critical tasks an administrator performs. Simply put, if you are a database administrator (DBA) and have a significant loss of data in a database you are responsible for, your job may be on the line.

Microsoft SQL Server 2008 R2 : Setting Up and Configuring Database Mirroring (part 5) - Monitoring a Mirrored Database Environment & Removing Mirroring

Database Mirroring Monitor allows you to monitor roles of the mirroring partnership, see the history of transactions flowing to the mirror server, see the status and speed of this transaction flow, and set thresholds to alert you if failures or other issues occur.

Microsoft SQL Server 2008 R2 : Setting Up and Configuring Database Mirroring (part 4) - Configuring Database Mirroring by Using the Wizard

After you have the endpoints created, the roles established, the connections to the endpoints granted, and the mirror database restored on the mirror server, you could easily run through the final short steps in the Database Mirroring Wizard to enable and start mirroring.

Microsoft SQL Server 2008 R2 : Setting Up and Configuring Database Mirroring (part 3) - Creating the Database on the Mirror Server & Identifying the Other Endpoints for Database Mirroring

When the endpoints are configured and roles are established, you can create the database on the mirror server and get it to the point of being able to mirror. You must first make a backup copy of the principal database .

Microsoft SQL Server 2008 R2 : Setting Up and Configuring Database Mirroring (part 2) - Creating the Endpoints & Granting Permissions

Each server instance in the database mirroring configuration must have an endpoint defined so that the other servers can communicate with it. This is sort of like a private phone line to your friends.

Microsoft SQL Server 2008 R2 : Setting Up and Configuring Database Mirroring (part 1)

Microsoft uses a few other concepts and technologies in database mirroring. You have already learned about the copy-on-write technology. Microsoft also uses endpoints, which are assigned to each server in a database mirroring configuration.

Microsoft SQL Server 2008 R2 : Database Mirroring - What Is Database Mirroring?

When you mirror a database, you are essentially asking for a complete copy of a database to be created and maintained, with as much up-to-the-second completeness as possible; you are asking for a mirror image.

SQL Injection : Code-Level Defenses - Validating Input

When performing input validation you should always ensure that the input is in its canonical (simplest) form before making any input validation decisions. This may involve decoding the input into a simpler format, or just rejecting input that isn't already in canonical format where non-canonical input isn't expected.

SQL Injection : Code-Level Defenses - Using Parameterized Statements

One of the root causes of SQL injection is the creation of SQL queries as strings that are then sent to the database for execution. This behavior, commonly known as dynamic string building or dynamic SQL, is one of the primary causes of an application being vulnerable to SQL injection.

SQL Server 2005 : Extending User-Defined Aggregates

Each of the other SQLCLR features, with the possible exception of triggers, will see more use in production applications than will aggregates, but aggregates and types are the only members of the group that can help developers do things that simply were not possible before.