2,411
edits
Changes
From SME Server
Jump to navigationJump to search
mLine 4:
Line 4: − + Line 52:
Line 52: − − − − − − − − − Line 89:
Line 80: − + Line 140:
Line 131: − + Line 190:
Line 181: − + Line 230:
Line 221: − + + + Line 239:
Line 232: − + − + + + + + + + − The host name xp3c used in the examples above works in a workgroup environment, it could(should?) be a full FQDN like xp3c.mydomain.com in a NT domain environment.+ − + − Ms SQL Server might not allow the db system user "sa" to connect from outside the server, create another account with proper permissions.+
Minor text changs
Adding support in SME Server for a universal connection to foreign datebase servers using Open Database Connectivity (ODBC) with focus on PHP.
Adding support in SME Server for a universal connection to foreign datebase servers using Open Database Connectivity (ODBC) with focus on PHP.
We will assume that you have an Ms SQL Server 2000/2005 running somewhere. The SQL Server should allow remote access and support connections using TCP/IP. As of my knowledge, connections using named pipes are unsupported. Of course; you will want a login id and password.
We will assume that you have an Microsoft SQL Server 2000/2005 running somewhere. The SQL Server should allow remote access and support connections using TCP/IP. As of my knowledge, connections using named pipes are unsupported. Of course; you will want a login id and password.
It should be similar with Sybase and other versions of SQL Server, consult FreeTDS and unixODBC documentation for details.
It should be similar with Sybase and other versions of SQL Server, consult FreeTDS and unixODBC documentation for details.
wget http://ibiblio.org/pub/Linux/ALPHA/freetds/stable/freetds-0.82.tar.gz
wget http://ibiblio.org/pub/Linux/ALPHA/freetds/stable/freetds-0.82.tar.gz
gzip -d freetds-0.82.tar.gz
gzip -d freetds-0.82.tar.gz
tar -xvf freetds-0.82.tar
tar -xvf freetds-0.82.tar
cd freetds-0.82
cd freetds-0.82
./configure --sysconfdir=/etc --prefix=/usr --with-tdsver=8.0
./configure --sysconfdir=/etc --prefix=/usr --with-tdsver=8.0
make
make
make install
make install
make clean
make clean
signal-event post-upgrade; signal-event reboot
signal-event post-upgrade; signal-event reboot
{{Warning box|msg=Leaving gcc on a production server is considered a security risk, if you do not really need it you should not install it, if you need it you should seriously consider uninstalling gcc when you no longer need it. Removing gcc can be done using the following command:
{{Warning box|msg=Leaving gcc on a production server is considered a security risk, if you do not really need it you should not install it, if you need it you should seriously consider uninstalling gcc when you no longer need it. Removing gcc can be done using the following command:
yum remove gcc}}
yum remove gcc}}
unixodbc: yes
unixodbc: yes
Test connection to the foreign database, overriding settings in freetds.conf (modify to suit your conditions). IP and not FQDN should be used. If on a NT domain, replace <dbuser> with <'DOMAINNAME\dbuser'> (apostrophe before and after).
Test connection to the foreign database, overriding settings in freetds.conf (modify to suit your conditions). IP and not FQDN should be used. If on a NT domain, replace <dbuser> with <'DOMAINNAME\dbuser'>.
tsql -H 192.168.0.112 -p 1433 -U dbuser -P dbpass
tsql -H 192.168.0.112 -p 1433 -U dbuser -P dbpass
[FreeTDS]
[FreeTDS]
Description = Access Ms SQL Server with FreeTDS driver
Description = Access Microsoft SQL Server with FreeTDS driver
Driver = /usr/lib/libtdsodbc.so
Driver = /usr/lib/libtdsodbc.so
Generally speaking, isql is a bit more fussy about correct configuration settings than tsql, therefore we include also this test.
Generally speaking, isql is a bit more fussy about correct configuration settings than tsql, therefore we include also this test.
At the command line enter <isql -v DSN USERNAME PASSWORD>. If on a NT domain, replace <dbuser> with <'DOMAINNAME\dbuser'> (apostrophe before and after):
At the command line enter <isql -v DSN USERNAME PASSWORD>. If on a NT domain, replace <dbuser> with <'DOMAINNAME\dbuser'>:
isql -v remoteserver dbuser dbpass
isql -v remoteserver dbuser dbpass
FreeTDS [http://www.freetds.org/userguide/ user guide] with [http://www.freetds.org/userguide/troubleshooting.htm troubleshooting section].
FreeTDS [http://www.freetds.org/userguide/ user guide] with [http://www.freetds.org/userguide/troubleshooting.htm troubleshooting section].
[http://se2.php.net/manual/en/book.uodbc.php php.net ODBC]
unixODBC [http://www.unixODBC.org official site]
[http://php.net/manual/en/book.uodbc.php php.net ODBC]
Input from, and credit to, Nick Critten [http://bends.se/it/smeserver/filer/HowTo_NickCritten_freetds.html unofficial copy of his HowTo] and [http://www.calio.it/docs/doku.php/sqlserver calio.it] [http://translate.google.se/translate?u=http%3A%2F%2Fwww.calio.it%2Fdocs%2Fdoku.php%2Fsqlserver&sl=it&tl=en&hl=sv&ie=UTF-8 translated]
Input from, and credit to, Nick Critten [http://bends.se/it/smeserver/filer/HowTo_NickCritten_freetds.html unofficial copy of his HowTo] and [http://www.calio.it/docs/doku.php/sqlserver calio.it] [http://translate.google.se/translate?u=http%3A%2F%2Fwww.calio.it%2Fdocs%2Fdoku.php%2Fsqlserver&sl=it&tl=en&hl=sv&ie=UTF-8 translated]
Tab spaces in config files may cause troubles, use single space before and after the <=>.
Tab spaces in config files may cause troubles, use single space before and after the <=>.
If on a NT domain, replace <dbuser> with <'DOMAINNAME\dbuser'> (apostrophe before and after).
If on a NT domain, replace <dbuser> with <'DOMAINNAME\dbuser'> (with a single quotation mark before and after).
<br> Tests suggest that <DOMAINNAME\\dbuser> also work.
<br>Escaping the backslash with another backslash <DOMAINNAME\\dbuser> would also work.
The host name xp3c used in the examples above works in a workgroup environment, it could (should?) be a full FQDN like xp3c.mydomain.com in a NT domain environment.
In the source directory freetds-0.82/src/apps is the shell script "osql" that attempts to automatically verify the ODBC setup. It checks odbc.ini, odbcinst, and, optionally, freetds.conf, then execute isql (assume it's unixODBC's isql). Syntax: osql -S server -U user -P password.
cd freetds-0.82/src/apps
./osql -S xp3c -U dbuser -P dbpass
On some systems (RISC) the drivers in /usr/local/lib/ may have the extension .sl rather than .so for shared libraries.
====Ms SQL Server====
====Microsoft SQL Server====
If your SQL Server are using instances, replace <port = 1433> with <instance = MyInstanceName> in your freetds.conf template fragment. Maybe adding the instance name after host in freetds.conf like this: <Server = xp3c\MyInstanceName> would aid too.
If your SQL Server are using instances, replace <port = 1433> with <instance = MyInstanceName> in your freetds.conf template fragment. Maybe adding the instance name after host in freetds.conf like this: <Server = xp3c\MyInstanceName> would aid too.
From SQL Server 2000 TDS version 8.0 should be used. Add the line <tds version = 8.0> in your template fragment for freetds.conf
From SQL Server 2000 TDS version 8.0 should be used. Add the line <tds version = 8.0> in your template fragment for freetds.conf
Microsoft SQL Server might not allow the db system user "sa" to connect from outside the server, create another account with proper permissions.
Express edition have remote access disabled by default. Can be changed in the menu "Surface Area Configuration". [http://support.microsoft.com/kb/914277 More info here]
Express edition have remote access disabled by default. Can be changed in the menu "Surface Area Configuration". [http://support.microsoft.com/kb/914277 More info here]
