Database Task Parallel Foundation - dbParallel for Oracle & SQL Server

Created Issue: STATE_ID in TPW_PJOB_ARCHIVE ALWAYS=11? [1092]

Sorri — Thu, 10 Jan 2013 15:25:05 GMT

Hello Abel Cheng,

thanks for the nice parallel execution framework - I am just calling the first test procedures.
What is interesting to me is that in the TPW_PJOB_ARCHIVE table the State is always STATE=11 (ARCHIVED), which might not be so interesting as the last STATE it had after executing (was the job succesful or not?).
What is good, is the TPW_TASK_ARCHIVE table, where at least I could see an error message if the task did not run succesful, but also no state.
Can you help me out with this issue?

Greetings

Sven

Updated Wiki: Home

AbelCheng — Thu, 15 Nov 2012 04:10:33 GMT

Project Description
The dbParallel is a Database Task Parallel Foundation that provides database developers an application level support for parallel programming. Being distinct from Oracle 11g R2's DBMS_PARALLEL_EXECUTE parallelism within a query by chunks, dbParallel works more like a .NET Task Parallel Library implemented on database side, it handles the partitioning of the asynchronous job, the scheduling of tasks, state management, and other low-level details in a lightweight implementation.

Get started
A quick example (for Oracle Version)

PROCEDURE TEST_1
AS
    tPJob_ID    PLS_INTEGER;
    tSQL        VARCHAR2(256);
BEGIN
    tPJob_ID := XYZ.TPW_CALL.CREATE_PJOB('App1', 'User1', 'This is test1.');

    tSQL := UTL_LMS.FORMAT_MESSAGE('DBMS_LOCK.SLEEP(%d)', 10);
    XYZ.TPW_CALL.ADD_TASK(tPJob_ID, tSQL, 60, 'Task1 sleep for 10 seconds.');
    
    tSQL := UTL_LMS.FORMAT_MESSAGE('DBMS_LOCK.SLEEP(%d)', 70);
    XYZ.TPW_CALL.ADD_TASK(tPJob_ID, tSQL, 60, 'Task2 sleep for 70 seconds.');

    tSQL := UTL_LMS.FORMAT_MESSAGE('DBMS_LOCK.SLEEP(%d)', 30);
    XYZ.TPW_CALL.ADD_TASK(tPJob_ID, tSQL, 60, 'Task3 sleep for 30 seconds.');

    tSQL := UTL_LMS.FORMAT_MESSAGE('DBMS_LOCK.SLEEP(%d)', 70);
    XYZ.TPW_CALL.ADD_TASK(tPJob_ID, tSQL, 120, 'Task4 sleep for 70 seconds.');

    tSQL := UTL_LMS.FORMAT_MESSAGE('DBMS_LOCK.SLEEP(%d)', 15);
    XYZ.TPW_CALL.ADD_CALLBACK_FOR_SUCCESS(tPJob_ID, tSQL, 180, 'Sleep for 15s if all success.');

    tSQL := UTL_LMS.FORMAT_MESSAGE('DBMS_LOCK.SLEEP(%d)', 25);
    XYZ.TPW_CALL.ADD_CALLBACK_FOR_FAIL(tPJob_ID, tSQL, 180, 'Sleep for 25s if fail.');

    XYZ.TPW_CALL.START_PJOB(tPJob_ID);

    DBMS_OUTPUT.PUT_LINE('New PJob_ID#' || tPJob_ID);
END TEST_1;

The example executes Task1-4 in parallel and when everything is finished, the callback task is executed (in this case callback will be a fail since task 2 failed - timeout).

Features
Following API list of current version reflects the features:

