ODBC Connection problems

Visual objects applications connect to other databases like SQL through an ODBC connection.  The default connection is made on version 10.  Later versions of SQL server installs version 11, which might cause the default connection to fail.  Version 10 is linked to SQL Server 2008 and SQL Server 2012 links to a default ODBC of version 11.  Upgraing is not a problem as Version 10 will be retained, but uninstalling the older version might result in unexpected connection problems from VO apps that require ODBC connection to SQL.

The installed drivers can be seen on the Control Panel | Data Sources (ODBC) interface.

If required, this can be corrected by downloading the correct version of SQL Server Native Client, which is free.  The download linked to SQL Server 2008 is normally the correct version 10 and the required file is: sqlncli.msi and can be installed if required.

Applications that allow the selection of the ODBC Provider can select this as indicated below.

Bernard

SQL and the Firewall

The latest programs developed by Aviation Databases, makes use of SQL server to store and manipulate the data.  This is a robust method but we have found that users new in the SQL environment experience problems to connect to the server from a non-server station.

There is a detailed article available on the internet assisting users to configure the SQL server environment for connection from a remote PC.  Click here for a summary to configure the server and click here for a summary of how to open the Firewall.  The basic requirements are as follows:

On the Server

1. Ensure that the SQL Server Browser is running and the start mode is automatic (SQL Server Configuration manager)
2. Enable TCP/IP protocol (SQL Server Configuration manager)
3. If the server is not operating in a Domain environment, Windows Authentication will not be available.  Select SQL Server and Windows authentication (SQL Server Management Studio)
4. Firewall must allow the programs “sqlbrowser.exe” and “sqlserver.exe” access.  Also open the default listening port TCP 1433

Also look into our other Blog on installing SQL Server 2008.

Installing SQL Server 2008

Aviation Databases are using SQL Server as a data server in our latest programs.  This is done due to the advantages this gives us to improve our applications.  SQL Server is a more stable data platform and is faster when large files are processed by our programs.  There are various other advantages to using SQL server and it is simply time to move from the old dBase environment.

Users not familiar with SQL Server, find it difficult to know where to start and what is required.  SQL Server is a very powerfull server system, but to use our programs with SQL server will not require the users to interact with SQL server at all, as all communication with SQL Server is done from the program.  Afirst time installation is required on the Server or a PC dedicated for this task.

Note that these instructions are only relevant to the server PC and is not required for other station PC’s that use our programs.  These PC’s will simply link to the server, but does not require any installation of SQL Server components.

The minimum requirements does not require any SQL server management tools to be installed.  Management tools are handy, should maintenance be required in the SQL server.  The only other choice is to know if your server PC is a 32-bit or 64-bit system.  The next step is to download the latest installation programs and to install.  Please follow these simple steps to ensure a smooth installation.

We are using SQL Server 2008 Express as a minimum requirement.  SQL Server Express is a free application for the typical database size that we normally require and can be downloaded from the internet.  At the moment R2 is available and can be downloaded from these sites:

• Basic server installation
• Server with management tools installation

Experienced users can simply follow the installation dialog, but this might be challenging for new users.  It is therefore recommended that users download this small configuration file from our ftp site to enable installation from the command line with no user information required.

Older PC’s might require other updates, before you will be able to install SQL Server.  These requirements are defined on the web link and can also be downloaded from this page.  These are: Microsoft .Net Frameworek 3.5 SP1 and Windows Installer 4.5 Note that the Server with management tools requires an extra program: Windows PowerShell 1.0 to be installed on the server PC.

Once your Server PC is up to date, proceed to install SQL Server.  Copy the configuration file into the same directory as the SQL Server 2008 installation file.  Open the command prompt window (Start –> Run > cmd).  Change to the download directory and run the installation from the command prompt: (On a 32-bit installation)

SQLEXPR32_x86_enu.exe /ConfigurationFile=c:\sql\AvdataSQLConfig.INI

On a successful installation, it should be possible to see the server.  This can be checked from the command prompt, by entering the command: “sqlcmd –L”

Grant application user access

Users must have sufficient access rights or roles on the SQL server to connect to the database and access the database files and procedures as stored in the SQL server.  This is applicable to all programs using a SQL server for the data, like Toolman and Status.

Installing Status and Toolman applications for the first time on a server machine, will grant the SQL user sufficient access to the database.  It is however necessary to allow other users access to the database.  This can be done from inside the program from the SQL connect window.

There are two different possibilities here, users can log on with Windows Authentication, where the program will use the access asigned to the “BUILTIN\Users” or specific users where Windows Authentication is not used.

From the waterfall menu select the SQL Connect window, connect to the server and select Save on the catalog selection.  The Manage Access button should be available if you have sufficient access to grant access to others.

Select the “Manage Access” button.  The window that will open shows all you access rights and has two options to grant rights to other users.

 

Selecting the top “Grant” button, will allow all “BUILTIN\Users” access to the selected catalog or database.  This will therefore work in a domain or environment where users will connect through Windows Authentication.

Alternatively, it is possible to create users and assign the applicable rights to this new user to access the database.  Note that some SQL server requires a strong password, otherwise this step might fail.

Once access is granted to other users, there should be no problems for them to connect and use the applicable database from the program.

---

Users experienced in SQL can use the Management Studio application to set this access.  Assign the database owner role to users.