tsql(1) [debian man page]
tsql(1) FreeTDS Utilities tsql(1) NAME
tsql - utility to test FreeTDS connections and queries SYNOPSIS
tsql { -S servername [-I interface] | -H hostname -p port } -U username [-P password] [-o options] tsql -C DESCRIPTION
tsql is a diagnostic tool provided as part of FreeTDS. It uses the TDS protocol directly to connect to Sybase or Microsoft SQL Servers, and allows the user to issue queries that test the capabilities of FreeTDS. tsql is *not* a replacement for a complete isql, such as sqsh (www.sqsh.org). It is designed to rely on the lowest level FreeTDS library, tdslib, as a way to isolate potential bugs in the protocol implementation. tsql can be run in two ways, one which uses the freetds.conf and one which connects directly using the server's hostname and port. When -S is used, FreeTDS uses the freetds.conf (or equivalent) and environment variables in the normal way to determine the server's ip address and port. You can use -I to specify a filename, overriding FreeTDS's configuration file search algorithm. The -H and -p parameters are provided especially for troubleshooting new configurations (or servers). Use of these parameters causes FreeTDS to ignore any freetds.conf and environment variables. OPTIONS
-S servername the Database Server to which to connect. -I interface a freetds.conf or interfaces file describing servername -H hostname the DNS hostname of the server -p port the port at which SQL Server is listening -U username database login name. If username is not provided, a domain login is attempted for TDS 7+ connections. -P password database password. -L list server "instances" (with -H) -C prints some of the compile-time configuration parameters. -o options apply the options specified to every command. f No footer [result count] h No header [titles] t Print time v Print version q Quiet NOTES
Typing "exit", "quit", or "bye" (or ^D) exits tsql. Typing "version" displays the TDS protocol version. Command batches may be separated with "go" or "GO". If "GO", the version string is reported before executing the batch. After prompting for the password, tsql will attempt to connect to the remote server. tsql displays a counter indicating the number of seconds that it is attempting to connect. Typically, tsql should immediately respond with a '1>' prompt. If you see the counter (1, 2, 3, ...), most likely tsql is unable to connect to the indicated server. If you can connect with "tsql -S servername", your basic FreeTDS installation is working. If you have suggestions for ways to make tsql more useful as a diagnostic tool, please recommend them to the FreeTDS mailing list for con- sideration. HISTORY
tsql first appeared in FreeTDS 0.60. AUTHORS
The tsql utility was written by Brian Bruns. BUGS
Several, to be sure, now that it's documented. :) doc 13 November 2011 tsql(1)
Check Out this Related Man Page
DBIx::Class::Storage::DBI::ODBC::Microsoft_SQL_Server(3)User Contributed Perl DocumentatioDBIx::Class::Storage::DBI::ODBC::Microsoft_SQL_Server(3) NAME
DBIx::Class::Storage::DBI::ODBC::Microsoft_SQL_Server - Support specific to Microsoft SQL Server over ODBC DESCRIPTION
This class implements support specific to Microsoft SQL Server over ODBC. It is loaded automatically by DBIx::Class::Storage::DBI::ODBC when it detects a MSSQL back-end. Most of the functionality is provided from the superclass DBIx::Class::Storage::DBI::MSSQL. USAGE NOTES
Basic Linux Setup (Debian) sudo aptitude install tdsodbc libdbd-odbc-perl unixodbc In case it is not already there put the following (adjust for non-64bit arch) in "/etc/odbcinst.ini": [FreeTDS] Description = FreeTDS Driver = /usr/lib/x86_64-linux-gnu/odbc/libtdsodbc.so Setup = /usr/lib/x86_64-linux-gnu/odbc/libtdsS.so UsageCount = 1 Set your $dsn in connect_info as follows: dbi:ODBC:server=<my.host.name>;port=1433;driver=FreeTDS;tds_version=8.0 If you use the EasySoft driver (<http://www.easysoft.com>): dbi:ODBC:server=<my.host.name>;port=1433;driver=Easysoft ODBC-SQL Server Basic Windows Setup Use the following $dsn for the Microsoft ODBC driver: dbi:ODBC:driver={SQL Server};server=SERVERSQL_SERVER_INSTANCE_NAME And for the Native Client: dbi:ODBC:driver={SQL Server Native Client 10.0};server=SERVERSQL_SERVER_INSTANCE_NAME Go into Control Panel -> System and Security -> Administrative Tools -> Data Sources (ODBC) to check driver names and to set up data sources. Use System DSNs, not User DSNs if you want to use DSNs. If you set up a DSN, use the following $dsn for connect_info: dbi:ODBC:dsn=MY_DSN MULTIPLE ACTIVE STATEMENTS
The following options are alternative ways to enable concurrent executing statement support. Each has its own advantages and drawbacks and works on different platforms. Read each section carefully. For more details about using MAS in MSSQL over DBD::ODBC see this excellent document provided by EasySoft: <http://www.easysoft.com/developer/languages/perl/multiple-active-statements.html>. In order of preference, they are: o mars o dynamic_cursors o server_cursors METHODS
connect_call_use_mars Use as: on_connect_call => 'use_mars' in your connection info, or alternatively specify it directly: Your::Schema->connect ( $original_dsn . '; MARS_Connection=Yes', $user, $pass, \%attrs, ) Use to enable a feature of SQL Server 2005 and later, "Multiple Active Result Sets". See "Does DBD::ODBC support Multiple Active Statements?" in DBD::ODBC::FAQ for more information. This does not work on FreeTDS drivers at the time of this writing, and only works with the Native Client, later versions of the Windows MS ODBC driver, and the Easysoft driver. connect_call_use_dynamic_cursors Use as: on_connect_call => 'use_dynamic_cursors' Which will add "odbc_cursortype => 2" to your DBI connection attributes, or alternatively specify the necessary flag directly: Your::Schema->connect (@dsn, { ... odbc_cursortype => 2 }) See "odbc_cursortype" in DBD::ODBC for more information. If you're using FreeTDS, "tds_version" must be set to at least 8.0. This will not work with CODE ref connect_info's. WARNING: on FreeTDS (and maybe some other drivers) this will break "SCOPE_IDENTITY()", and "SELECT @@IDENTITY" will be used instead, which on SQL Server 2005 and later will return erroneous results on tables which have an on insert trigger that inserts into another table with an "IDENTITY" column. WARNING: on FreeTDS, changes made in one statement (e.g. an insert) may not be visible from a following statement (e.g. a select.) WARNING: FreeTDS versions > 0.82 seem to have completely broken the ODBC protocol. DBIC will not allow dynamic cursor support with such versions to protect your data. Please hassle the authors of FreeTDS to act on the bugs that make their driver not overly usable with DBD::ODBC. connect_call_use_server_cursors Use as: on_connect_call => 'use_server_cursors' May allow multiple active select statements. See "odbc_SQL_ROWSET_SIZE" in DBD::ODBC for more information. Takes an optional parameter for the value to set the attribute to, default is 2. WARNING: this does not work on all versions of SQL Server, and may lock up your database! At the time of writing, this option only works on Microsoft's Windows drivers, later versions of the ODBC driver and the Native Client driver. AUTHOR
See "AUTHOR" in DBIx::Class and "CONTRIBUTORS" in DBIx::Class. LICENSE
You may distribute this code under the same terms as Perl itself. perl v5.18.2 2013-12-16 DBIx::Class::Storage::DBI::ODBC::Microsoft_SQL_Server(3)