XYZ.TPW_CALL.CREATE_PJOB
Each of the above sample processing units are called a PJob. PJob represents an asynchronous operation. This method returns a pJob Id for below methods (2, 3, 4, 5, 6).
XYZ.TPW_CALL.ADD_TASK
Each pJob contains one or more parallel tasks. Each task is a dynamic SQL. Call the ADD_TASK multiple times to add every parallel tasks into the pJob.
XYZ.TPW_CALL.ADD_CALLBACK_FOR_SUCCESS
This is a optional method. Since a pJob is asynchronous, the callback Task is called to execute a continuation when all the parallel Tasks successfully completed.
XYZ.TPW_CALL.ADD_CALLBACK_FOR_FAIL
This is a optional method. Similar but opposite to previous callback for success, the callback Task for fail is called to execute a continuation when all the parallel Tasks completed but any of them throw out database exception(s).
XYZ.TPW_CALL.START_PJOB
Starts the pJob, scheduling it for execution.
XYZ.TPW_CALL.TRY_CANCEL_PJOB
Try to cancel a scheduled pJob if it hasn't begin to execute.
XYZ.TPW_CALL.START_NEW_SINGLE_TASK
This method encapsulates a series of steps for conveniently creating and starting single task and callback task.
XYZ.TPW_CALL.WAIT_PJOB
Waits for all provided Tasks (parallel subtasks and callback task) of a pJob to complete execution.
To support this method, Oracle version utilizes the signaling mechanism come from SYS.DBMS_ALERT package; SQL Serverv version imitates it by a polling loop at present.

(XYZ is the schema name, it should be replaced by your schema name)

Open the source code of Oracle package TPW_CALL (or SQL Server stored procedures with prefix TPW_CALL_) for detail parameters.

How It's Made

Database Side
Each pJob is added into the Scheduler, and then the State Manager controls every stage in the lifecycle of the pJob.
Windows Service Side
At least one Pump Service must reside in Windows Services (or other hosting environment) act as a dispatcher, as shown in the following figure:

The dispatcher executes each of the provided tasks, possibly in parallel. No guarantees are made about the order in which the tasks execute or how many degree of parallelism. All tuning settings are located in TPW_PUMP_CONFIG table.
Each Task of a pJob is actually executed in the database through its separate connection. In other words, each Task runs in a different database session. Temporary table and transaction can not be expected to cross Tasks.

Service Mode - (Primary Mode | Standby Mode)

A Pump Service always starts up in Standby Mode. Multiple Standby Services can keep running for the same database, one of them will switch to Primary Mode when none Primary Service is active.

Security Model

To create or operate a pJob:
The user must have EXECUTE privilege on the package TPW_CALL - for Oracle version;
(Underlying stored procedures with prefix of "TPW_CALL_" for SQL Server version)
To execute Task's SQL:
As a ultimate executor, the security account of Pump Service must have privileges to execute Tasks' SQL.

Applicability

The original intention of dbParallel is designed for time consuming database processing with one or more independent tasks can run concurrently. Not all processing is suitable for parallelization; for example, if a batch job performs only a small amount of work on each subtask, or it doesn't run for more than one second, then the overhead of parallelization can cause the processing to run more slowly. Besides, some special attention (e.g. locks, deadlocks, and race conditions) can not be ignored.

System Requirements

