Results 1 to 8 of 8

Thread: ODBC Connection to MS-SQL v11

  1. #1
    Junior Member
    Join Date
    Jul 2015
    Posts
    12

    ODBC Connection to MS-SQL v11

    I can create a system DSN to the SQL server using the SQL Server Native Client 11, the SQL server or ODBC driver 11 for SQL Server. However if I use Lianja ODBC driver, it can't connect (no response is the answer) In the app Builder, it can't use any of the connection I create with the other drivers. (Failed to connect to DB source.)

    Windows 7, tried 32 and 64 bit options. Tried using the ODBC manager.

    How are connections to MSSQL v 11 (2014) handled? Or what am I missing?

  2. #2
    Lianja Team davefoss's Avatar
    Join Date
    Feb 2012
    Posts
    111
    Lianja currently only supports 32 bit ODBC drivers so you will want to verify that you are using the 32 bit version of the SQL Server ODBC driver as well as the 32 bit ODBC Administrator (usually found here: C:\Windows\SysWOW64\odbcad32.exe). You can test the connection in the ODBC tab of the Console WorkSpace by entering your DSN name as the Connstring and supplying any necessary user credentials.

    The Lianja ODBC driver is used to connect to the Lianja SQL Server.

  3. #3
    Junior Member
    Join Date
    Jul 2015
    Posts
    12
    Thanks, tried USER and SYSTEM DSN, 32 and 64 bit. Just about every combination I can think of.

    What is the update process? The Lianja Create Virtual tables from ODBC responds very quickly when I press the tables button. I don't know how it knows that fast it can't do anything. Is there a restart/reload process between when I create a new DSN and when the wizard can use that connection?

  4. #4
    Junior Member
    Join Date
    Jul 2015
    Posts
    12
    Here what I was able to connect.
    Driver={SQL Server Native Client 11.0};Server=myServerAddress;
    Database=myDataBase;Uid=myUsername;Pwd=myPassword;

    Instead of a local or system DSN, it is the actual string that is saved by the control panel that worked for me.

  5. #5
    Lianja Team davefoss's Avatar
    Join Date
    Feb 2012
    Posts
    111
    As long as the DSN exists when you try to use it then you shouldn't have any issues.

  6. #6
    Lianja Development Team barrymavin's Avatar
    Join Date
    Feb 2012
    Location
    UK, USA, Thailand
    Posts
    6,221
    You can always specify the full connection string if you do not want to setup an odbc dsn on each machine.

    As dave has pointed out you need to create a 32 bit odbc dsn and also have the 32 bit odbc driver installed.

    Many people are using virtual tables with odbc.

    Later as detailed in the roadmap we will be providing a 64-bit version on windows which will use the normal 64 bit odbc drivers but in the meanwhile you need to use the 32 bit ones.

    Be be sure to make yourself heard on the poll!
    http://www.lianja.com/community/show...3553#post13553
    Last edited by barrymavin; 2015-07-25 at 09:29.
    Principal developer of Lianja, Recital and other products

    Follow me on:

    Twitter: http://twitter.com/lianjaInc
    Facebook: http://www.facebook.com/LianjaInc
    LinkedIn: http://www.linkedin.com/in/barrymavin

  7. #7
    Lianja MVP
    Join Date
    Feb 2012
    Location
    Berea, KY, USA
    Posts
    2,068
    One tip on installing the 32-bit drivers on 64-bit machines: regardless of your SQL Server version (back to 2005), get the 64-bit "ODBC Driver 11 For SQL Server" 64-bit install https://www.microsoft.com/en-us/down....aspx?id=36434 and it will install both the 64-bit driver and the 32-bit driver. If you try to install the 32-bit install on an x64 machine, it will fail.

    When building an installer, run both installs for silent install, using the directions here: https://msdn.microsoft.com/en-us/lib...=sql.110).aspx (This does not appear to be searchable by Google, so store it away somewhere for when you need it). The installation command will look like this, but you will want to rename the installers to identify them. This command line is different than all prior versions in a couple of ways:

    Code:
    msiexec /quiet /passive /qn /i msodbcsql.msi IACCEPTMSODBCSQLLICENSETERMS=YES


    The ODBC Driver 11 will work against all SQL Servers back to 2005, so this simplifies your installer. Further simplifying matters, as mentioned above, you can have the installer run both the 64-bit (which includes 32-bit) and the 32-bit installs. If on x64, the 33-bit install will fail to run (but do so silently and quickly), but the 64-bit install will install the 32-bit driver. The reverse is true if you are installing on a 32-bit server.

    enjoy,

    Hank

  8. #8
    Member
    Join Date
    Mar 2014
    Posts
    93
    Hi Hank - very good info!
    Certainly will save a fair bit of research time if I find myself in a similar situation...
    Regards Paul.

Bookmarks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Journey into the Cloud
Join us