Hi,
Setting the Witango datasource life to 0 and enabling pooling is definitely quicker. The only problem I have come across is if there is a separate insert action and then try to retrieve the new id of the inserted row in a selection action immediately after, the select falls to return the id because the connection has been closed. Combining the insert and select statements in a DirectDBMS should be the solution. Ted ________________________________ From: Robert Garcia [mailto:[email protected]] Sent: Friday, October 23, 2009 3:27 AM To: [email protected] Subject: Re: Witango-Talk: sql server 2005 odbc pooling Pooling is done within .net, and pooling is done similar to how witango uses persistent connections. I would try using Datasource life on witango to 30 or so, and then turn pooling off. Then I would test with pooling on and witango datasource life at 0, and see which performs better, but I wouldn't use with both on. -- Robert Garcia President - BigHead Technology VP Application Development - eventpix.com 13653 West Park Dr Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 [email protected] - [email protected] http://bighead.net/ - http://eventpix.com/ On Oct 22, 2009, at 4:55 PM, Ted Wolfley wrote: Hi, Came across an article that suggests boasting application connection speed for the sql server odbc by enabling pooling in the sql server odbc driver. The sql server odbc driver installs with pooling off. Has anyone tried enabling with Witango? witango 5.5 on window 2003 32-bit sql server 2005 x64 on windows 2003 x64 Thanks. Ted ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
