I'm writting an application NT service that query and update data from SapDB odbc source.
1) My application use only one connection to datasource but many request (statement) may be run in a same time (multiple threads). Does anybody know if I should use a connection per thread, or if nothing will change.
Use one connection per thread. SAP Db allows only one active query per connection, so all the other threads will block until the query is finished. (Query being used rather loosely as one network request. Executing a SELECT and fetching the values consists of several network requests)
2) I saw in DBMGui a number named "waits for logwritter", this number is very high for me, is that normal or may it be a weakness of my application.
Maybe you're running in autocommit mode. This is almost always a bad idea and very slow on SAP DB.
3) My service is running on same server than SapDB kernel, there is no dependance between those services. when I shutdown my server, all my ODBC/Sql command run an exception. This does not occurs if I stop my service before shutdown. How can I solve that ? I can not ask the administrator to stop services one by one before any shutdown if he want my application stop well.
Isn't there some API where you can set dependencies between services? ChangeServiceConfig has a parameter dependencies, where you can name services that must start before your own. I don't know if this implies that your service gets stopped before the dependent services.
Daniel Dittmar
-- Daniel Dittmar SAP DB, SAP Labs Berlin [EMAIL PROTECTED] http://www.sapdb.org
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
