This topic describes basic concepts behind the creation of dSources from SQL Server databases.
When you create a dSource from a SQL Server database, the initial snapshot is derived from a full or differential database backup of the source database. The database backup can be a new full database backup initiated by the Delphix Engine, the most recent existing database backup, or a specific existing database backup as identified by its backup_set_uuid. When loading from an existing backup, the backup should be in a location that is accessible over SMB by both the staging target's environment user and the Windows user running the SQL Server instance on the staging host, as shown in the diagram in Setting Up SQL Server Environments: An Overview.
After obtaining the initial snapshot and linking the dSource, the Delphix Engine keeps the dSource and the source database in sync by monitoring the source database for new backups, and then using those backups to perform a restore on the staging database, as described in Setting Up SQL Server Environments: An Overview. If the source database is in full or bulk-logged recovery model, the Delphix Engine monitors and applies new transaction log backups. If the source database is in simple recovery model, the Delphix Engine monitors and applies new full and differential database backups.
After you have linked a database into the Delphix Engine, you can re-initialize it by performing a sync on the dSource. Performing a sync restores a database backup, which can be a new full database backup taken by the Delphix Engine, the most recent full or differential database backup, or a specific full or differential backup as identified by its backup_set_uuid.
The Delphix Engine supports source database backups that SQL Server creates natively, as well as backups created by Quest/Netvault LiteSpeed and Red Gate SQL Backup Pro. For more information, see the topic Supported Operating Systems, Server Versions, and Backup Software for SQL Server.