K
kirchner
Guest
Hello Craig, >> q1) is it expected that one 4gl connect should spawn multiple odbc connections into sql server (in our case 4)? By default yes. DataServer will create one "read/write" connection through which it will route any data modification operations as well any non-NO-LOCK queries. Keep in mind some (maybe all) SHARE-LOCK queries might be downgraded to NO-LOCK depending on configuration. This one connection if refered as the "Master Connection" in the dataserv.lg file. On top of that you will usually have 5 extra connections for NO-LOCK queries, those are the "Firehose Connections" or "Secondary Connections" depending on where you look at. More can be created on demand, I've seen a client with around 30 connection per prowin32 session. You can control whether those connections are created and how many of them, but if you disable them or limit their usage performance will usually suffer. >> q2) how do you get all of the connections to have read-committed? AFAIK you don't. But again, when you use SHARE- or EXCLUSIVE-LOCK the operations will be routed through the master connection so that's the one you need to watch out for. I've never seen anything but NO-LOCK queries through secondary connections and NO-LOCK is pretty much the same as read uncommitted. >> q3) any other ideas why it stalls trying write data back to sql server? Hard to tell without looking, but check for blocked stuff in SQL Server. Maybe some other session has an UPDATE lock on the same resource and you are waiting for a conversion from U to X lock. Do you get any useful error message when you crash?
Continue reading...
Continue reading...