The freetds.log file was overloading the system, so I changed the debug flags in /etc/freetds.conf :
; dump file = /tmp/freetds.log
#; debug flags = 0xffff
; debug flags = 0x80
How do I restart freetds or unixodbc? Nothing is taking effect, even when I comment out the dump file = /tmp/freetds.log line.
With the mysql shell, you can get vertical output when executing interactive queries by ending them with \G instead of ;.
For example:
mysql> select * from foo limit 1\G
*************************** 1. row ***************************
sid: foo
login: bar
1 row in set (0.00 sec)
Is it possible to do the same using fisql from FreeTDS?
Alternatively, I will accept an answer that can recommend a better UNIX-compatible command line interface to SQL Server that has this capability.
Thanks!
I'm working on a Python project that uses DSN-less connections with SQLAlchemy / pyodbc / unixODBC / FreeTDS to fetch data from a SQL Server database. Now I would like to set client charset directly in the connection string which is not possible in FreeTDS versions prior to 0.91.
Unfortunately 0.91 is not available in any PPA or as a deb file and as my compiling skills are quite lacking I haven't been able successfully compile it directly from source.
A user over at the Ubuntu Forums seems to have the same problem.
So, how would I go about compiling FreeTDS 0.91 on Ubuntu 11.04 x64? Any help would be greatly appreciated.
I'm using the FreeTDS driver with DBD::Sybase, connecting to an MS SQL Server. When I query certain values of certain records, I get this error:
DBD::Sybase::st fetchrow_arrayref failed: OpenClient message: LAYER = (0) ORIGIN = (0) SEVERITY = (9) NUMBER = (99)
Server , database
Message String: WARNING! Some character(s) could not be converted into client's character set. Unconverted bytes were changed to question marks ('?').
This seems to happen for records that contain special Windows character-set characters, such as curly quotes, copied and pasted from people's Outlook and Word messages.
Unfortunately, I do not have any control of this database; sanitizing the input on the way in is obviously the way to go, but is not available to me.
What FreeTDS settings do I need to change to be able to successfully query these records?
Additional information:
The query works fine from tsql. I only get this error through Perl's DBD::Sybase interface. (Should I test through something else? I don't have the expertise yet to install PHP or Python. I've got jTDS and can use it, but I think that's a completely different implementation, not an interface to FreeTDS.)
Adding
client charset = UTF-8
to my freetds.conf file results in "Out of memory!" printed to STDERR.
I've got SQL server running on a machine which is not in a domain, and which is not operating in mixed mode (it's running with "Windows Authentication").
I'm trying to connect to it from a Linux web server running freetds via TCP/IP, using NTLM to authenticate.
The firewall on the SQL server is very restrictive. 1433 is open to my web server, but I'm getting conflicting information from the web on what additional ports (TCP/UDP) are needed for NTLM to succeed. It is currently fail; I can talk on 1433 to request NTLM, but the actual authentication always fails.
One source says 137, 138, 139, but those are just the NetBIOS ports. Do I really need those? Another source says 135. Still others seem to say 1434... I can't make heads or tails of it. Dammit Jim, I'm a programmer, not a network administrator!
EDIT:
The exact error message:
Msg 18452, Level 14, State 1, Server , Line 0
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Msg 20002, Level 9, State -1, Server OpenClient, Line -1
Adaptive Server connection failed
I am attempting to connect with a remote machine username, i.e. 'servername\username'. Some sources recommend that I set up mirrored accounts on the local and remote machines, but the local machine is running Linux, not IIS under Windows.