I have simple script:

for i in {1..1000}
do
    isql -v -k "Driver={ODBC Driver 17 for SQL Server};Server=mssqlserver,1282;Database=dbname;UID=user;PWD=xxx;Encrypt=no" >> aaa.log &
done

We upgraded OS from RHEL 7.9 to 8.10. ODBC drivers installed: 11, 13, 17. Now, when I execute it 99% of the connections are OK, BUT some of them end in error: > SQL> [Microsoft][ODBC Driver 13 for SQL Server]TCP Provider: Error code 0x2746 [Microsoft][ODBC Driver 13 for SQL Server]Client unable to establish connection Such amount of connections are needed in one of SAS programs. 100% of successful connections were in the RHEL 7.9 release. Can you advice if there is a parameter in Linux, or maybe some ODBC, OPENSSL to have it working again? I have tried rolling back to RHEL 7.9 and the script is working without any issues.

I have a vague recollection that Firebird's isql utility will in some situations make an exclusive connection to the database, meaning that any other connection attempts will be refused. I fail to find information about this. Can anyone explain in which situations this happens, and in particular how I can make sure it does NOT happen? My intended usage is to execute some commands/queries in a scheduled task, and I don't want to run the risk of blocking other database work while this task is executing. From a few simple tests it seems like I get an exclusive connection, i.e. no other connections are allowed, when there are no other connections present. Conversely, if there are other connections when isql connects, isql's connection doesn't block other connections. I tested this with Firebird 3.0.4 in superserver mode and FlameRobin, using the same database alias for both isql and FlameRobin connections. The alias is defined with an absolute local file path. Should I include host and port to ensure that isql always connects through the superserver (allowing other connections) rather than opening the file directly (blocking other connections)?

How can I check the previous command line history in sybase command line?

I am wondering if it is possible to pass parameters to an SQL script from within sybase's isql utility. For example, I'd like to store a select statement in the file the_script.sql that would look something like select col_1, col_2, etc from table where cond1 > $param1 and cond2 < $param2 Then, with that file, I'd like to "execute" it from isql with :r the_script.sql 900 20 with the expectation that $param1 is repleaced with 900 and $param2 with 20. Is there a possibility to achieve what I want?

I have a third-party Sybase database, which my users would like to connect to and query from a Linux box, using [iSQL](http://isql.sourceforge.net/) . I have installed [UnixODBC](http://www.unixodbc.org/) and [FreeTDS](http://www.freetds.org/) . As it is third-party database however, I am not able to perform any GRANTs. The query fails with iSQL on Linux: [unixODBC][FreeTDS][SQL Server]ASA Error -121: Permission denied: you do not have permission to use the "CREATE PROCEDURE" statement It appears that the actual SQL that is getting sent by iSQL is CREATE PROCEDURE AS . I have read the iSQL and FreeTDS manpages but there is no hint in there about how to disable this behavior. This works OK in Python: >>> import Sybase >>> db = Sybase.connect('host:port', 'user', 'password', 'db') >>> c = db.cursor() >>> c.execute('select table_name from systable') >>> len(c.fetchall()) 570 So I believe I have installed the Sybase client libraries correctly. Before I recommend this solution instead, can I as a DBA do anything about fixing iSQL?

The default output (text) width in sybase isql is 80. It can be changed with the -w flag when isql is started on a command line: isql -w 200 -S... -U... -P... Now, I am wondering if there is a possibility to change the text width when I am already connected. I would have expected something like 1> set columnwidth 200 2> go or something similar. Yet, in the documentation I am unable to find something in this direction. So, does that mean that this is impossible or am I looking in the wrong place?