Which source control systems are supported?
Git, Mercurial, Subversion, Perforce and Team Foundation Server. Please see supported software page for the specific version
How is integration with a source control system managed, e.g. via a command line interface?
ApexSQL Source Control provides native support with latest application control interfaces for all supported source control systems which does not need a separate installation of a client in order to work (except for Mercurial). Besides this the user can use any source control system that supports the Command Line Interface
What source control models are supported?
ApexSQL Source Control supports both shared and dedicated database development models
How do I initially script my entire database into source control?
After the database is linked to source control with ApexSQL Source Control, by default all objects in the Action center tab will be selected for the initial commit. Click the Apply button to perform the initial commit
Can I version control encrypted objects?
Yes, encrypted objects can be versioned in any supported source control system
What SQL Server versions are supported?
Microsoft SQL Server vNext CTP1, 2016, 2014, 2012, 2008 with Client tools (SQL Server Management Studio), and 2005 without Client tools
Can all ApexSQL add-ins co-exist in a single SQL Server Management Studio instance?
ApexSQL Source Control can be used alongside any other ApexSQL add-in
How can I build a database directly from my versioned objects?
Use ApexSQL Build to create a database directly from the scripts stored under source control with a few clicks, or use ApexSQL Source Control to link an empty database to the repository where the scripts are stored and apply all from source control through the Action center tab
What SQL Server objects can be version controlled?
All SQL Server non-system objects can be version controlled through ApexSQL Source Control
How do I manage change conflicts?