Logging, Restart and Commit options

DataPipe Search and Replace: Online Help Logging, Restart and Commit options	Submit feedback on this topic
Home Menus: File Edit Options (Logging, Restart & Commit) Tools Help Tabs: Query Sample data Transforms Preview changes Go

This dialog controls logging, restart and cursor options.

Logging

No logging

Errors are not logged to a file. This is the default.

Log actions to file

Actions such as job start and user name, job end, restart parameters, the query being used, and any erroneous records are all appended to the log file. A typical log file looks like this:

DataPipe Log File

date,time,level,message
2002-09-11,13:37:00,Info,Log file started
2002-09-11,13:37:00,Info,Job started by [Simon Carter]
2002-09-11,13:45:21,Info,Restarting at record 2
2002-09-11,13:37:06,Error,Invalid column value set on row 10, column "price"
Old Value: <NULL>
New Value: AAAAAAAAAAAA
Error: Type mismatch
2002-09-11,13:43:06,Info,Complete. 70 rows processed
2002-09-11,13:43:06,Info,End of job

Restart

No restart

All records are processed. This is the default.

Restart from record

DataPipe starts changes from the specified record. This can be used to restart a job that you cancelled.

Cursor and Lock options

Note: DataPipe always moves forward through a result set, so it does not require options that provide bi-directional scrolling.

Cursor location

Determines whether to use a client-side or server-side cursor library. DataPipe's default is Use Server.

A client-side cursor offers more flexibility. All data is retrieved to the local machine and then operated on there, allowing operations not normally supported by servers like sorting and resorting the data and additional filtering. SQL statements are executed at the server, so for statements that restrict the result set with a WHERE clause, only the reduced result set is retrieved to a local cursor.

A server-side cursor offers less flexibility, but may be more advantageous (or necessary) for large result sets. Using a server-side cursor becomes necessary when the sheer size of a result set exceeds the available disk space that would be needed to create the client-side cursor. Also, many servers only support unidirectional cursors. This would preclude moving the record pointer in the dataset backward (even one record) through the result set.

Cursor type

Indicates the type of cursor used for the record set when it is opened. Cursor type affects directional scrolling through a record set and the visibility of changes made by other users. DataPipe's default is Dynamic.

Cursor Type	Meaning
Unspecified	A specific cursor type has not yet been specified.
Forward Only	Forward-only cursor in which you can only scroll forward; better performance because only requires single through record set.
Keyset	Keyset cursor; records added by other users are not visible; records deleted by other users are inaccessible.
Dynamic	Dynamic cursor; data modifications, deletions, and insertions by other users are visible; scrolling forward and back allowed.
Static	Static cursor; static copy of records; data changes by other users not visible; used mostly for reporting.

Note: Only Static is supported if the Cursor Location is set to Use Client.

Note: If the requested cursor type is not supported by the provider, the provider may return another cursor type.

Lock type

Specifies the type of record lock used during editing. DataPipe's default is Optimistic.

Lock Type	Meaning
Unspecified	A specific lock type has not been specified or determined. The provider will use the default locking scheme.
Read Only	Read-only; the current execution cannot modify data.
Pessimistic	Pessimistic locks; locks instantiated on a record-by-record basis when edit mode is applied to a record.
Optimistic	Optimistic locks; locked are initiated on a record-by-record basis, but only when updates are applied and a record is being updated.
Batch Optimistic	Optimistic batch updates; used for batch update mode rather than immediate update mode.

Note: To use a specific locking scheme, the provider and database type must support that locking scheme. Use Unspecified to have the provider use the default locking scheme. Use the Lock Type Batch Optimistic to open a record set in batch update mode.