freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: Frediano Ziglio <freddy77 AT gmail.com>
- To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
- Subject: Re: [freetds] [FreeTDS] connection pool
- Date: Thu, 1 Sep 2016 11:24:47 +0100
2016-09-01 1:53 GMT+01:00 Xiaobiao Yin <xiaobiaoyin AT outlook.com>:
> Hi Frediano
>
> Thank you really.
>
> In my case, I have to insert the rows to table one by one.
>
> For the connection pooling, I got the information from the User Guide.
>
> http://www.freetds.org/userguide/tdspool.htm,
>
> The FreeTDS connection pool currently only supports TDS version 4.2.
>
Oh... thanks to point it out, this page is out of date unfortunately.
Basically no 5.0 (Sybase), no encryption, SQL username/passwords.
>
> If FreeTDS 1.0 supports protocol 7.2 with some limitations, where can I
> find the
>
> limitation's description, so that I can identify if it will affect my case.
>
>
> BTW, is there any sample code for connection pooling?
>
Beside protocol version pool examples should work.
>
> Thanks in advance
>
> Eric
>
> ________________________________
> From: FreeTDS <freetds-bounces AT lists.ibiblio.org> on behalf of Frediano
> Ziglio <freddy77 AT gmail.com>
> Sent: Wednesday, August 31, 2016 9:18 PM
> To: FreeTDS Development Group
> Subject: Re: [freetds] [FreeTDS] connection pool
>
> 2016-08-31 11:35 GMT+01:00 Xiaobiao Yin <xiaobiaoyin AT outlook.com>:
>> Hi Experts
>>
>>
>> I use FreeTDS (linux) to communicate with a SQL server 2005 in Windows,
>>
>> and tried to use [dbcmd() and dbsqlexec()] 100 times to insert 1 item to
>> database tables.
>>
>> The performance is that one insert statement consumes about 2~3ms.
>>
>>
>> I know there is a so called Connection pool, but it only support TDS
>> 4.2 while SQL server need TDS 7.2.
>>
>>
>> So in order to optimize the performance, I may need to open 2 or more
>> connections, it is a little hard to
>>
>> control these connections.
>>
>>
>> My question is that are there some ways to optimize the performace.
>>
>> The target should be 1ms per 1 insert statement.
>>
>>
>> Any suggetions are welcome.
>>
>>
>> Thanks
>>
>> Eric
>>
>
>
> It's not clear if the problem is application or connections.
> If you have one application that needs to insert rows into a table
> it's better to batch the inserts instead of using a query for each
> row.
> If you have multiple process each needing to connect to database and
> insert a row then would be better to use a connection pooling. The
> connection pooling included in FreeTDS 1.0 supports protocol 7.2 with
> some limitations.
>
Frediano
-
Re: [freetds] [FreeTDS] connection pool,
Thompson, William, 09/01/2016
- Re: [freetds] [FreeTDS] connection pool, Xiaobiao Yin, 09/01/2016
- Re: [freetds] [FreeTDS] connection pool, Xiaobiao Yin, 09/02/2016
-
Re: [freetds] [FreeTDS] connection pool,
matthew . green, 09/02/2016
- Re: [freetds] [FreeTDS] connection pool, Eric Yin, 09/04/2016
- <Possible follow-up(s)>
-
Re: [freetds] [FreeTDS] connection pool,
Frediano Ziglio, 09/01/2016
- Re: [freetds] [FreeTDS] connection pool, Xiaobiao Yin, 09/01/2016
Archive powered by MHonArc 2.6.24.