![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » ElevateDB Technical Support » Product Manuals » ElevateDB Version 2 Manual for Delphi 7 » Using ElevateDB » Connecting Sessions |
User: Administrator (case-insensitive) Password: EDBDefault (case-sensitive)
192.168.0.1 ElevateDBServer
ElevateDBServer 12010/tcp
procedure TMyForm.MySessionBeforeConnect(Sender: TObject); var Registry: TRegistry; begin Registry:=TRegistry.Create; try Registry.RootKey:=HKEY_LOCAL_MACHINE; if Registry.OpenKey('SOFTWARE/My Application',False) then begin if Registry.ReadBool('IsRemote') then begin with MySession do begin SessionType:=stRemote; RemoteAddress:=Registry.ReadString('RemoteAddress'); RemotePort:=Registry.ReadString('RemotePort'); end; end else MySession.SessionType:=stLocal; end else ShowMessage('Error reading connection information '+ 'from the registry'); finally Registry.Free; end; end;
Property | Description |
ForceBufferFlush | Controls whether the session will automatically force the operating system to flush data to disk after every write operation completed by ElevateDB. Please see the Buffering and Caching topic for more information. The default value is False. |
RecordLockProtocol | Controls whether the session will use a pessimistic or optimistic locking model when editing rows via navigational or SQL methods. Please see the Locking and Concurrency topic for more information. The default value is lpPessimistic. |
RecordLockRetryCount | Controls the number of times that the engine will retry a row lock before raising an exception. This property is used in conjunction with the RecordLockWaitTime property. The default value is 15 retries. |
RecordLockWaitTime | Controls the amount of time, in milliseconds, that the engine will wait in-between row lock attempts. This property is used in conjuction with the RecordLockRetryCount property. The default value is 100 milliseconds. |
RecordChangeDetection | Controls whether the session will detect changes to a row during editing or deletion and issue an error if the row has changed since it was last cached. Please see the Change Detection topic for more information. The default value is False. |
KeepConnections | Controls whether temporary TEDBDatabase components are kept connected even after they are no longer needed. This property has no obvious effect upon a local session, but can result in tremendous performance improvements for a remote session, therefore it defaults to True and should be left as such in most cases. |
KeepTablesOpen | Controls whether the physical tables opened within the session are kept open even after they are no longer being used by the application. Setting this property to True can dramatically improve the performance of SQL statements and any other operations that involve constantly opening and closing the same tables over and over. |
SQLStmtCacheSize | Controls how many SQL statements can be cached in memory for each open database in the session. Caching SQL statements improves the performance of ElevateDB by avoiding very expensive preparation/un-preparation cycles. The default value is 0, which means that SQL statements will not be cached for the session. If a session needs to free any cached SQL statements, it can do so at any time by calling the TEDBSession FreeCachedSQLStmts method. |
FuncProcCacheSize | Controls how many functions/procedures can be cached in memory for each open database in the session. Caching functions/procedures improves the performance of ElevateDB by avoiding very expensive preparation/un-preparation cycles. The default value is 0, which means that functions/procedures will not be cached for the session. If a session needs to free any cached functions/procedures, it can do so at any time by calling the TEDBSession FreeCachedFuncProcs method. |
ProgressTimeInterval | Controls the amount of time, in milliseconds, that must elapse between progress updates before ElevateDB will generate a progress event. The default value is 1000 milliseconds, or 1 second. |
ExcludeFromLicensedSessions | Specifies whether the current session should be included in the session license count controlled by the TEDBEngine LicensedSessions property for local sessions, or by the ElevateDB Server for remote sessions. This is useful for situations where you have a utility session that you want to exclude from your own licensing restrictions, such as when a session is used in a thread for performance reasons.![]() |
This web page was last updated on Thursday, November 16, 2023 at 10:39 AM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |