Terminology Overview of Team Edition for Database Professionals
With Visual Studio Team Edition for Database Professionals, you can create and manage your database as part of your development process alongside your source code. The following definitions explain terminology that relates to Team Edition for Database Professionals.
- Agile Methods
A family of processes that application developers use to minimize risk by developing applications in a series of short iterations that last one to four weeks. In this paradigm, the primary measure of progress is working software, instead of hours spent or tasks completed. Agile Methods emphasizes real-time communication, such as face-to-face meetings, telephone calls, and instant messaging, over written documents.
- common script
In database unit testing, one of the following scripts: TestInitialize or TestCleanup. Common scripts do not run as part of a database unit test. Instead, they run before and after tests and test runs to modify the test environment, which includes the database that is being tested.
- cross-database references
A reference to one or more objects from an object definition or script that resides in a different database. The two databases might reside on different servers. A cross-database reference is sometimes referred to as a three-part or four-part name because such references specify the names of servers (optional), databases, schemas, and objects.
- Data Definition Language (DDL)
Statements in SQL that define, instead of manipulate, data (for example, CREATE TABLE, CREATE INDEX, GRANT, and REVOKE).
- database development life cycle
A structured process that is imposed upon the development of the database portion of an application. It is essentially a subset of the software development life cycle that is specific to one or more databases in an application.
- data generation plan
A file that contains information about a particular database schema and how Data Generator will generate data for it.
- Data Manipulation Language (DML)
Statements in SQL that manipulate, instead of define, data (for example, INSERT, UPDATE, DELETE, and SELECT).
- database project
An offline representation of a database. Each database project contains the scripts that are required to deploy a new database or to update an existing database to a database server. A database project does not contain the data that resides in that database. Database projects are saved as .dbproj files.
- database object
A database component (for example, a table, index, trigger, view, key, constraint, default, rule, user-defined data type, or stored procedure in a database). Can also refer to a database.
- database refactoring
The process by which you can modify the names of database objects in such a way that all instances of those names within the database project are modified at the same time. For example, if you rename a column in a database table by using refactoring, you also update all stored procedures, views, indexes, functions, unit tests, and so on that reference the column.
- database unit test
A unit test that validates whether a certain aspect of your database is working as you expect.
- isolated development environment
A private copy of the database that is created from the database project and typically filled with data by using a data generation plan. You can use an isolated development environment to safely implement and test changes to the database schema without interfering with other development processes. After you complete your tests, you can then share your changes with rest of the team when you check your version of the schema into version control.
- model database
A database that is installed with Microsoft SQL Server and that provides the template for new user databases. SQL Server creates a database by copying in the contents of the model database and then expanding the new database to the size requested.
- post-deployment scripts
A set of zero or more user-specified database scripts that are executed in a specific order after the database deployment script is executed.
- pre-deployment scripts
A set of zero or more user-specified database scripts that are executed in a specific order before the database deployment script is executed.
- project items
The different types of objects that a database project comprises, including data generation plans, scripts, and the schema object definitions.
- RAISERROR statement
A Transact-SQL (T-SQL) statement that displays an error message and sets the @@ERROR automatic variable without changing the flow of the procedure. You can use RAISERROR statements to return test results from database unit tests.
An object or collection of database objects that contain structural information, or metadata, about a database.
The database in a particular operation that the operation does not modify. For example, if you compare your database project to the current deployment of that database with the intent of updating the deployment to match the project, the database project is considered the source for that operation.
- tabular data stream (TDS)
The internal protocol for transferring data between a client and a server that is running Microsoft SQL Server. TDS allows client and server products to communicate regardless of operating system, server release, or network transport.
The database on which an operation acts. The operation might or might not modify the target, depending on the type of operation. For example, if you compare your database project to the current deployment of that database with the intent of updating the deployment to match the project, the deployed database is considered the target for that operation.
- test condition
In a database unit test, a set of frequently used validation functions that test whether a unit test returns the expected results. A test condition analyzes the execution results of a unit test and determines, based on its parameters, whether the results met the criterion of the test condition.
- test script
A defined requirement that is checked against a product and that yields either a pass or a fail result. A pass result indicates that the requirement was met, and a fail result indicates that the requirement was not met.