Abstract:
This “How To” article provides an alternative database installation method in cases where the standard Attach Database Wizard is insufficient.
Instructions:
Download backup of a blank Velocity database to be used as a model here: https://drive.google.com/file/d/1Mj7Stou9Op_l_772o_W2P_V7K-pkFmp2/view?usp=sharing
The database is a blank Velocity 3.6 database that can be used for installing Velocity 3.6 or later
This model database is from a SQL Server 2012 - so you won't be able to restore it to a SQL Server 2008R2 environment, but you can restore it to SQL2012, 2014, 2016, 2017+
Create a Velocity database in SQL server - leave options default
Restore the backup you downloaded in Step 1 with overwrite, and if necessary change the file locations to reflect your environment.
Run this query:
Use Velocity;
declare @authPath nvarchar(100);
set @authPath = 'domainName'
insert into MiscProperties (Name, Value)
values ('UseDomainAuthentication','1'),
('AuthenticationPath',@authPath)
Note: Change the domain name in the @authpath to reflect the actual domain name
On the new Velocity application server, manually install the correct SQL Native Client Installer by downloading directly from Microsoft here: https://www.microsoft.com/en-us/download/details.aspx?id=50402
Install Velocity
Type in the remote SQL instance name
Ignore the 'domain admin' message
Use 'advanced user and service' accounts
Click next all the way through