This topic explains major concepts related to using SQL Server with the Delphix Engine. For explanations of general Delphix concepts, see Glossary of Major Delphix Concepts.
General Concepts
| Term | Explanation | Synonyms |
|---|---|---|
Server | A computer system of some kind, either physical or virtual, that has an operating system and software on it. This system can run:
| Some synonyms are "location" dependent, noted below. Some apply to all hosting locations. Physical systems in a local datacenter:
Virtual systems in VMWare or another hypervisor:
Virtual system in a cloud:
|
Cluster | One or more servers that share the same data and are capable of being connected to as a highly available whole. A metaphor for this is "many doors leading to the same room": there are multiple servers leading to the same database(s) for redundancy and horizontal scaling. |
|
dSource for SQL Server | A dSource is the Delphix-side representation of a source database. Strictly speaking, it is a backup of the source database that has been compressed and stored inside of Delphix to be kept up to date over time. To add a SQL Server dSource the following need to be added: Staging Environment, Source Environment. Then a backup needs to be stored on SMB location along with Differential backups and transaction log backups if required. | |
Delphix Connector | A Windows service that enables communication between the Delphix Engine and the Windows target environment where it is installed | |
| Domain | Collective name for data objects, such as dSources, virtual databases (VDBs), users, groups, and related policies and resources | |
Environment | A Delphix environment is a pointer to a server or cluster, and the subsequent discovery of all database instances and databases. Depending on the type of server or cluster being attached and defined, an environment can be a:
| |
VDB for SQL Server | In a normal cloning operation, SQL Server Data files consisting of blocks are copied in full from one system to another using some form of backup and recovery. With Delphix, the data already exists in compressed form as a dSource. Virtual SQL Server Data files are created from snapshots and presented to the Target Environment via iSCSI. No data blocks are actually copied, allowing for near-instant cloning. |
SQL Server Concepts in Delphix
| Term | Explanation | Synonyms |
|---|---|---|
| Microsoft SQL Server | A relational database management system (RDBMS) traditionally hosted on the Microsoft Windows platform |
|
Database Discovery | Database discovery is initiated during the configuration of a Source Environment. Delphix will use a Target Environment as a proxy to find SQL Server instances and databases on the Source Database Server. Once a database has been discovered, it can be linked as a dSource. During initial discovery and environment refreshes, Delphix pushes a fresh copy of the toolkit to each host environment. Included in the toolkit are: A JRE (Java Runtime Engine), Delphix .jar files, the hostchecker utility, scripts for managing the environment and/or VDBs, and Delphix Connector log files. Delphix then executes some of these scripts to discover information about the database instance and databases. In some environments, the scripts are customized to fit your particular server configuration. | |
Database Server | A server with SQL Server installed and a SQL Server Instance, capable of hosting one or more databases | |
Instance | The software (set of memory structures) used to manipulate and manage data in the database. Typically describes a complete database environment, including the database software, user configuration, databases, and other functionality associated with the database software. | |
SQL Server Instance | An instance (see Instance) using the SQL Server software. The running SQL Server software on a Windows Server, capable of opening and running SQL Server databases. | |
SQL Server Managed Backups | Backups taken via SQL Server natively, output to a location on disk. This location must be shared via SMB with the Staging Server. | |
Standalone Windows server | A Windows Server that is not part of a Cluster. If this Server contains a SQL Server Instance, it can be connected to Delphix as a Source, Staging, or Target depending upon its purpose. | |
Validated Sync environment | ||
Validated Sync | The process used by Delphix to sync changes from a Source Database into Delphix. Based on the dSource Validated Sync Mode, Delphix will synchronize the dSource over time using full backups, differential backups, and transaction log backups. | |
Windows Target Environment | A Delphix environment pointing to a Windows Target Database Server. This is the type of environment to which you provision VDBs. It can also be the basis for a staging environment or connector environment with possible additional prerequisites. |
Concepts about the Source
| Term | Explanation | Synonyms |
|---|---|---|
Data source | A SQL Server database that is linked as a Delphix dSource | source database |
Source database server | A database server containing one or more databases that will be linked to Delphix. |
|
| Source Environment for SQL Server | A Delphix environment pointing to a Windows Source Database Server. | |
| Source Host for SQL Server | A Windows source host on which the source database (which is within a SQL Server instance) resides.
|
Concepts about the Target
| Term | Explanation | Synonyms |
|---|---|---|
Target Database Server for SQL Server | A Database Server that meets all the requirements under the Target section of Windows Database Server Requirements. See Windows Target Environment for more information. | Target Server, Target Server for SQL Server |
Target Environment for SQL Server |
Concepts about Staging
| Term | Explanation | Synonyms |
|---|---|---|
Staging database for SQL Server | A database that is automatically configured by Delphix on a Staging Server while consuming backups from a source database. | Staging Database |
Staging environment for SQL Server | A Delphix Environment pointing to a Windows Staging Server. Required for the ongoing population of backup data from your source database into the Delphix Engine. This server behaves much like a VDB target environment. Must run the same version of SQL Server as your source. | |
Windows Staging Server | A Database Server configured as a Standalone Target Server, additionally configured to access and consume backups from a Source Database. This Server should have the same version of SQL Server installed as the Source Database Server. |
|
Staging Target Database Servers | See Windows Staging Server | |
Staging Target for SQL Server |
Types of Users
| User | Explanation |
|---|---|
Source SQL Server database user | A SQL Server database user configured with the Delphix prerequisite permissions on a source database server |
Target SQL Server database user | A SQL Server Database user configured with the Delphix prerequisite permissions on a Target Database Server |
Staging Target SQL Server database user | A SQL Server Database user configured with the Delphix prerequisite permissions on a Staging Database Server |
SQL Server Data Operations in the Delphix Engine
The terms below describe actions you can perform on a Delphix Engine.
For a glossary of data operations for Delphix in general, including refreshing a VDB from a dSource and rewinding a VDB, see the Data Operations section of the general glossary.
| Concept | Explanation |
|---|---|
Configure the source environment | The act of configuring a Delphix environment to point to a source database server. Prior to performing this step, you must have one target environment configured to act as a connector target. |
Configure the target environment using a Validated Sync environment | The Validated Sync environment is required for the ongoing population of backup data from your source database into the Delphix Engine. This server behaves much like a VDB Target Environment. The Validated Sync Environment must run the same version of MS SQL Server as your Source. Synonymous to staging target for SQL Server. |
Link a SQL Server dSource | The action of defining the connection between an SQL Server database from which changes will be captured, and the Delphix dSource. This action includes the initial full restore of the SQL Server database within the Delphix dSource. |
Manage SQL Server Environments | The act of configuring or managing the Delphix environments that point to SQL Server database servers or clusters. |
Refresh SQL Server environment | Updating an environment on which the underlying software has been updated. After changes are made to an environment that was already set up in the Delphix Management application (such as installing a new database home, creating a new database, or adding a new listener) it may be necessary to refresh the environment to reflect these changes. During environment discovery and environment refreshes, Delphix pushes a fresh copy of the toolkit to each host environment. Included in the toolkit are: A JRE (Java Runtime Engine), Delphix jar files, the hostchecker utility, scripts for managing the environment and/or VDBs, Delphix Connector log files. Delphix then executes some of these scripts to discover information about the objects in the environment (such as where the databases are installed, the database names, information required to connect to these databases, etc.). In some environments (Windows in particular), the scripts are customized to fit the customer’s environment. |
SQL Server and Delphix Self-Service (Jet Stream)
| Concept | Explanation |
|---|---|
Refresh a SQL Server VDB from parent VDB in Delphix Self-Service | Refresh is faster since Refresh will update the data (on the active branch) of a user's data container. The user will then have the latest data in the sources of the data template from which the container was provisioned. |
Reset SQL Server VDB in Delphix Self-Service | Reset in Delphix Self-Service, is a simplified version of Restore built to support an "undo." It allows a user to reset the state of their application container to the last operation. The complete set of operations that reset will reset to is: CREATE_BOOKMARK, CREATE_BRANCH, REFRESH, RESET, RESTORE, and UNDO. This can be useful for testing workflows where, after each test, users want to reset the state of their environment. |
Similarities and Differences between a SQL database and a Delphix VDB
Similarities
- is read/write capable
- has its own transaction logs
- is accessible via a SQL Server Instance
- can be upgraded to a higher release of SQL Server
Connections to a VDB can be made with ADO.NET, OLE DB and all other methods
Differences
You can rewind a VDB to a prior point in time without the need for special SQL Server features.
You can provision a VDB from a VDB.
You can refresh VDBs at any time from their source database with a few clicks.
You can analyze I/O-related bottlenecks by drilling into Delphix’s Network.
You can take a snapshot of a VDB at any point without impacting performance or usability, effectively bookmarking key points in a VDBs timeline.