SQL Authentication

To use SQL Authentication instead of the built-in NT (Windows) Authentication follow the steps below:

1.  Create an SQL User

  • Launch the Database Utility Program (located on the database server. If you are using Windows 7, Windows Vista, or Windows 2008 Server, right-click the shortcut and choose Run As Administrator.
  • Connect to the proper SQL Server hosting your ESHA Database
  • From the drop-down on the toolbar, verify the correct database is selected ('gendata' or 'eshadata')
  • Click on "Users > Manage"
  • Click the "New" button
  • For Authentication, select SQL Authentication
  • Type in a "User Name" and "Password" (repeated for verification)
    Click "Create"

NOTE:If using SQL Server Management Studio to create the SQL user, it is recommended to deselect 'User must change password at next login'.  Also, this Login must be made a member of the ESHA Database role 'FPRole'.

2.  Create a "UDL" file on the Client machine

    • On the client machine, create a new file called "esha.udl" in the "c:\program files\esha research\{program}sql" folder (Make sure that file extensions aren't hidden or else this will look like a text file)
  • Open the "esha.udl" file and go to the "Provider" tab
  • Select "Microsoft OLE Provider for SQL Server"
  • Press "Next" (Connection tab)
  • Choose your server from the list (Generally this is "servername\esha")
  • Choose to "Use a specific user name and password"
  • Type in the user name and password created above
  • From the database list, select the database you wish to connect to ('eshadata' or 'gendata')
  • Press "Test Connection" to test the database connectivity
  • If the test is successful, press "Ok"

3.  Make changes to the ini file

  • Open the program's ini file, located in "c:\program files\esha research\{program}sql"
  • Change "UsesUDLFileConnection=0" to "UsesUDLFileConnection=1"
  • Change "UDLFilePathString=" to "UDLFilePathString=c:\program files\esha research\{program}sql\esha.udl"
  • Save the changes to the ini file and exit

If you have any questions, regarding this procedure, let us know.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk