Version User Scope of changes
Oct 17 2009, 10:09 AM EDT (current) sdrevik 217 words added
Oct 17 2009, 10:03 AM EDT sdrevik

Changes

Key:  Additions   Deletions
For most installations of SQL Server on a single machine (it depends on the version), the SQL "Instance" name is the same as the PC. e.g., if you installed on a PC called "DASSERVER", the SQL Instance name is also "DASSERVER."

However, for SQL Express, or installations where a PC is running multiple versions of SQL (and in some other cases), the SQL Installer may create a different instance name: DASSERVER\SQLSERVER, DASSERVER\SQLEXPRESS, etc

When this happens, you cannot use the "localhost" reference in some of our documentation. Rather, the reference to the database server must be explicit in the Server Settings Editor and the E-DAS Data Conversion Tool.

Also, for the E-DAS Data Conversion Tool, you must edit C:\Program Files\Agilaire LLC\Edas Conversion\AirVisionConversion.exe.cfg to reference you exact instance name, e.g:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<configSections>
</configSections>
<connectionStrings>
<add name="AirVisionConversion.Properties.Settings.AvDataConnectionString3"
connectionString="Data Source=DASSERVER\SQLSERVER;Initial Catalog=AvData;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="AirVisionConversion.Properties.Settings.AvDataConnectionString"
connectionString="Data Source=DASSERVER\SQLSERVER;Initial Catalog=AvData;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="AirVisionConversion.Properties.Settings.AvDataConnectionString1"
connectionString="Data Source=DASSERVER\SQLSERVER;Initial Catalog=AvData;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="AirVisionConversion.Properties.Settings.AvDataConnectionString2"
connectionString="Data Source=DASSERVER\SQLSERVER;Initial Catalog=AvData;Integrated Security=True"
providerName="System.Data.SqlClient" />
</connectionStrings>
</configuration>


(Note that for Vista or Server 2008, you will need to edit a copy of this file on your desktop, and re-copy to the Program Files directory, as you cannot edit it directly there, even with Administrator privileges).