{"id":1306,"date":"2022-12-14T19:15:54","date_gmt":"2022-12-14T19:15:54","guid":{"rendered":"https:\/\/www.hammerdb.com\/blog\/?p=1306"},"modified":"2022-12-14T19:16:14","modified_gmt":"2022-12-14T19:16:14","slug":"configuring-unixodbc-and-sql-server-drivers-for-hammerdb-on-linux","status":"publish","type":"post","link":"https:\/\/www.hammerdb.com\/blog\/uncategorized\/configuring-unixodbc-and-sql-server-drivers-for-hammerdb-on-linux\/","title":{"rendered":"Configuring unixODBC and SQL Server Drivers for HammerDB on Linux"},"content":{"rendered":"

 <\/p>\n

In this post, we will do a walk through example of installing and configuring unixODBC and the SQL Server on Linux drivers as well as the HammerDB connection options to enable HammerDB on Linux to be able to connect to SQL Server. In the example, we have SQL Server running on Windows and are using a virtualized Linux instance to run HammerDB to connect to SQL Server.<\/p>\n

unixODBC<\/h3>\n

Firstly get unixODBC from here http:\/\/www.unixodbc.org\/<\/a> and configure making sure the that the –enable-fastvalidate option is given. In this example, we install in the \/usr\/local directory using the command make and make install after configure.<\/p>\n

\n\t\t\t
\n
\n
\n
<\/div>\n
<\/div>\n
<\/div>\n <\/div>\n
\n \n Copy Code<\/span>\n Copied<\/span>\n Use a different Browser<\/span><\/a>\n <\/div>\n <\/div>\n 
<\/p>\n
.\/configure --prefix=\/usr\/local\/unixODBC --enable-gui=no --enable-drivers=no --enable-iconv --with-iconv-char-enc=UTF8 --with-iconv-ucode-enc=UTF16LE --enable-threads=yes --enable-fastvalidate<\/pre>\n
<\/code><\/pre>\n\t\t\t<\/div>\n        <\/div>\n
Microsoft ODBC Drivers<\/h3>\n
Then install the Microsoft ODBC Drivers using the instructions here<\/a>.\u00a0 Once installed, we will see the drivers successfully installed and find the dependent libraries we need.<\/p>\n
\n\t\t\t
\n                
\n                    
\n                        
<\/div>\n                        
<\/div>\n                        
<\/div>\n                    <\/div>\n                    
\n                        \n                        Copy Code<\/span>\n                        Copied<\/span>\n                        Use a different Browser<\/span><\/a>\n                    <\/div>\n                <\/div>\n                
<\/p>\n
root@REDPOLL:\/opt\/microsoft# ls\r\nmsodbcsql17 msodbcsql18\r\nroot@REDPOLL:\/opt\/microsoft# ls msodbcsql18\/lib64\/\r\nlibmsodbcsql-18.1.so.2.1\r\n<\/pre>\n
<\/code><\/pre>\n\t\t\t<\/div>\n        <\/div>\n
Add the drivers to \/usr\/local\/odbcinst.ini either using the obcinst command or through manual editing of odbcinst.ini.<\/p>\n
\n\t\t\t
\n                
\n                    
\n                        
<\/div>\n                        
<\/div>\n                        
<\/div>\n                    <\/div>\n                    
\n                        \n                        Copy Code<\/span>\n                        Copied<\/span>\n                        Use a different Browser<\/span><\/a>\n                    <\/div>\n                <\/div>\n                
<\/p>\n
root@REDPOLL:\/usr\/local\/unixODBC\/etc# more odbcinst.ini \r\n[ODBC Driver 17 for SQL Server]\r\nDescription=Microsoft ODBC Driver 17 for SQL Server\r\nDriver=\/opt\/microsoft\/msodbcsql17\/lib64\/libmsodbcsql-17.10.so.2.1\r\nUsageCount=1\r\n[ODBC Driver 18 for SQL Server]\r\nDescription=Microsoft ODBC Driver 18 for SQL Server\r\nDriver=\/opt\/microsoft\/msodbcsql18\/lib64\/libmsodbcsql-18.1.so.2.1\r\nUsageCount=1<\/pre>\n
<\/code><\/pre>\n\t\t\t<\/div>\n        <\/div>\n
We can verify the configuration and drivers as follows:<\/p>\n
\n\t\t\t
\n                
\n                    
\n                        
<\/div>\n                        
<\/div>\n                        
<\/div>\n                    <\/div>\n                    
\n                        \n                        Copy Code<\/span>\n                        Copied<\/span>\n                        Use a different Browser<\/span><\/a>\n                    <\/div>\n                <\/div>\n                
<\/p>\n
root@REDPOLL:\/usr\/local\/unixODBC# .\/bin\/odbcinst -j\r\nunixODBC 2.3.11\r\nDRIVERS............: \/usr\/local\/unixODBC\/etc\/odbcinst.ini\r\nSYSTEM DATA SOURCES: \/usr\/local\/unixODBC\/etc\/odbc.ini\r\nFILE DATA SOURCES..: \/usr\/local\/unixODBC\/etc\/ODBCDataSources\r\nUSER DATA SOURCES..: \/usr\/local\/unixODBC\/etc\/odbc.ini\r\nSQLULEN Size.......: 8\r\nSQLLEN Size........: 8\r\nSQLSETPOSIROW Size.: 8\r\n\r\nroot@REDPOLL:\/usr\/local\/unixODBC# .\/bin\/odbcinst -d -q\r\n[ODBC Driver 17 for SQL Server]\r\n[ODBC Driver 18 for SQL Server]\r\n\r\n<\/pre>\n
<\/code><\/pre>\n\t\t\t<\/div>\n        <\/div>\n
As our hammerdb user we can then set our .bash_profile and ensure that the ODBC drivers are found.<\/p>\n
\n\t\t\t
\n                
\n                    
\n                        
<\/div>\n                        
<\/div>\n                        
<\/div>\n                    <\/div>\n                    
\n                        \n                        Copy Code<\/span>\n                        Copied<\/span>\n                        Use a different Browser<\/span><\/a>\n                    <\/div>\n                <\/div>\n                
<\/p>\n
hammerdb@REDPOLL:~$ more .bash_profile \r\nexport PATH=\"$PATH:\/opt\/mssql-tools\/bin\"\r\nexport PATH=:\/usr\/local\/unixODBC\/bin:$PATH\r\nexport LD_LIBRARY_PATH=\/usr\/local\/unixODBC\/lib:$LD_LIBRARY_PATH\r\nexport ODBCSYSINI=\/usr\/local\/unixODBC\/etc\r\nexport ODBCINI=\/usr\/local\/unixODBC\/etc\/odbc.ini\r\n\r\nhammerdb@REDPOLL:~$ odbcinst -d -q\r\n[ODBC Driver 17 for SQL Server]\r\n[ODBC Driver 18 for SQL Server]<\/pre>\n
<\/code><\/pre>\n\t\t\t<\/div>\n        <\/div>\n
Test Connectivity<\/h3>\n
In this example, as we are running HammerDB for Linux in a VM to connect back to the Windows host we need to either configure or temporarily disable Defender Firewall to allow HammerDB to connect to SQL Server.<\/p>\n
\"\"<\/a><\/p>\n
And also enable remote connections to SQL Server from SSMS.<\/p>\n
\"\"<\/a><\/p>\n
We also need to use SQL Server Authentication, and set a password for the sa user.<\/p>\n
\"\"<\/a><\/p>\n
And configure HammerDB to connect from Linux to Windows, and therefore we set the TCP check option as well as using the SQL Server authentication with the user and password we set previously.<\/p>\n
\"\"<\/a><\/p>\n
Build Schema<\/h3>\n
We can now run HammerDB to verify that we can connect to SQL Server from our Linux client.<\/p>\n
\"\"<\/a><\/p>\n
Run Test<\/h3>\n
We the build is complete, we can begin running a test from our SQL Server on Linux client.<\/p>\n
\"\"<\/a><\/p>\n
And confirm that our Linux host has connected and is running the workload on SQL Server.<\/p>\n
\"\"<\/a><\/p>\n
Summary<\/h3>\n
In this post, we have shown how to configure the ODBC Drivers for SQL Server on Linux for HammerDB. When the test complete, do not forget to re-enable Windows Firewall if you disabled it.<\/p>\n","protected":false},"excerpt":{"rendered":"
  In this post, we will do a walk through example of installing and configuring unixODBC and the SQL Server on Linux drivers as well as the HammerDB connection options to enable HammerDB on Linux to be able to connect to SQL Server. In the example, we have SQL Server running on Windows and are … <\/p>\n
Continue reading “Configuring unixODBC and SQL Server Drivers for HammerDB on Linux”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"ppma_author":[5],"class_list":["post-1306","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"authors":[{"term_id":5,"user_id":2,"is_guest":0,"slug":"hammerdb","display_name":"HammerDB","avatar_url":{"url":"https:\/\/www.hammerdb.com\/blog\/wp-content\/uploads\/2018\/10\/logo-white.png","url2x":"https:\/\/www.hammerdb.com\/blog\/wp-content\/uploads\/2018\/10\/logo-white.png"},"author_category":"","user_url":"http:\/\/www.hammerdb.com","last_name":"","first_name":"","job_title":"","description":""}],"_links":{"self":[{"href":"https:\/\/www.hammerdb.com\/blog\/wp-json\/wp\/v2\/posts\/1306","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.hammerdb.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.hammerdb.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.hammerdb.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.hammerdb.com\/blog\/wp-json\/wp\/v2\/comments?post=1306"}],"version-history":[{"count":14,"href":"https:\/\/www.hammerdb.com\/blog\/wp-json\/wp\/v2\/posts\/1306\/revisions"}],"predecessor-version":[{"id":1328,"href":"https:\/\/www.hammerdb.com\/blog\/wp-json\/wp\/v2\/posts\/1306\/revisions\/1328"}],"wp:attachment":[{"href":"https:\/\/www.hammerdb.com\/blog\/wp-json\/wp\/v2\/media?parent=1306"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.hammerdb.com\/blog\/wp-json\/wp\/v2\/categories?post=1306"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.hammerdb.com\/blog\/wp-json\/wp\/v2\/tags?post=1306"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.hammerdb.com\/blog\/wp-json\/wp\/v2\/ppma_author?post=1306"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}