Supported Databases:
- Oracle (dev and test on version 11g R1 and R2, hasn't try on earlier version);
- SQL Server 2005 or later version;
Windows Service:
.NET Framework 4.0 Client Profile
ADO.NET Provider:
+ Oracle - DataDirect Connect for ADO.NET v3.5
Or - ODP.NET
(the provider can be easily replaced by other provider for Oracle with the source code)
+ SQL Server - .NET Framework build-in SqlClient provider.

At present the dbParallel only support Oracle and SQL Server.

Contribute

Welcome all feedback through the CodePlex project (through comments, patches, or items in the Issue Tracker);
Earnestly request adding support for other databases;

Support

Feel free to use the source in your apps, and products.
For production support, please mark [PROD] in email subject to abelcys@gmail.com.
This project is developed in personal time, the source code support can be available only at night - Easten Time (US & Canada).

Source code checked in, #20526

Project Collection Service Accounts — Mon, 01 Oct 2012 20:30:29 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #20525

Project Collection Service Accounts — Mon, 01 Oct 2012 20:28:33 GMT

Checked in by server upgrade

Updated Release: dbParallel Beta2 (Jul 18, 2012)

AbelCheng — Sun, 22 Jul 2012 02:54:14 GMT

All above releases require .NET Framework 4.0 or later.
The source code solution requires Visual Studio 2010 or later version.
The second download requires DataDirect(V3.5) to connect Oracle;
The third download requires ODP.NET to connect Oracle;

Install instructions can be found in "Setup for Oracle.txt" and "Setup for SQL Server.txt".

Please use the source code if the provider need to be replaced by others. For example ODP.NET: remove reference DDTek.Oracle.dll, add reference Oracle.DataAccess.dll and set conditional compilation symbols "ORACLE;ODP_NET" in DataAccess project properties.

As a derivative library of this project, the dbParallel DataBooster Library (for Oracle & SQL Server) can be obtained at http://databooster.codeplex.com/ separately.

Released: dbParallel Beta2 (Jul 18, 2012)

Sun, 22 Jul 2012 02:54:14 GMT

Updated Release: dbParallel Beta2 (Jul 19, 2012)

abelcheng — Fri, 20 Jul 2012 03:04:16 GMT

Released: dbParallel Beta2 (Jul 19, 2012)

Fri, 20 Jul 2012 03:04:16 GMT

Updated Release: dbParallel (Beta2) (Jul 18, 2012)

abelcheng — Thu, 19 Jul 2012 02:39:04 GMT

All above releases require .NET Framework 4.0 or later.
The source code solution requires Visual Studio 2010 or later version.
The second download requires DataDirect(V3.5) to connect Oracle;
The third download requires ODP.NET to connect Oracle;

Install instructions can be found in "Setup for Oracle.txt" and "Setup for SQL Server.txt".

Please use the source code if the provider need to be replaced by others. For example ODP.NET, add reference Oracle.DataAccess.dll and set conditional compilation symbols "ORACLE;ODP_NET" in DataAccess project properties.

As a derivative library of this project, the dbParallel DataBooster Library (for Oracle & SQL Server) can be obtained at http://databooster.codeplex.com/ separately.

Released: dbParallel (Beta2) (Jul 18, 2012)

Thu, 19 Jul 2012 02:39:04 GMT

All above releases require .NET Framework 4.0 or later.
The source code solution requires Visual Studio 2010 or later version.
The second download requires DataDirect(V3.5) to connect Oracle;
The third download requires ODP.NET to connect Oracle;

Install instructions can be found in "Setup for Oracle.txt" and "Setup for SQL Server.txt".

Please use the source code if the provider need to be replaced by others. For example ODP.NET, add reference Oracle.DataAccess.dll and set conditional compilation symbols "ORACLE;ODP_NET" in DataAccess project properties.

As a derivative library of this project, the dbParallel DataBooster Library (for Oracle & SQL Server) can be obtained at http://databooster.codeplex.com/ separately.

Updated Release: dbParallel Beta2 (Jul 18, 2012)

Abelcheng — Wed, 18 Jul 2012 20:26:21 GMT

All above releases require .NET Framework 4.0 or later.
The source code solution requires Visual Studio 2010 or later version.
The second download requires DataDirect(V3.5) to connect Oracle;
The third download requires ODP.NET to connect Oracle;

Install instructions can be found in "Setup for Oracle.txt" and "Setup for SQL Server.txt".

Please use the source code if the provider need to be replaced by others. For example ODP.NET, add reference Oracle.DataAccess.dll and set conditional compilation symbols "ORACLE;ODP_NET" in DataAccess project properties.

As a derivative library of this project, the dbParallel DataBooster Library (for Oracle & SQL Server) can be obtained at http://databooster.codeplex.com/ separately.

Released: dbParallel Beta2 (Jul 18, 2012)

Wed, 18 Jul 2012 20:26:21 GMT

All above releases require .NET Framework 4.0 or later.
The source code solution requires Visual Studio 2010 or later version.
The second download requires DataDirect(V3.5) to connect Oracle;
The third download requires ODP.NET to connect Oracle;

Install instructions can be found in "Setup for Oracle.txt" and "Setup for SQL Server.txt".

Please use the source code if the provider need to be replaced by others. For example ODP.NET, add reference Oracle.DataAccess.dll and set conditional compilation symbols "ORACLE;ODP_NET" in DataAccess project properties.

As a derivative library of this project, the dbParallel DataBooster Library (for Oracle & SQL Server) can be obtained at http://databooster.codeplex.com/ separately.

Updated Release: dbParallel Beta2 (Jul 18, 2012)

abelcheng — Wed, 18 Jul 2012 20:13:17 GMT

All above releases require .NET Framework 4.0 or later.
The source code solution requires Visual Studio 2010 or later version.
The second download requires DataDirect(V3.5) to connect Oracle;
The third download requires ODP.NET to connect Oracle;

Please use the source code if the provider need to be replaced by others. For example ODP.NET, add reference Oracle.DataAccess.dll and set conditional compilation symbols "ORACLE;ODP_NET" in DataAccess project properties.

As a derivative library of this project, the dbParallel DataBooster Library (for Oracle & SQL Server) can be obtained at http://databooster.codeplex.com/ separately.

Updated Release: dbParallel Beta2 (Jul 18, 2012)

abelcheng — Wed, 18 Jul 2012 06:04:01 GMT

All above releases require .NET Framework 4.0 or later.
The source code solution requires Visual Studio 2010 or later version.
The second download requires DataDirect(V3.5) to connect Oracle;
The third download requires ODP.NET to connect Oracle;

Please use the source code if the provider need to be replaced by others. For example ODP.NET, add reference Oracle.DataAccess.dll and set conditional compilation symbols "ORACLE;ODP_NET" in DataAccess project properties.

As a derivative library of this project, the dbParallel DataBooster Library (for Oracle) can be obtained at http://databooster.codeplex.com/ separately.

Released: dbParallel Beta2 (Jul 18, 2012)

Wed, 18 Jul 2012 06:04:01 GMT

All above releases require .NET Framework 4.0 or later.
The source code solution requires Visual Studio 2010 or later version.
The second download requires DataDirect(V3.5) to connect Oracle;
The third download requires ODP.NET to connect Oracle;

Please use the source code if the provider need to be replaced by others. For example ODP.NET, add reference Oracle.DataAccess.dll and set conditional compilation symbols "ORACLE;ODP_NET" in DataAccess project properties.

As a derivative library of this project, the dbParallel DataBooster Library (for Oracle) can be obtained at http://databooster.codeplex.com/ separately.

Updated Release: dbParallel Beta2 (Jul 18, 2012)

AbelCheng — Wed, 18 Jul 2012 06:00:03 GMT

All above releases require .NET Framework 4.0 or later.
The source code solution requires Visual Studio 2010 or later version.
The second download requires DataDirect(V3.5) to connect Oracle;
The third download requires ODP.NET to connect Oracle;

Please use the source code if the provider need to be replaced by others. For example ODP.NET, add reference Oracle.DataAccess.dll and set conditional compilation symbols "ORACLE;ODP_NET" in DataAccess project properties.

As a derivative library of this project, the dbParallel DataBooster Library (for Oracle) can be obtained at http://databooster.codeplex.com/ separately.

Updated Wiki: Home

AbelCheng — Wed, 18 Jul 2012 05:58:12 GMT

Get started
A quick example (for Oracle Version)

PROCEDURE TEST_1
AS
    tPJob_ID    PLS_INTEGER;
    tSQL        VARCHAR2(256);
BEGIN
    tPJob_ID := XYZ.TPW_CALL.CREATE_PJOB('App1', 'User1', 'This is test1.');

    tSQL := UTL_LMS.FORMAT_MESSAGE('DBMS_LOCK.SLEEP(%d)', 10);
    XYZ.TPW_CALL.ADD_TASK(tPJob_ID, tSQL, 60, 'Task1 sleep for 10 seconds.');
    
    tSQL := UTL_LMS.FORMAT_MESSAGE('DBMS_LOCK.SLEEP(%d)', 70);
    XYZ.TPW_CALL.ADD_TASK(tPJob_ID, tSQL, 60, 'Task2 sleep for 70 seconds.');

    tSQL := UTL_LMS.FORMAT_MESSAGE('DBMS_LOCK.SLEEP(%d)', 30);
    XYZ.TPW_CALL.ADD_TASK(tPJob_ID, tSQL, 60, 'Task3 sleep for 30 seconds.');

    tSQL := UTL_LMS.FORMAT_MESSAGE('DBMS_LOCK.SLEEP(%d)', 70);
    XYZ.TPW_CALL.ADD_TASK(tPJob_ID, tSQL, 120, 'Task4 sleep for 70 seconds.');

    tSQL := UTL_LMS.FORMAT_MESSAGE('DBMS_LOCK.SLEEP(%d)', 15);
    XYZ.TPW_CALL.ADD_CALLBACK_FOR_SUCCESS(tPJob_ID, tSQL, 180, 'Sleep for 15s if all success.');

    tSQL := UTL_LMS.FORMAT_MESSAGE('DBMS_LOCK.SLEEP(%d)', 25);
    XYZ.TPW_CALL.ADD_CALLBACK_FOR_FAIL(tPJob_ID, tSQL, 180, 'Sleep for 25s if fail.');

    XYZ.TPW_CALL.START_PJOB(tPJob_ID);

    DBMS_OUTPUT.PUT_LINE('New PJob_ID#' || tPJob_ID);
END TEST_1;

The example executes Task1-4 in parallel and when everything is finished, the callback task is executed (in this case callback will be a fail since task 2 failed - timeout).

Features
Following API list of current version reflects the features:

XYZ.TPW_CALL.CREATE_PJOB
Each of the above sample processing units are called a PJob. PJob represents an asynchronous operation. This method returns a pJob Id for below methods (2, 3, 4, 5, 6).
XYZ.TPW_CALL.ADD_TASK
Each pJob contains one or more parallel tasks. Each task is a dynamic SQL. Call the ADD_TASK multiple times to add every parallel tasks into the pJob.
XYZ.TPW_CALL.ADD_CALLBACK_FOR_SUCCESS
This is a optional method. Since a pJob is asynchronous, the callback Task is called to execute a continuation when all the parallel Tasks successfully completed.
XYZ.TPW_CALL.ADD_CALLBACK_FOR_FAIL
This is a optional method. Similar but opposite to previous callback for success, the callback Task for fail is called to execute a continuation when all the parallel Tasks completed but any of them throw out database exception(s).
XYZ.TPW_CALL.START_PJOB
Starts the pJob, scheduling it for execution.
XYZ.TPW_CALL.TRY_CANCEL_PJOB
Try to cancel a scheduled pJob if it hasn't begin to execute.
XYZ.TPW_CALL.START_NEW_SINGLE_TASK
This method encapsulates a series of steps for conveniently creating and starting single task and callback task.
XYZ.TPW_CALL.WAIT_PJOB
Waits for all provided Tasks (parallel subtasks and callback task) of a pJob to complete execution.
To support this method, Oracle version utilizes the signaling mechanism come from SYS.DBMS_ALERT package; SQL Serverv version imitates it by a polling loop at present.

(XYZ is the schema name, it should be replaced by your schema name)

Open the source code of Oracle package TPW_CALL (or SQL Server stored procedures with prefix TPW_CALL_) for detail parameters.

How It's Made

Database Side
Each pJob is added into the Scheduler, and then the State Manager controls every stage in the lifecycle of the pJob.
Windows Service Side
At least one Pump Service must reside in Windows Services (or other hosting environment) act as a dispatcher, as shown in the following figure:

Service Mode - (Primary Mode | Standby Mode)

A Pump Service always starts up in Standby Mode. Multiple Standby Services can keep running for the same database, one of them will switch to Primary Mode when none Primary Service is active.

Security Model

To create or operate a pJob:
The user must have EXECUTE privilege on the package TPW_CALL - for Oracle version;
(Underlying stored procedures with prefix of "TPW_CALL_" for SQL Server version)
To execute Task's SQL:
As a ultimate executor, the security account of Pump Service must have privileges to execute Tasks' SQL.

Applicability

System Requirements

Supported Databases:
- Oracle (dev and test on version 11g R1 and R2, hasn't try on earlier version);
- SQL Server 2005 or later version;
Windows Service:
.NET Framework 4.0 Client Profile
ADO.NET Provider:
+ Oracle - DataDirect Connect for ADO.NET v3.5
Or - ODP.NET
(the provider can be easily replaced by other provider for Oracle with the source code)
+ SQL Server - .NET Framework build-in SqlClient provider.

At present the dbParallel only support Oracle and SQL Server.

Contribute

Welcome all feedback through the CodePlex project (through comments, patches, or items in the Issue Tracker);
Earnestly request adding support for other databases;

Documentation

To be prepared ...

Support

Updated Wiki: Home

AbelCheng — Wed, 18 Jul 2012 05:52:56 GMT

Get started
A quick example (for Oracle Version)

PROCEDURE TEST_1
AS
    tPJob_ID    PLS_INTEGER;
    tSQL        VARCHAR2(256);
BEGIN
    tPJob_ID := XYZ.TPW_CALL.CREATE_PJOB('App1', 'User1', 'This is test1.');

    tSQL := UTL_LMS.FORMAT_MESSAGE('DBMS_LOCK.SLEEP(%d)', 10);
    XYZ.TPW_CALL.ADD_TASK(tPJob_ID, tSQL, 60, 'Task1 sleep for 10 seconds.');
    
    tSQL := UTL_LMS.FORMAT_MESSAGE('DBMS_LOCK.SLEEP(%d)', 70);
    XYZ.TPW_CALL.ADD_TASK(tPJob_ID, tSQL, 60, 'Task2 sleep for 70 seconds.');

    tSQL := UTL_LMS.FORMAT_MESSAGE('DBMS_LOCK.SLEEP(%d)', 30);
    XYZ.TPW_CALL.ADD_TASK(tPJob_ID, tSQL, 60, 'Task3 sleep for 30 seconds.');

    tSQL := UTL_LMS.FORMAT_MESSAGE('DBMS_LOCK.SLEEP(%d)', 70);
    XYZ.TPW_CALL.ADD_TASK(tPJob_ID, tSQL, 120, 'Task4 sleep for 70 seconds.');

    tSQL := UTL_LMS.FORMAT_MESSAGE('DBMS_LOCK.SLEEP(%d)', 15);
    XYZ.TPW_CALL.ADD_CALLBACK_FOR_SUCCESS(tPJob_ID, tSQL, 180, 'Sleep for 15s if all success.');

    tSQL := UTL_LMS.FORMAT_MESSAGE('DBMS_LOCK.SLEEP(%d)', 25);
    XYZ.TPW_CALL.ADD_CALLBACK_FOR_FAIL(tPJob_ID, tSQL, 180, 'Sleep for 25s if fail.');

    XYZ.TPW_CALL.START_PJOB(tPJob_ID);

    DBMS_OUTPUT.PUT_LINE('New PJob_ID#' || tPJob_ID);
END TEST_1;

The example executes Task1-4 in parallel and when everything is finished, the callback task is executed (in this case callback will be a fail since task 2 failed - timeout).

Features
Following API list of current version reflects the features:

XYZ.TPW_CALL.CREATE_PJOB
Each of the above sample processing units are called a PJob. PJob represents an asynchronous operation. This method returns a pJob Id for below methods (2, 3, 4, 5, 6).
XYZ.TPW_CALL.ADD_TASK
Each pJob contains one or more parallel tasks. Each task is a dynamic SQL. Call the ADD_TASK multiple times to add every parallel tasks into the pJob.
XYZ.TPW_CALL.ADD_CALLBACK_FOR_SUCCESS
This is a optional method. Since a pJob is asynchronous, the callback Task is called to execute a continuation when all the parallel Tasks successfully completed.
XYZ.TPW_CALL.ADD_CALLBACK_FOR_FAIL
This is a optional method. Similar but opposite to previous callback for success, the callback Task for fail is called to execute a continuation when all the parallel Tasks completed but any of them throw out database exception(s).
XYZ.TPW_CALL.START_PJOB
Starts the pJob, scheduling it for execution.
XYZ.TPW_CALL.TRY_CANCEL_PJOB
Try to cancel a scheduled pJob if it hasn't begin to execute.
XYZ.TPW_CALL.START_NEW_SINGLE_TASK
This method encapsulates a series of steps for conveniently creating and starting single task and callback task.
XYZ.TPW_CALL.WAIT_PJOB
Waits for all provided Tasks (parallel subtasks and callback task) of a pJob to complete execution.
To support this method, Oracle version utilizes the signaling mechanism come from SYS.DBMS_ALERT package; SQL Serverv version imitates it by a polling loop at present.

(XYZ is the schema name, it should be replaced by your schema name)

Open the source code of Oracle package TPW_CALL (or SQL Server stored procedures with prefix TPW_CALL_) for detail parameters.

How It's Made

Database Side
Each pJob is added into the Scheduler, and then the State Manager controls every stage in the lifecycle of the pJob.
Windows Service Side
At least one Pump Service must reside in Windows Services (or other hosting environment) act as a dispatcher, as shown in the following figure:

Service Mode - (Primary Mode | Standby Mode)

A Pump Service always starts up in Standby Mode. Multiple Standby Services can keep running for the same database, one of them will switch to Primary Mode when none Primary Service is active.

Security Model

To create or operate a pJob:
The user must have EXECUTE privilege on the package TPW_CALL - for Oracle version;
(Underlying stored procedures with prefix of "TPW_CALL_" for SQL Server version)
To execute Task's SQL:
As a ultimate executor, the security account of Pump Service must have privileges to execute Tasks' SQL.

Applicability

System Requirements

Supported Databases:
- Oracle (dev and test on version 11g R1 and R2, hasn't try on earlier version);
- SQL Server 2005 or later version;
Windows Service:
.NET Framework 4.0 Client Profile
ADO.NET Provider:
+ Oracle - DataDirect Connect for ADO.NET v3.5
Or - ODP.NET
(the provider can be easily replaced by other provider for Oracle with the source code)
+ SQL Server - .NET Framework build-in SqlClient provider.

At present the dbParallel only support Oracle and SQL Server.

Contribute

Welcome all feedback through the CodePlex project (through comments, patches, or items in the Issue Tracker);
Earnestly request adding support for other databases;

Documentation

To be prepared ...

Support

Created Release: dbParallel Beta2 (Jul 18, 2012)

AbelCheng — Wed, 18 Jul 2012 05:50:36 GMT

dbParallel for Oracle & SQL Server (Beta 2)

All above releases require .NET Framework 4.0 or later.
The source code solution requires Visual Studio 2010 or later version.
The second download requires DataDirect(V3.5) to connect Oracle;
The third download requires ODP.NET to connect Oracle;

Please use the source code if the provider need to be replaced by others. For example ODP.NET, add reference Oracle.DataAccess.dll and set conditional compilation symbols "ORACLE;ODP_NET" in DataAccess project properties.

As a derivative library of this project, the dbParallel DataBooster Library (for Oracle) can be obtained at http://databooster.codeplex.com/ separately.

Source code checked in, #18048

AbelCheng — Wed, 18 Jul 2012 04:01:50 GMT

Prepare for Beta2.