Follow the steps below if you have a supported edition of Microsoft SQL Server. We recommend that you create an instance for Smart Interop Publisher, but you can skip this section to continue using your existing SQL Server instance.
-
Verify that you have access to your original installation media. Otherwise, you cannot continue the configuration steps below.
-
Verify that you have Administrator privileges on the computer.
-
Click Start > All Programs > Microsoft SQL Server [Version Number] > Configuration Tools > SQL Server Installation Center (64-bit).
-
Click Installation > New SQL Server stand-alone installation or add features to an existing installation.
-
Accept the licensing terms, and click Next.
-
From the Setup Support Files page, click Install.
-
From the Setup Support Rules page, correct any failures before continuing.
-
Click Next.
-
From the Feature Selection page, select the Database Engine Services.
-
For Shared feature directory and Shared feature directory (x86), use the default paths, or choose a custom location.
We recommend that you use the default paths.
-
Click Next.
-
From the Instance Configuration page, we suggest the following names. You can use whatever name and ID is required for your system setup.
-
Named instance: SPIOPSQLExpress
-
Instance ID: SPIOPSQLExpress
-
-
Click Next.
-
From the Server Configuration page, select NT AUTHORITY\NETWORK SERVICE for the Account name, and then click Next.
-
From the Database Engine Configuration page:
-
Select Windows authentication mode.
-OR-
Select Mixed Mode which includes a local SQL Administrator account and Windows authentication. -
In the Specify SQL Server administrators, click Add Current User.
-
For other users or groups to access this database, click Add and then enter their names or group names.
-
-
Click Next.
-
From the Error and Usage Reporting page, select options to send error reports to Microsoft; otherwise, click Next.
-
From the Installation Progress page, wait as the install process finishes.
-
From the Complete page, click Close.
Perform Network Configuration
Follow the steps below to configure your network for Smart Interop Publisher.
-
Click Start > All Programs > Microsoft SQLServer [version number] > Configuration Tools > SQL Server Configuration Manager.
-
From the Configuration Manager, go to SQL Server Network Configuration > Protocols for SPIOPSQLEXPRESS.
If you gave the server a different instance name, make sure you use that name here
in place of SPIOPSQLEXPRESS.
-
Enable Named Pipes and TCP/IP.
-
Click OK at the prompt.
-
To restart the server, click SQL Server Services, and then click SQL Server SPIOPEXPRESS (or your instance name), and right-click to select Restart.
Wait as the service restarts.
-
Close the SQL Server Configuration Manager.
-
Continue on to Install Smart Interop Publisher.
Grant Existing Users Permission to Access the SQL Server Instance
SQL Server must be configured to use Windows Authentication to allow communication from Smart Interop Publisher. The user login for each workstation running Smart Interop Publisher must also exist for that user on the SQL Server instance. The Windows login must have the role of dbcreator.
The steps below outline the process for using SQL Server Management Studio to create the SQL Server instance user login. The steps can vary depending on how the SQL Server was initially configured.
-
Start the MS SQL Server Management Studio.
-
Connect to SQL Server using an account that has administrator privileges.
-
Expand Security.
-
Right-click Logins.
-
Select New Login.
The Login - New dialog box displays.
-
In the General Page, enter in a Windows authentication login, such as a valid domain login.
-
You might have to search and check names, depending on the LAN Configuration at your site. On the Server Roles page, verify that the account has the server role dbcreator activated. You can add other roles to the account, if required.
-
On the User Mapping page, assign the user the dbowner role on any existing site or project databases.
-
-
Click OK to create the login.
The new login displays in the Logins treeview.
-
Exit MS SQL Server management Studio.