From 92ff979f880b88863157342de3c47311d9c27805 Mon Sep 17 00:00:00 2001
From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com>
Date: Tue, 11 Jul 2023 13:49:29 -0400
Subject: [PATCH 01/19] Edits to EDB .Net doc
---
...advanced_server_net_connector_overview.mdx | 2 +-
...ling_and_configuring_the_net_connector.mdx | 210 ++++++++----------
.../06_opening_a_database_connection.mdx | 40 ++--
.../07_retrieving_database_records.mdx | 4 +-
.../10_deleting_records_in_a_database.mdx | 2 +-
...red_procedures_in_your_net_application.mdx | 24 +-
.../7.0.4.1/12_using_advanced_queueing.mdx | 86 +++----
...sing_a_ref_cursor_in_a_net_application.mdx | 14 +-
.../7.0.4.1/14_using_plugins.mdx | 25 +--
.../7.0.4.1/15_using_object_types.mdx | 10 +-
.../7.0.4.1/16_scram_compatibility.mdx | 2 +-
..._advanced_server_net_connector_logging.mdx | 9 +-
12 files changed, 206 insertions(+), 222 deletions(-)
diff --git a/product_docs/docs/net_connector/7.0.4.1/03_the_advanced_server_net_connector_overview.mdx b/product_docs/docs/net_connector/7.0.4.1/03_the_advanced_server_net_connector_overview.mdx
index 4c582c1b1f9..138f23121a6 100644
--- a/product_docs/docs/net_connector/7.0.4.1/03_the_advanced_server_net_connector_overview.mdx
+++ b/product_docs/docs/net_connector/7.0.4.1/03_the_advanced_server_net_connector_overview.mdx
@@ -18,7 +18,7 @@ The .NET Connector supports the following frameworks:
## The .NET class hierarchy
-The .NET class hierarchy contains classes that you can use to create objects that control a connection to the EDB Postgres Advanced Server database and manipulate the data stored on the server. The following are just a few of the most commonly used object classes.
+The .NET class hierarchy contains classes that you can use to create objects that control a connection to the EDB Postgres Advanced Server database and manipulate the data stored on the server. The following are a few of the most commonly used object classes.
`EDBConnection`
diff --git a/product_docs/docs/net_connector/7.0.4.1/04_installing_and_configuring_the_net_connector.mdx b/product_docs/docs/net_connector/7.0.4.1/04_installing_and_configuring_the_net_connector.mdx
index 4bf486640ac..6256283cc01 100644
--- a/product_docs/docs/net_connector/7.0.4.1/04_installing_and_configuring_the_net_connector.mdx
+++ b/product_docs/docs/net_connector/7.0.4.1/04_installing_and_configuring_the_net_connector.mdx
@@ -7,51 +7,43 @@ title: "Installing and configuring the .NET Connector"
## Installing the .NET Connector
-You can use the EDB .NET Connector Installer (available [from the EDB website](https://www.enterprisedb.com/software-downloads-postgres)) to add the .NET Connector to your system. After downloading the installer, right-click on the installer icon, and select `Run As Administrator` from the context menu. When prompted, select an installation language and click `OK` to continue to the `Setup` window.
+You can use the EDB .NET Connector Installer (available [from the EDB website](https://www.enterprisedb.com/software-downloads-postgres)) to add the .NET Connector to your system.
-
+1. After downloading the installer, right-click the installer icon, and select **Run As Administrator** from the context menu. When prompted, select an installation language and select **OK** to continue to the Setup window.
-The .NET Connector Installation wizard
+ 
-Click `Next` to continue.
+1. Select **Next**.
-
+ 
-The Installation dialog
+1. Use the Installation Directory dialog box to specify the directory in which to install the connector. Select **Next**.
-Use the `Installation Directory` dialog to specify the directory in which the connector will be installed, and click `Next` to continue.
+ 
-
+1. To start the installation, on the Ready to Install dialog box, select **Next**. Popups confirm the progress of the installation wizard.
-The Ready to Install dialog
+ 
-Click `Next` on the `Ready to Install` dialog to start the installation; popup dialogs confirm the progress of the installation wizard.
+1. When the wizard informs you that it has completed the setup, select **Finish**.
-
+You can also use StackBuilder Plus to add or update the connector on an existing Advanced Server installation.
-The installation is complete
+1. To open StackBuilder Plus, from the Windows **Apps** menu, select **StackBuilder Plus**.
-When the wizard informs you that it has completed the setup, click the `Finish` button to exit the dialog.
+ 
-You can also use StackBuilder Plus to add or update the connector on an existing Advanced Server installation; to open StackBuilder Plus, select `StackBuilder Plus` from the Windows `Apps` menu.
+1. When StackBuilder Plus opens, follow the onscreen instructions.
-
+1. From the Database Drivers node of the tree control, select the **EnterpriseDB.Net Connector** option.
-Starting StackBuilder Plus
+ 
-When StackBuilder Plus opens, follow the onscreen instructions.
-
-Select the `EnterpriseDB.Net Connector` option from the `Database Drivers` node of the tree control.
-
-
-
-Selecting the Connectors installer
-
-Follow the directions of the onscreen wizard to add or update an installation of an EDB Connector.
+1. Follow the directions of the onscreen wizard to add or update an installation of an EDB Connector.
## Configuring the .NET Connector
-Please see the following environment-specific sections for information about configuring the .NET Connector:
+For information about configuring the .NET Connector in each environment, see:
- **Referencing the Library Files.** [General configuration information](#referencing_the_library_files) applicable to all components.
- **.NET 7.0** Instructions for configuring for use with [.NET 7.0](#setup_7_0)
@@ -62,49 +54,47 @@ Please see the following environment-specific sections for information about con
- **.NET Standard 2.1** Instructions for configuring for use with [.NET Standard 2.1](#standard_setup_2_1).
- **.NET EntityFramework Core** Instructions for configuring for use with [.NET EntityFramework Core](#entity_setup).
-
-
### Referencing the library files
To reference library files with Microsoft Visual Studio:
-1. Select the project in the `Solution Explorer`.
-2. Select `Add Reference` from the `Project` menu.
-3. When the `Add Reference` dialog box opens, browse to select the appropriate library files.
-
-Optionally, the library files can be copied to the specified location.
+1. Select the project in the Solution Explorer.
+2. Select **Project > Add Reference**.
+3. In the Add Reference` dialog box, browse to select the appropriate library files.
-Before you can use an EDB .NET class, you must import the namespace into your program. Importing a namespace makes the compiler aware of the classes available within the namespace. The namespace is:
+Optionally, you can copy the library files to the specified location.
- `EnterpriseDB.EDBClient`
+Before you can use an EDB .NET class, you must import the namespace into your program. Importing a namespace makes the compiler aware of the classes available within the namespace. The namespace is `EnterpriseDB.EDBClient`.
-The method you use to include the namespace varies by the type of application you are writing. For example, the following command imports a namespace into an `ASP.NET` page:
+The method you use to include the namespace varies by the type of application you're writing. For example, the following command imports a namespace into an `ASP.NET` page:
- `<% import namespace="EnterpriseDB.EDBClient" %>`
+```text
+ <% import namespace="EnterpriseDB.EDBClient" %>
+```
-To import a namespace into a C# application, write:
+To import a namespace into a C# application, use:
- `using EnterpriseDB.EDBClient;`
+```text
+ using EnterpriseDB.EDBClient;
+```
### .NET framework setup
-The following sections describe the setup for various .NET versions.
+Each .NET version has specific setup instructions.
#### .NET 7.0
-For .NET 7.0, the data provider installation path is:
-
-`C:\Program Files\edb\dotnet\net7.0\`
+For .NET 7.0, the data provider installation path is `C:\Program Files\edb\dotnet\net7.0\`.
You must add the following dependencies to your project:
-`EnterpriseDB.EDBClient.dll`
+- `EnterpriseDB.EDBClient.dll`
-Depending on your application type, you may require to import the namespace into the source code. See [Referencing the library files](#referencing_the_library_files) for this and the other information about referencing the library files.
+Depending on your application type, you might need to import the namespace into the source code. See [Referencing the library files](#referencing_the_library_files) for this and the other information about referencing the library files.
@@ -116,171 +106,163 @@ For .NET 6.0, the data provider installation path is:
You must add the following dependencies to your project:
- `EnterpriseDB.EDBClient.dll`
+- `EnterpriseDB.EDBClient.dll`
-Depending on your application type, you may require to import the namespace into the source code. See [Referencing the library files](#referencing_the_library_files) for this and the other information about referencing library files.
+Depending on your application type, you might need to import the namespace into the source code. See [Referencing the library files](#referencing_the_library_files) for this and the other information about referencing library files.
#### .NET 5.0
-For .NET 5.0, the data provider installation path is:
-
- `C:\Program Files\edb\dotnet\net5.0\`
+For .NET 5.0, the data provider installation path is `C:\Program Files\edb\dotnet\net5.0\`.
You must add the following dependencies to your project:
- `EnterpriseDB.EDBClient.dll`
+- `EnterpriseDB.EDBClient.dll`
-Depending on your application type, you may require to import the namespace into the source code. See [Referencing the library files](#referencing_the_library_files) for this and the other information about referencing the library files.
+Depending on your application type, you might need to import the namespace into the source code. See [Referencing the library files](#referencing_the_library_files) for this and the other information about referencing the library files.
#### .NET Core 3.1
-If you are using .NET Core 3.1, the data provider installation path is:
-
- `C:\Program Files\edb\dotnet\netcoreapp3.1\`
+For .NET Core 3.1, the data provider installation path is `C:\Program Files\edb\dotnet\netcoreapp3.1\`.
The following shared library files are required:
- `EnterpriseDB.EDBClient.dll`
+- `EnterpriseDB.EDBClient.dll`
- `System.Threading.Tasks.Extensions.dll`
+- `System.Threading.Tasks.Extensions.dll`
- `System.Runtime.CompilerServices.Unsafe.dll`
+- `System.Runtime.CompilerServices.Unsafe.dll`
- `System.ValueTuple.dll`
+- `System.ValueTuple.dll`
- `System.Memory.dll`
+- `System.Memory.dll`
-Depending on your application type, you may require to import the namespace into the source code. See [Referencing the library files](#referencing_the_library_files) for this and the other information about referencing the library files.
+Depending on your application type, you might need to import the namespace into the source code. See [Referencing the library files](#referencing_the_library_files) for this and the other information about referencing the library files.
#### .NET Standard 2.0
-For .NET Standard Framework 2.0, the data provider installation path is:
-
- `C:\Program Files\edb\dotnet\netstandard2.0\`
+For .NET Standard Framework 2.0, the data provider installation path is `C:\Program Files\edb\dotnet\netstandard2.0\`.
You must add the following dependencies to your project:
- `EnterpriseDB.EDBClient.dll`
+- `EnterpriseDB.EDBClient.dll`
- `System.Threading.Tasks.Extensions.dll`
+- `System.Threading.Tasks.Extensions.dll`
- `System.Runtime.CompilerServices.Unsafe.dll`
+- `System.Runtime.CompilerServices.Unsafe.dll`
- `System.ValueTuple.dll`
+- `System.ValueTuple.dll`
!!! Note
- If your target framework is .Net Core 2.0, then include the following file in your project:
-
-`System.Threading.Tasks.Extensions.dll`
+ If your target framework is .Net Core 2.0, then include the file `System.Threading.Tasks.Extensions.dll` in your project.
-Depending on your application type, you may require to import the namespace into the source code. See [Referencing the library files](#referencing_the_library_files) for this and the other information about referencing the library files.
+Depending on your application type, you might need to import the namespace into the source code. See [Referencing the library files](#referencing_the_library_files) for this and the other information about referencing the library files.
#### .NET Standard 2.1
-For .NET Standard Framework 2.1, the data provider installation path is:
-
- `C:\Program Files\edb\dotnet\netstandard2.1\`
+For .NET Standard Framework 2.1, the data provider installation path is `C:\Program Files\edb\dotnet\netstandard2.1\`.
The following shared library files are required:
- `EnterpriseDB.EDBClient.dll`
+- `EnterpriseDB.EDBClient.dll`
- `System.Memory.dll`
+- `System.Memory.dll`
- `System.Runtime.CompilerServices.Unsafe.dll`
+- `System.Runtime.CompilerServices.Unsafe.dll`
- `System.Text.Json.dll`
+- `System.Text.Json.dll`
- `System.Threading.Tasks.Extensions.dll`
+- `System.Threading.Tasks.Extensions.dll`
- `System.ValueTuple.dll`
+- `System.ValueTuple.dll`
-Depending on your application type, you may require to import the namespace into the source code. See [Referencing the library files](#referencing_the_library_files) for this and the other information about referencing the library files.
+Depending on your application type, you might need to import the namespace into the source code. See [Referencing the library files](#referencing_the_library_files) for this and the other information about referencing the library files.
-#### .NET EntityFramework Core
+#### .NET Entity Framework Core
-To configure the .NET Connector for use with Entity Framework Core, the data provider installation path is:
+To configure the .NET Connector for use with Entity Framework Core, the data provider installation path is either:
- `C:\Program Files\edb\dotnet\EF.Core\EFCore.PG\net7.0`
+- `C:\Program Files\edb\dotnet\EF.Core\EFCore.PG\net7.0`
- `C:\Program Files\edb\dotnet\EF.Core\EFCore.PG\net6.0`
+- `C:\Program Files\edb\dotnet\EF.Core\EFCore.PG\net6.0`
The following shared library file is required:
- `EnterpriseDB.EDBClient.EntityFrameworkCore.PostgreSQL.dll`
+- `EnterpriseDB.EDBClient.EntityFrameworkCore.PostgreSQL.dll`
!!! Note
- Entity Framework Core can be used with the EnterpriseDB.EDBClient.dll library available in the net7.0 or net6.0 subdirectory.
+ You can use Entity Framework Core with the `EnterpriseDB.EDBClient.dll` library available in the `net7.0` or `net6.0` subdirectory.
See [Referencing the library files](#referencing_the_library_files) for information about referencing the library files.
The following NuGet packages are required:
- `Microsoft.EntityFrameworkCore.Design`
+- `Microsoft.EntityFrameworkCore.Design`
+
+- `Microsoft.EntityFrameworkCore.Relational`
+
+- `Microsoft.EntityFrameworkCore.Abstractions`
- `Microsoft.EntityFrameworkCore.Relational`
- `Microsoft.EntityFrameworkCore.Abstractions`
+For usage information about Entity Framework Core, see the [Microsoft documentation](https://learn.microsoft.com/en-us/ef/core/).
+**Prerequisite**
-For usage information about Entity Framework Core, refer to the Microsoft documentation.
+To open a command prompt:
-**Prerequisite**:
+Select **Tools > Command Line > Developer Command Prompt**.
-Install dotnet-ef (using Command Prompt)
+Install dotnet-ef (using the command prompt),
`dotnet tool install --global dotnet-ef`
**Sample project**
-Create a new Console Application based on .NET 7.0 or .NET 6.0.
+Create a new Console Application based on .NET 7.0 or .NET 6.0..
Add Reference to the following EDB assemblies:
- `EnterpriseDB.EDBClient.EntityFrameworkCore.PostgreSQL.dll`
+- `EnterpriseDB.EDBClient.EntityFrameworkCore.PostgreSQL.dll`
- `EnterpriseDB.EDBClient.dll`
+- `EnterpriseDB.EDBClient.dll`
Add the following NuGet packages:
- `Microsoft.EntityFrameworkCore.Design`
+- `Microsoft.EntityFrameworkCore.Design`
- `Microsoft.EntityFrameworkCore.Relational`
+- `Microsoft.EntityFrameworkCore.Relational`
- `Microsoft.EntityFrameworkCore.Abstractions`
+- `Microsoft.EntityFrameworkCore.Abstractions`
+**Database-first scenario**
-Command Prompt
+Issue the following command to create model classes corresponding to all objects in the specified database:
- `Open Tools` → `Command Line` → `Developer Command Prompt`
+```text
+dotnet ef dbcontext scaffold Host=;Database=;Username=;Password=;Port= EnterpriseDB.EDBClient.EntityFrameworkCore.PostgreSQL -o Models
+```
-**Database first scenario**
+**Code-first scenario**
-Issue the following command to create Model Classes corresponding to all objects in the specified database:
+Add code for defining a DbContext and create, read, update, and delete operations.
-`dotnet ef dbcontext scaffold Host=;Database=;Username=;Password=;Port= EnterpriseDB.EDBClient.EntityFrameworkCore.PostgreSQL -o Models`
-
-**Code first scenario**
-
-Add code for defining a DbContext and create, read, update & delete operations.
-
-Please refer to the Microsoft documentation for further details.
+For further details, see the Microsoft documentation.
Issue the following commands to create the initial database and tables:
- `dotnet ef migrations add InitialCreate --context BloggingContext`
-
- `dotnet ef database update --context BloggingContext`
+```text
+ dotnet ef migrations add InitialCreate --context BloggingContext
+ dotnet ef database update --context BloggingContext
+```
diff --git a/product_docs/docs/net_connector/7.0.4.1/06_opening_a_database_connection.mdx b/product_docs/docs/net_connector/7.0.4.1/06_opening_a_database_connection.mdx
index b7722c72c7e..8f5eb142b23 100644
--- a/product_docs/docs/net_connector/7.0.4.1/06_opening_a_database_connection.mdx
+++ b/product_docs/docs/net_connector/7.0.4.1/06_opening_a_database_connection.mdx
@@ -7,28 +7,30 @@ title: "Opening a database connection"
An `EDBConnection` object is responsible for handling the communication between an instance of EDB Postgres Advanced Server and a .NET application. Before you can access data stored in an EDB Postgres Advanced Server database, you must create and open an `EDBConnection` object.
+## Creating an EDBConnection object
+
You can open a connection using one of the following approaches. In either case, you must import the namespace `EnterpriseDB.EDBClient`.
-- Connection with a data source:
+### Connection with a data source
- 1. Create an instance of the `EDBDataSource` object using a connection string as a parameter to the create method of the `EDBDataSource` class.
+1. Create an instance of the `EDBDataSource` object using a connection string as a parameter to the create method of the `EDBDataSource` class.
- 2. Call the `OpenConnection` method of the `EDBDataSource` object to open a connection.
+2. Call the `OpenConnection` method of the `EDBDataSource` object to open a connection.
- This example shows how to open a connection using a data source:
+This example shows how to open a connection using a data source:
```text
await using var dataSource = EDBDataSource.Create(ConnectionString);
var connection = dataSource.OpenConnection();
```
-- Connection without a data source:
+### Connection without a data source
- 1. Create an instance of the `EDBConnection` object using a connection string as a parameter to the constructor of the `EDBConnection` class.
+1. Create an instance of the `EDBConnection` object using a connection string as a parameter to the constructor of the `EDBConnection` class.
- 2. Call the `Open` method of the `EDBConnection` object to open the connection.
+2. Call the `Open` method of the `EDBConnection` object to open the connection.
- This example shows how to open a connection without a data source:
+This example shows how to open a connection without a data source:
```text
EDBConnection conn = new EDBConnection(ConnectionString);
@@ -36,7 +38,7 @@ You can open a connection using one of the following approaches. In either case,
```
!!! Note
- For `EnterpriseDB.EDBClient 7.0.4` and later, the `EDBDataSource` is recommended to connect to EDB Postgres Advanced Server database or execute SQL directly against it. For more information on data source, see [Npgsql docs](https://www.npgsql.org/doc/basic-usage.html).
+ For `EnterpriseDB.EDBClient 7.0.4` and later, we recommend `EDBDataSource` to connect to EDB Postgres Advanced Server database or execute SQL directly against it. For more information on data source, see the [Npgsql documentation](https://www.npgsql.org/doc/basic-usage.html).
@@ -74,7 +76,7 @@ You can include the following parameters in the connection string:
`Load Role Based Tables`
- Use `Load Role Based Tables` to load table OIDs based on role. This change impacts only the loading of table type OID and not the composite type. Setting this parameter to `true` triggers the new functionality. The default value is `false`.
+ Use `Load Role Based Tables` to load table OIDs based on role. This change affects only the loading of table type OID and not the composite type. Setting this parameter to `true` triggers the new functionality. The default value is `false`.
`MaxPoolSize`
@@ -94,7 +96,7 @@ You can include the following parameters in the connection string:
`No Reset On Close`
-When `Pooling` is enabled and the connection is closed, reopened, and the underlying connection is reused, then some operations are executed to discard the previous connection resources. It is possible to override this behavior by enabling `No Reset On Close`.
+When `Pooling` is enabled and the connection is closed, reopened, and the underlying connection is reused, then some operations are executed to discard the previous connection resources. You can override this behavior by enabling `No Reset On Close`.
`Port`
@@ -120,13 +122,13 @@ When `Pooling` is enabled and the connection is closed, reopened, and the underl
Use `sslmode` to specify an SSL connection control preference. `sslmode` can be:
- `prefer` — Use SSL if possible.
+- `prefer` — Use SSL if possible.
- `require` — Throw an exception if an SSL connection can't be established.
+- `require` — Throw an exception if an SSL connection can't be established.
- `allow` — Connect without SSL. This parameter isn't supported.
+- `allow` — Connect without SSL. This parameter isn't supported.
- `disable` — Don't attempt an SSL connection. This is the default behavior.
+- `disable` — Don't attempt an SSL connection. This is the default behavior.
`SyncNotification`
@@ -217,7 +219,9 @@ namespace EnterpriseDB
Save the file as `EDBConnection-Sample.cs` and compile it with the following command:
-`csc /r:EnterpriseDB.EDBClient.dll /out:Console.exe EDBConnection-Sample.cs`
+```text
+csc /r:EnterpriseDB.EDBClient.dll /out:Console.exe EDBConnection-Sample.cs`
+```
Compiling the sample generates a `Console.exe` file. You can execute the sample code by entering `Console.exe`. When executed, the console verifies that it opened successfully.
@@ -267,6 +271,8 @@ namespace EDBTestClient
Change the database connection string to point to the database that you want to connect to. Then compile the file with the following command:
-`csc /r:EnterpriseDB.EDBClient.dll /out:WinForm.exe WinForm-Example.cs`
+```text
+csc /r:EnterpriseDB.EDBClient.dll /out:WinForm.exe WinForm-Example.cs
+```
This command generates a `WinForm.exe` file in the same folder that the executable was compiled under. Invoking the executable displays a message that the connection was successful.
diff --git a/product_docs/docs/net_connector/7.0.4.1/07_retrieving_database_records.mdx b/product_docs/docs/net_connector/7.0.4.1/07_retrieving_database_records.mdx
index 0240ff776e6..c8c7cc6fb3a 100644
--- a/product_docs/docs/net_connector/7.0.4.1/07_retrieving_database_records.mdx
+++ b/product_docs/docs/net_connector/7.0.4.1/07_retrieving_database_records.mdx
@@ -25,7 +25,7 @@ The results of the SQL statement are retrieved into an `EDBDataReader` object.
Loop through the contents of the `EDBDataReader` object to display the records returned by the query in a `WHILE` loop.
-The `Read()` method advances to the next record (if a record exists) and returns `true` if a record exists. It returns `false` if `EDBDataReader` has reached the end of the result set.
+The `Read()` method advances to the next record (if there is one) and returns `true` if a record exists. It returns `false` if `EDBDataReader` has reached the end of the result set.
```cpp
<% @ Page Language="C#" %>
@@ -62,7 +62,7 @@ private void Page_Load(object sender, System.EventArgs e)
```
-To exercise the sample code, save the code in your default web root directory in a file named `selectEmployees.aspx`. Then, to invoke the program, enter the following URL into a browser: `http://localhost/selectEmployees.aspx`.
+To exercise the sample code, save the code in your default web root directory in a file named `selectEmployees.aspx`. Then, to invoke the program, enter the following URL in a browser: `http://localhost/selectEmployees.aspx`.
## Retrieving a single database record
diff --git a/product_docs/docs/net_connector/7.0.4.1/10_deleting_records_in_a_database.mdx b/product_docs/docs/net_connector/7.0.4.1/10_deleting_records_in_a_database.mdx
index 155fa6a5a1b..8c797af0868 100644
--- a/product_docs/docs/net_connector/7.0.4.1/10_deleting_records_in_a_database.mdx
+++ b/product_docs/docs/net_connector/7.0.4.1/10_deleting_records_in_a_database.mdx
@@ -7,7 +7,7 @@ title: "Deleting records in a database"
You can use the `ExecuteNonQuery()` method of `EDBCommand` to delete records from a database stored on an EDB Postgres Advanced Server host with a `DELETE` statement.
-In the example that follows, the `DELETE` command is stored in the variable `strDeleteQuery`. The code passes the employee number to the `DELETE` command (specified by `EmpNo`). The command is then executed using the `ExecuteNonQuery()` method.
+In the example that follows, the `DELETE` command is stored in the variable `strDeleteQuery`. The code passes the employee number specified by `EmpNo` to the `DELETE` command. The command is then executed using the `ExecuteNonQuery()` method.
```cpp
<% @ Page Language="C#" Debug="true"%>
diff --git a/product_docs/docs/net_connector/7.0.4.1/11_using_spl_stored_procedures_in_your_net_application.mdx b/product_docs/docs/net_connector/7.0.4.1/11_using_spl_stored_procedures_in_your_net_application.mdx
index 97028f3da09..51a2c02f6f6 100644
--- a/product_docs/docs/net_connector/7.0.4.1/11_using_spl_stored_procedures_in_your_net_application.mdx
+++ b/product_docs/docs/net_connector/7.0.4.1/11_using_spl_stored_procedures_in_your_net_application.mdx
@@ -7,8 +7,8 @@ title: "Using SPL stored procedures in your .NET application"
You can include SQL statements in an application in two ways:
-- By adding the SQL statements directly in the .NET application code.
-- By packaging the SQL statements in a stored procedure and executing the stored procedure from the .NET application.
+- By adding the SQL statements directly in the .NET application code
+- By packaging the SQL statements in a stored procedure and executing the stored procedure from the .NET application
In some cases, a stored procedure can provide advantages over embedded SQL statements. Stored procedures support complex conditional and looping constructs that are difficult to duplicate with SQL statements embedded directly in an application.
@@ -38,7 +38,7 @@ BEGIN
END;
```
-When EDB Postgres Advanced Server has validated the stored procedure, it echoes `CREATE PROCEDURE`.
+When EDB Postgres Advanced Server validates the stored procedure, it echoes `CREATE PROCEDURE`.
### Using the EDBCommand object to execute a stored procedure
@@ -85,7 +85,7 @@ To invoke the sample code, enter the following in a browser: `http://localhost/s
## Example: Executing a stored procedure with IN parameters
-The following example shows calling a stored procedure that includes `IN` parameters. To create the sample procedure, invoke `EDB-PSQL` and connect to the EDB Postgres Advanced Server host database. Enter the following SPL code at the command line:
+This example calls a stored procedure that includes `IN` parameters. To create the sample procedure, invoke EDB-PSQL and connect to the EDB Postgres Advanced Server host database. Enter the following SPL code at the command line:
```sql
CREATE OR REPLACE PROCEDURE
@@ -113,13 +113,13 @@ END;
```
-When EDB Postgres Advanced Server has validated the stored procedure, it echoes `CREATE PROCEDURE`.
+When EDB Postgres Advanced Server validates the stored procedure, it echoes `CREATE PROCEDURE`.
### Passing input values to a stored procedure
Calling a stored procedure that contains parameters is similar to executing a stored procedure without parameters. The major difference is that, when calling a parameterized stored procedure, you must use the `EDBParameter` collection of the `EDBCommand` object. When the `EDBParameter` is added to the `EDBCommand` collection, properties such as `ParameterName`, `DbType`, `Direction`, `Size`, and `Value` are set.
-The following example shows the process of executing a parameterized stored procedure from a C# script.
+This example shows the process of executing a parameterized stored procedure from a C# script:
```cpp
<% @ Page Language="C#" Debug="true"%>
@@ -199,15 +199,15 @@ It assigns a value to each parameter before passing them to the `EMP_INSERT` sto
The `Prepare()` method prepares the statement before calling the `ExecuteNonQuery()` method.
-The `ExecuteNonQuery` method of the `EDBCommand` object executes the stored procedure. After the stored procedure executes, a test record is inserted into the `emp` table, and the values inserted are displayed on the webpage.
+The `ExecuteNonQuery` method of the `EDBCommand` object executes the stored procedure. After the stored procedure executes, a test record is inserted into the `emp` table, and the values inserted are displayed on the web page.
## Example: Executing a stored procedure with IN, OUT, and INOUT parameters
-The previous example demonstrated how to pass `IN` parameters to a stored procedure. The following examples show how to pass `IN` values and return `OUT` values from a stored procedure.
+The previous example showed how to pass `IN` parameters to a stored procedure. The following examples show how to pass `IN` values and return `OUT` values from a stored procedure.
### Creating the stored procedure
-The following stored procedure passes the department number and returns the corresponding location and department name. To create the sample procedure, open the EDB-PSQL command line, and connect to the EDB Postgres Advanced Server host database. Enter the following SPL code at the command line:
+The following stored procedure passes the department number and returns the corresponding location and department name. To create the sample procedure, invoke EDB-PSQL and connect to the EDB Postgres Advanced Server host database. Enter the following SPL code at the command line:
```sql
CREATE OR REPLACE PROCEDURE
@@ -233,7 +233,7 @@ BEGIN
END;
```
-When EDB Postgres Advanced Server has validated the stored procedure, it echoes `CREATE PROCEDURE`.
+When EDB Postgres Advanced Server validates the stored procedure, it echoes `CREATE PROCEDURE`.
### Receiving output values from a stored procedure
@@ -244,7 +244,7 @@ When retrieving values from `OUT` parameters, you must explicitly specify the di
In each method, you must declare each parameter, indicating the direction of the parameter (`ParameterDirection.Input`, `ParameterDirection.Output`, or `ParameterDirection.InputOutput`). Before invoking the procedure, you must provide a value for each `IN` and `INOUT` parameter. After the procedure returns, you can retrieve the `OUT` and `INOUT` parameter values from the `command.Parameters[]` array.
-The following code shows using the `ExecuteReader` method to retrieve a result set:
+This code shows using the `ExecuteReader` method to retrieve a result set:
```cpp
<% @ Page Language="C#" Debug="true"%>
@@ -294,7 +294,7 @@ private void Page_Load(object sender, System.EventArgs e)
```
-The following code shows using the `ExecuteNonQuery` method to retrieve a result set:
+This code shows using the `ExecuteNonQuery` method to retrieve a result set:
```cpp
<% @ Page Language="C#" Debug="true"%>
diff --git a/product_docs/docs/net_connector/7.0.4.1/12_using_advanced_queueing.mdx b/product_docs/docs/net_connector/7.0.4.1/12_using_advanced_queueing.mdx
index 1cc0b985b04..2f1588f481f 100644
--- a/product_docs/docs/net_connector/7.0.4.1/12_using_advanced_queueing.mdx
+++ b/product_docs/docs/net_connector/7.0.4.1/12_using_advanced_queueing.mdx
@@ -7,27 +7,29 @@ title: "Using advanced queueing"
EDB Postgres Advanced Server advanced queueing provides message queueing and message processing for the EDB Postgres Advanced Server database. User-defined messages are stored in a queue. A collection of queues is stored in a queue table. Create a queue table before creating a queue that depends on it.
-On the server side, procedures in the `DBMS_AQADM` package create and manage message queues and queue tables. Use the `DBMS_AQ` package to add or remove messages from a queue or register or unregister a PL/SQL callback procedure. For more information about `DBMS_AQ` and `DBMS_AQADM`, see [DBMS_AQ](../../epas/11/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/#pID0E01HG0HA).
+On the server side, procedures in the `DBMS_AQADM` package create and manage message queues and queue tables. Use the `DBMS_AQ` package to add messages to or remove messages from a queue or register or unregister a PL/SQL callback procedure. For more information about `DBMS_AQ` and `DBMS_AQADM`, see [DBMS_AQ](../../epas/11/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/#pID0E01HG0HA).
On the client side, the application uses the EDB.NET driver to enqueue and dequeue messages.
## Enqueueing or dequeueing a message
-For more information about using EDB Postgres Advanced Server's advanced queueing functionality, see the [Database Compatibility for Oracle Developers Built-in Package Guide](/epas/latest/epas_compat_bip_guide/).
+For more information about using EDB Postgres Advanced Server's advanced queueing functionality, see [Built-in packages](/epas/latest/epas_compat_bip_guide/).
### Server-side setup
To use advanced queueing functionality on your .NET application, you must first create a user-defined type, queue table, and queue, and then start the queue on the database server. Invoke EDB-PSQL and connect to the EDB Postgres Advanced Server host database. Use the following SPL commands at the command line:
-**Creating a user-defined type**
+#### Creating a user-defined type
-To specify a RAW data type, create a user-defined type. The following example shows creating a user-defined type named as `myxml`.
+To specify a RAW data type, create a user-defined type. This example shows creating a user-defined type named as `myxml`:
-`CREATE TYPE myxml AS (value XML)`;
+```
+CREATE TYPE myxml AS (value XML);
+```
-**Creating the queue table**
+#### Creating the queue table
-A queue table can hold multiple queues with the same payload type. The following example shows creating a table named `MSG_QUEUE_TABLE`.
+A queue table can hold multiple queues with the same payload type. This example shows creating a table named `MSG_QUEUE_TABLE`:
```Text
EXEC DBMS_AQADM.CREATE_QUEUE_TABLE
@@ -37,9 +39,9 @@ EXEC DBMS_AQADM.CREATE_QUEUE_TABLE
END;
```
-**Creating the queue**
+#### Creating the queue
-The following example shows creating a queue named `MSG_QUEUE` in the table `MSG_QUEUE_TABLE`.
+This example shows creating a queue named `MSG_QUEUE` in the table `MSG_QUEUE_TABLE`:
```Text
BEGIN
@@ -49,7 +51,7 @@ END;
**Starting the queue**
-Once the queue is created, invoke the following SPL code at the command line to start a queue in the EDB database.
+Once the queue is created, invoke the following SPL code at the command line to start a queue in the EDB database:
```Text
BEGIN
@@ -62,7 +64,7 @@ END;
Once you've created a user-defined type, followed by queue table and queue, start the queue. Then, you can enqueue or dequeue a message using EDB .Net drivers.
-**Enqueue a message**
+#### Enqueue a message
To enqueue a message on your .NET application, you must:
@@ -71,10 +73,10 @@ To enqueue a message on your .NET application, you must:
3. Create the enqueue message and define a payload.
4. Call the `queue.Enqueue` method.
-The following code shows using the `queue.Enqueue` method:
+The following code shows using the `queue.Enqueue` method.
!!! Note
- The following code creates the message and serializes it. This is just an example code and won't compile if copied as it is. You must serialize the message as XML.
+ This code creates the message and serializes it. This is example code and doesn't compile if copied as it is. You must serialize the message as XML.
```Text
using EnterpriseDB.EDBClient;
@@ -188,7 +190,7 @@ namespace AQXml
}
```
-**Dequeueing a message**
+#### Dequeueing a message
To dequeue a message on your .NET application, you must:
@@ -197,7 +199,7 @@ To dequeue a message on your .NET application, you must:
3. Call the `queue.Dequeue` method.
!!! Note
- The following code creates the message and serializes it. This is just an example code and won't compile if copied as it is. You must serialize the message as XML.
+ The following code creates the message and serializes it. This is example code and doesn't compile if copied as it is. You must serialize the message as XML.
```Text
using System;
@@ -361,9 +363,9 @@ namespace DequeueXML
## EDBAQ classes
-The following EDBAQ classes are used in this application:
+The following EDBAQ classes are used in this application.
-**EDBAQDequeueMode**
+### EDBAQDequeueMode
The `EDBAQDequeueMode` class lists all the dequeuer modes available.
@@ -374,52 +376,52 @@ The `EDBAQDequeueMode` class lists all the dequeuer modes available.
| Remove | Deletes the message after reading. This is the default value. |
| Remove_NoData | Confirms receipt of the message. |
-**EDBAQDequeueOptions**
+### EDBAQDequeueOptions
The `EDBAQDequeueOptions` class lists the options available when dequeuing a message.
| Property | Description |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| ConsumerName | The name of the consumer for which to dequeue the message. |
-| DequeueMode | This is set from `EDBAQDequeueMode`. It represents the locking behavior linked with the dequeue option. |
-| Navigation | This is set from `EDBAQNavigationMode`. It represents the position of the message to fetch. |
-| Visibility | This is set from `EDBAQVisibility`. It represents whether the new message is dequeued as part of the current transaction. |
+| DequeueMode | Set from `EDBAQDequeueMode`. It represents the locking behavior linked with the dequeue option. |
+| Navigation | Set from `EDBAQNavigationMode`. It represents the position of the message to fetch. |
+| Visibility | Set from `EDBAQVisibility`. It represents whether the new message is dequeued as part of the current transaction. |
| Wait | The wait time for a message as per the search criteria. |
| Msgid | The message identifier. |
| Correlation | The correlation identifier. |
-| DeqCondition | The dequeuer condition. It is a Boolean expression. |
+| DeqCondition | The dequeuer condition. It's a Boolean expression. |
| Transformation | The transformation to apply before dequeuing the message. |
| DeliveryMode | The delivery mode of the dequeued message. |
-**EDBAQEnqueueOptions**
+### EDBAQEnqueueOptions
The `EDBAQEnqueueOptions` class lists the options available when enqueuing a message.
| Property | Description |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------ |
-| Visibility | This is set from `EDBAQVisibility`. It represents whether the new message is enqueued as part of the current transaction. |
+| Visibility | Set from `EDBAQVisibility`. It represents whether the new message is enqueued as part of the current transaction. |
| RelativeMsgid | The relative message identifier. |
| SequenceDeviation | The sequence when to dequeue the message. |
| Transformation | The transformation to apply before enqueuing the message. |
| DeliveryMode | The delivery mode of the enqueued message. |
-**EDBAQMessage**
+### EDBAQMessage
The `EDBAQMessage` class lists a message to enqueue/dequeue.
| Property | Description |
| ------------ | -------------------------------- |
-| Payload | The actual message to be queued. |
+| Payload | The actual message to queue. |
| MessageId | The ID of the queued message. |
-**EDBAQMessageProperties**
+### EDBAQMessageProperties
The `EDBAQMessageProperties` lists the message properties available.
| Property | Description |
| ---------------- | --------------------------------------------------------------------------------------------- |
| Priority | The priority of the message. |
-| Delay | The duration post which the message is available for dequeuing, in seconds. |
+| Delay | The duration after which the message is available for dequeuing, in seconds. |
| Expiration | The duration for which the message is available for dequeuing, in seconds. |
| Correlation | The correlation identifier. |
| Attempts | The number of attempts taken to dequeue the message. |
@@ -431,7 +433,7 @@ The `EDBAQMessageProperties` lists the message properties available.
| TransactionGroup | The transaction group for the dequeued messages. |
| DeliveryMode | The delivery mode of the dequeued message. |
-**EDBAQMessageState**
+### EDBAQMessageState
The `EDBAQMessageState` class represents the state of the message during dequeue.
@@ -442,17 +444,17 @@ The `EDBAQMessageState` class represents the state of the message during dequeue
| Ready | The message is ready to be processed. |
| Waiting | The message is in waiting state. The delay isn't reached. |
-**EDBAQMessageType**
+### EDBAQMessageType
The `EDBAQMessageType` class represents the types for payload.
| Value | Description |
| --------- | ------------------------------------------------------------------------------------- |
| Raw | The raw message type.
Note: Currently, this payload type isn't supported. |
-| UDT | The user defined type message. |
+| UDT | The user-defined type message. |
| XML | The XML type message.
Note: Currently, this payload type isn't supported. |
-**EDBAQNavigationMode**
+### EDBAQNavigationMode
The `EDBAQNavigationMode` class represents the different types of navigation modes available.
@@ -462,21 +464,21 @@ The `EDBAQNavigationMode` class represents the different types of navigation mod
| Next_Message | Returns the next available message that matches the search items. |
| Next_Transaction | Returns the first message of next transaction group. |
-**EDBAQQueue**
+### EDBAQQueue
The `EDBAQQueue` class represents a SQL statement to execute `DMBS_AQ` functionality on a PostgreSQL database.
| Property | Description |
| ----------------- | --------------------------------------------------------------------------------------------- |
-| Connection | The connection to use |
-| Name | The name of the queue |
-| MessageType | The message type that's enqueued/dequeued from this queue, for example `EDBAQMessageType.Udt` |
-| UdtTypeName | The user-defined type name of the message type |
-| EnqueueOptions | The enqueue options to use |
-| DequeuOptions | The dequeue options to use |
-| MessageProperties | The message properties to use |
-
-**EDBAQVisibility**
+| Connection | The connection to use. |
+| Name | The name of the queue. |
+| MessageType | The message type that's enqueued/dequeued from this queue, for example `EDBAQMessageType.Udt`. |
+| UdtTypeName | The user-defined type name of the message type. |
+| EnqueueOptions | The enqueue options to use. |
+| DequeuOptions | The dequeue options to use. |
+| MessageProperties | The message properties to use. |
+
+### EDBAQVisibility
The `EDBAQVisibility` class represents the visibility options available.
diff --git a/product_docs/docs/net_connector/7.0.4.1/13_using_a_ref_cursor_in_a_net_application.mdx b/product_docs/docs/net_connector/7.0.4.1/13_using_a_ref_cursor_in_a_net_application.mdx
index 9b7c514a0ff..3b77d3f4ba8 100644
--- a/product_docs/docs/net_connector/7.0.4.1/13_using_a_ref_cursor_in_a_net_application.mdx
+++ b/product_docs/docs/net_connector/7.0.4.1/13_using_a_ref_cursor_in_a_net_application.mdx
@@ -12,15 +12,19 @@ A `ref cursor` is a cursor variable that contains a pointer to a query result se
`SYS_REFCURSOR` is a ref cursor type that allows any result set to be associated with it. This is known as a weakly typed ref cursor. The following example is a declaration of a weakly typed ref cursor:
- `name SYS_REFCURSOR`;
+```
+ name SYS_REFCURSOR`;
+```
Following is an example of a strongly typed ref cursor:
- `TYPE IS REF CURSOR RETURN emp%ROWTYPE`;
+```
+TYPE IS REF CURSOR RETURN emp%ROWTYPE`;
+```
## Creating the stored procedure
-The following sample code creates a stored procedure called `refcur_inout_callee`. It specifies the data type of the ref cursor being passed as an OUT parameter. To create the sample procedure, invoke EDB-PSQL and connect to the EDB Postgres Advanced Server host database. Enter the following SPL code at the command line:
+This sample code creates a stored procedure called `refcur_inout_callee`. It specifies the data type of the ref cursor being passed as an OUT parameter. To create the sample procedure, invoke EDB-PSQL and connect to the EDB Postgres Advanced Server host database. Enter the following SPL code at the command line:
```sql
CREATE OR REPLACE PROCEDURE
@@ -31,7 +35,7 @@ BEGIN
END;
```
-The following C# code uses the stored procedure to retrieve employee names from the `emp` table:
+This C# code uses the stored procedure to retrieve employee names from the `emp` table:
```cpp
using System;
@@ -88,7 +92,7 @@ namespace EDBRefCursor
}
```
-The following .NET code snippet displays the result on the console:
+This .NET code snippet displays the result on the console:
```cpp
for(int i = 0;i < fc; i++)
diff --git a/product_docs/docs/net_connector/7.0.4.1/14_using_plugins.mdx b/product_docs/docs/net_connector/7.0.4.1/14_using_plugins.mdx
index 90dbd406cf9..8f60d1b3f57 100644
--- a/product_docs/docs/net_connector/7.0.4.1/14_using_plugins.mdx
+++ b/product_docs/docs/net_connector/7.0.4.1/14_using_plugins.mdx
@@ -16,49 +16,40 @@ The plugins support the use of spatial, data/time, and JSON types. The following
## GeoJSON
-If you're using the GeoJSON plugin on .NET Standard 2.0, the data provider installation path is:
-
- `C:\Program Files\edb\dotnet\plugins\GeoJSON\netstandard2.0`
+If you're using the GeoJSON plugin on .NET Standard 2.0, the data provider installation path is `C:\Program Files\edb\dotnet\plugins\GeoJSON\netstandard2.0`.
The following shared library files are required:
-`EnterpriseDB.EDBClient.GeoJSON.dll`
+- `EnterpriseDB.EDBClient.GeoJSON.dll`
For detailed information about using the GeoJSON plugin, see the [Npgsql documentation](http://www.npgsql.org/doc/types/geojson.html).
## Json.NET
-If you're using the Json.NET plugin on .NET Standard 2.0, the data provider installation path is:
-
- `C:\Program Files\edb\dotnet\plugins\Json.NET\netstandard2.0`
+If you're using the Json.NET plugin on .NET Standard 2.0, the data provider installation path is `C:\Program Files\edb\dotnet\plugins\Json.NET\netstandard2.0`.
The following shared library files are required:
-`EnterpriseDB.EDBClient.Json.NET.dll`
+- `EnterpriseDB.EDBClient.Json.NET.dll`
For detailed information about using the Json.NET plugin, see the [Npgsql documentation](http://www.npgsql.org/doc/types/jsonnet.html).
## NetTopologySuite
-If you're using the NetTopologySuite plugin on .Net Standard 2.0, the data provider installation path is:
-
- `C:\Program Files\edb\dotnet\plugins\NetTopologySuite\netstandard2.0`
+If you're using the NetTopologySuite plugin on .Net Standard 2.0, the data provider installation path is `C:\Program Files\edb\dotnet\plugins\NetTopologySuite\netstandard2.0`.
The following shared library files are required:
- `EnterpriseDB.EDBClient.NetTopologySuite.dll`
+- `EnterpriseDB.EDBClient.NetTopologySuite.dll`
For detailed information about using the NetTopologySuite type plugin, see the [Npgsql documentation](http://www.npgsql.org/doc/types/nts.html).
## NodaTime
-If you're using the NodaTime plugin on .Net Standard 2.0, the data provider installation path is:
-
- `C:\Program Files\edb\dotnet\plugins\NodaTime\netstandard2.0`
+If you're using the NodaTime plugin on .Net Standard 2.0, the data provider installation path is `C:\Program Files\edb\dotnet\plugins\NodaTime\netstandard2.0`.
The following shared library files are required:
- `EnterpriseDB.EDBClient.NodaTime.dll`
+- `EnterpriseDB.EDBClient.NodaTime.dll`
For detailed information about using the NodaTime plugin, see the [Npgsql documentation](http://www.npgsql.org/doc/types/nodatime.html).
-
diff --git a/product_docs/docs/net_connector/7.0.4.1/15_using_object_types.mdx b/product_docs/docs/net_connector/7.0.4.1/15_using_object_types.mdx
index a5b9bde5488..c57c5ba4713 100644
--- a/product_docs/docs/net_connector/7.0.4.1/15_using_object_types.mdx
+++ b/product_docs/docs/net_connector/7.0.4.1/15_using_object_types.mdx
@@ -5,11 +5,9 @@ title: "Using object types in .NET"
-The SQL `CREATE TYPE` command creates a user-defined object type, which is stored in the EDB Postgres Advanced Server database.
+The SQL `CREATE TYPE` command creates a user-defined object type, which is stored in the EDB Postgres Advanced Server database. You can then reference these user-defined types in SPL procedures, SPL functions, and .NET programs.
-You can then reference these user-defined types in SPL procedures, SPL functions, and .NET programs.
-
-The basic object type is created with the `CREATE TYPE AS OBJECT` command with optional use of the `CREATE TYPE BODY` command.
+Create the basic object type with the `CREATE TYPE AS OBJECT` command. Optionally, use the `CREATE TYPE BODY` command.
## Using an object type
@@ -49,7 +47,7 @@ CREATE OR REPLACE TYPE BODY emp_obj_typ AS
END;
```
-The following listing is a complete .NET program that uses these user-defined object types:
+This example is a complete .NET program that uses these user-defined object types:
```text
using EnterpriseDB.EDBClient;
@@ -156,7 +154,7 @@ A call to `EDBCommandBuilder.DeriveParameters()` gets parameter information for
EDBCommandBuilder.DeriveParameters(cmd);
```
-The value of the parameter is set by creating an object of the .NET type and assigning it to the `Value` property of the parameter:
+Set the value of the parameter by creating an object of the .NET type and assigning it to the `Value` property of the parameter:
```text
addr_object_type address = new addr_object_type()
diff --git a/product_docs/docs/net_connector/7.0.4.1/16_scram_compatibility.mdx b/product_docs/docs/net_connector/7.0.4.1/16_scram_compatibility.mdx
index 886739de0ae..feff2da342b 100644
--- a/product_docs/docs/net_connector/7.0.4.1/16_scram_compatibility.mdx
+++ b/product_docs/docs/net_connector/7.0.4.1/16_scram_compatibility.mdx
@@ -7,4 +7,4 @@ legacyRedirects:
-The EDB .NET driver provides SCRAM-SHA-256 support for EDB Postgres Advanced Server version 10 and above. This support is available from EDB .NET 4.0.2.1 release onwards.
+The EDB .NET driver provides SCRAM-SHA-256 support for EDB Postgres Advanced Server version 10 and later. This support is available from EDB .NET 4.0.2.1 release and later.
diff --git a/product_docs/docs/net_connector/7.0.4.1/17_advanced_server_net_connector_logging.mdx b/product_docs/docs/net_connector/7.0.4.1/17_advanced_server_net_connector_logging.mdx
index 3702fc36be2..03bd1ed820a 100644
--- a/product_docs/docs/net_connector/7.0.4.1/17_advanced_server_net_connector_logging.mdx
+++ b/product_docs/docs/net_connector/7.0.4.1/17_advanced_server_net_connector_logging.mdx
@@ -5,10 +5,10 @@ title: "EDB .NET Connector logging"
-EDB .NET Connector supports the use of logging to help resolve issues with the .NET Connector when used in your application. EDB .NET Connector supports logging using the standard .NET Microsoft.Extensions.Logging package. For more information about Logging in .Net see [Logging in C# and .NET](https://learn.microsoft.com/en-us/dotnet/core/extensions/logging?tabs=command-line).
+EDB .NET Connector supports the use of logging to help resolve issues with the .NET Connector when used in your application. EDB .NET Connector supports logging using the standard .NET `Microsoft.Extensions.Logging` package. For more information about logging in .Net, see [Logging in C# and .NET](https://learn.microsoft.com/en-us/dotnet/core/extensions/logging?tabs=command-line).
!!! Note
- For versions earlier then 7.x, EDB .NET Connector had its own, custom logging API.
+ For versions earlier than 7.x, EDB .NET Connector had its own, custom logging API.
## Console logging provider
@@ -16,7 +16,7 @@ EDB .NET Connector supports the use of logging to help resolve issues with the .
### Console logging with EDBDataSource
-Create a `Microsoft.Extensions.Logging.LoggerFactory` and configure an `EDBDataSource` with it. Any use of connections opened through this data source will log via this logger factory.
+Create a `Microsoft.Extensions.Logging.LoggerFactory` and configure an `EDBDataSource` with it. Any use of connections opened through this data source log using this logger factory.
```text
var loggerFactory = LoggerFactory.Create(builder => builder.AddSimpleConsole());
@@ -32,7 +32,7 @@ _ = await command.ExecuteScalarAsync();
### Console logging without EDBDataSource
-Create a `Microsoft.Extensions.Logging.LoggerFactory` and configure EDB.NET Connector's logger factory globally using `EDBLoggingConfiguration.InitializeLogging` at the start of your program, before any other EDB.NET Connector API is used.
+Create a `Microsoft.Extensions.Logging.LoggerFactory` and configure EDB .NET Connector's logger factory globally using `EDBLoggingConfiguration.InitializeLogging`. Configure it at the start of your program, before using any other EDB .NET Connector API.
```text
var loggerFactory = LoggerFactory.Create(builder => builder.AddSimpleConsole());
@@ -43,6 +43,7 @@ await conn.OpenAsync();
await using var command = new EDBCommand("SELECT 1", conn);
_ = await command.ExecuteScalarAsync();
```
+
## Log levels
The following log levels are available:
From fc2d5dced5d7b82947a773d165171d4ce64e0e48 Mon Sep 17 00:00:00 2001
From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com>
Date: Tue, 11 Jul 2023 13:55:31 -0400
Subject: [PATCH 02/19] lower cased word
---
product_docs/docs/net_connector/7.0.4.1/index.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/product_docs/docs/net_connector/7.0.4.1/index.mdx b/product_docs/docs/net_connector/7.0.4.1/index.mdx
index d2c4ffbca2b..bf76485914e 100644
--- a/product_docs/docs/net_connector/7.0.4.1/index.mdx
+++ b/product_docs/docs/net_connector/7.0.4.1/index.mdx
@@ -1,7 +1,7 @@
---
title: "EDB .NET Connector"
directoryDefaults:
- description: "EDB .NET Connector Version 6.0.2.1 Documentation and release notes."
+ description: "EDB .NET Connector version 6.0.2.1 documentation and release notes."
---
The EDB .NET Connector distributed with EDB Postgres Advanced Server provides connectivity between a .NET client application and an EDB Postgres Advanced Server database server. You can:
From 9172039a167c84d82c620f26f5f5e8bce2ab4a1e Mon Sep 17 00:00:00 2001
From: drothery-edb
Date: Wed, 12 Jul 2023 10:42:19 -0400
Subject: [PATCH 03/19] PEM: fixing links broken with PEM agent restructure
---
.../docs/pem/9/managing_pem_agent/setting_agent_privileges.mdx | 2 +-
.../docs/pem/9/monitoring_performance/notifications.mdx | 2 +-
.../docs/pem/9/monitoring_performance/pem_remote_monitoring.mdx | 2 +-
product_docs/docs/pem/9/registering_database_server.mdx | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/product_docs/docs/pem/9/managing_pem_agent/setting_agent_privileges.mdx b/product_docs/docs/pem/9/managing_pem_agent/setting_agent_privileges.mdx
index 895f13ed1e3..1ae37aae839 100644
--- a/product_docs/docs/pem/9/managing_pem_agent/setting_agent_privileges.mdx
+++ b/product_docs/docs/pem/9/managing_pem_agent/setting_agent_privileges.mdx
@@ -17,7 +17,7 @@ PEM functionality lessens as the privileges of the PEM agent decrease. For compl
| Manage Alerts | yes | yes | yes
NOTE: When run alert script on the database server is selected, it will run on the machine, where bound PEM Agent is running, and not on the actual database server machine.
|
| Manage Charts | yes | yes | yes |
| Manage Dashboards | yes | Some dashboards may not be able to show complete data. For example, columns such as swap usage, CPU usage, IO read, and IO write will be displayed as 0 in the session activity dashboard. | Some dashboards may not be able to show complete data. For example, the operating system information of the database server will not be displayed as not available. |
-| Manage Probes | yes | Some of the PEM probes will not return information, and some of functionalities may be affected. For details about probe functionality, see the [Agent privileges](/pem/latest/managing_pem_agent/#agent-privileges). | Some of the PEM probes will not return information, and some of the functionalities may be affected. |
+| Manage Probes | yes | Some of the PEM probes will not return information, and some of functionalities may be affected. | Some of the PEM probes will not return information, and some of the functionalities may be affected. |
| Postgres Expert | yes | The Postgres Expert will be able to access the configuration expert and schema expert, but not the security expert. | The Expert will provide partial information as operating system information is not available. |
| Postgres Log Analysis Expert | yes | The Postgres Log Analysis Expert may not be able to do the analysis as it is dependent on the logs imported by log manager, which will not work as required. | The Postgres Log Analysis Expert will not be able to do the analysis as it is dependent on the logs imported by log manager, which will not work as required. |
| Scheduled Tasks | yes | For Linux if user is the same as batch_script_user in agent.cfg then shell script will run. | Scheduled tasks will work only for database server; scripts will run on a remote Agent. |
diff --git a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx
index a4af6858f75..eb0d1ba755c 100644
--- a/product_docs/docs/pem/9/monitoring_performance/notifications.mdx
+++ b/product_docs/docs/pem/9/monitoring_performance/notifications.mdx
@@ -82,7 +82,7 @@ To define a new webhook, select the plus sign (+) in the upper-right corner of t
### Defining webhook SSL configurations
-You can define the webhook SSL parameters in the respective agent configuration file or registry in Windows. You can find the list of webhook SSL parameters in [PEM agent configuration parameters](../managing_pem_agent/#agent-configuration). If you add or remove any of the agent configuration parameters, you must restart the agent to apply them.
+You can define the webhook SSL parameters in the respective agent configuration file or registry in Windows. You can find the list of webhook SSL parameters in [PEM agent configuration parameters](../managing_pem_agent/modifying_agent_configuration). If you add or remove any of the agent configuration parameters, you must restart the agent to apply them.
- On 32-bit Windows systems, PEM registry entries for webhooks are located in `HKEY_LOCAL_MACHINE\\Software\\EnterpriseDB\\PEM\\agent\\WEBHOOK`.
- On 64-bit Windows systems, PEM registry entries for webhooks are located in `HKEY_LOCAL_MACHINE\\Software\\Wow6432Node\\EnterpriseDB\\PEM\\agent\\WEBHOOK`.
diff --git a/product_docs/docs/pem/9/monitoring_performance/pem_remote_monitoring.mdx b/product_docs/docs/pem/9/monitoring_performance/pem_remote_monitoring.mdx
index dfeae973dad..ec5b38684a3 100644
--- a/product_docs/docs/pem/9/monitoring_performance/pem_remote_monitoring.mdx
+++ b/product_docs/docs/pem/9/monitoring_performance/pem_remote_monitoring.mdx
@@ -23,7 +23,7 @@ PEM remote monitoring supports:
| [Capacity Manager](capacity_manager/) | Limited | There's no correlation between the Postgres cluster and operating system metrics. |
| [Manage alerts](alerts/) | Limited | When you run an alert script on the Postges cluster, it runs on the machine where the bound PEM agent is running and not on the actual Postgres cluster machine. |
| [Manage dashboards](dashboards/) | Limited | Some dashboards might not be able to show complete data. For example, the operating system information where the Postgres cluster is running isn't displayed as it isn't available. |
-| [Manage probes](probes/) | Limited | Some of the PEM probes don't return information, and some of the functionality might be affected. For details about probe functionality, see [PEM agent privileges](../managing_pem_agent/#agent-privileges). |
+| [Manage probes](probes/) | Limited | Some of the PEM probes don't return information, and some of the functionality might be affected. For details about probe functionality, see [PEM agent privileges](../managing_pem_agent/setting_agent_privileges). |
| [Postgres Expert](../tuning_performance/postgres_expert/) | Limited | The Postgres Expert provides partial information as operating system information isn't available. |
| [Scheduled tasks](../pem_web_interface/#management-menu) | Limited | Scheduled tasks work only for Postgres clusters, and scripts run on a remote agent. |
| [Core usage reports](../reports/#core-usage-report) | Limited | The Core Usage reports don't show complete information. For example, the platform, number of cores, and total RAM aren't displayed. |
diff --git a/product_docs/docs/pem/9/registering_database_server.mdx b/product_docs/docs/pem/9/registering_database_server.mdx
index 2041e25f04a..dd4771239c9 100644
--- a/product_docs/docs/pem/9/registering_database_server.mdx
+++ b/product_docs/docs/pem/9/registering_database_server.mdx
@@ -126,7 +126,7 @@ For more information about using SSL encryption, see the [PostgreSQL documentati
- Use the **Database** field to specify the name of the Postgres database to which the agent initially connects. If you're registering a EDB Postgres Distributed database node then specify the EDB Postgres Distributed-enabled database name in this field.
-- In the **User name** field, specify the name of the role for the agent to use when connecting to the server. The specified role must be a database superuser for all of the features to work as expected. For the list of features that don't work if the specified role isn't a database superuser, see [Agent privileges](managing_pem_agent/#agent-privileges). If you're using the Kerberos authentication method, then specify the user having the pgd_monitor or pgd_superuser role in this field.
+- In the **User name** field, specify the name of the role for the agent to use when connecting to the server. The specified role must be a database superuser for all of the features to work as expected. For the list of features that don't work if the specified role isn't a database superuser, see [Agent privileges](managing_pem_agent/setting_agent_privileges). If you're using the Kerberos authentication method, then specify the user having the pgd_monitor or pgd_superuser role in this field.
If you're using Postgres version 10 or later, you can use the pg_monitor role to grant the required privileges to a non-superuser. For information about the pg_monitor role, see [Default Roles](https://www.postgresql.org/docs/current/default-roles.html).
From a73808f10fdd4f5bc84c9e010e05f1da8f943ab2 Mon Sep 17 00:00:00 2001
From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com>
Date: Thu, 13 Jul 2023 11:39:50 +0530
Subject: [PATCH 04/19] Updated and fixed content as per review comments from
Betsy
---
.../docs/net_connector/7.0.4.1/12_using_advanced_queueing.mdx | 2 +-
product_docs/docs/net_connector/7.0.4.1/index.mdx | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/product_docs/docs/net_connector/7.0.4.1/12_using_advanced_queueing.mdx b/product_docs/docs/net_connector/7.0.4.1/12_using_advanced_queueing.mdx
index 2f1588f481f..e454478d310 100644
--- a/product_docs/docs/net_connector/7.0.4.1/12_using_advanced_queueing.mdx
+++ b/product_docs/docs/net_connector/7.0.4.1/12_using_advanced_queueing.mdx
@@ -7,7 +7,7 @@ title: "Using advanced queueing"
EDB Postgres Advanced Server advanced queueing provides message queueing and message processing for the EDB Postgres Advanced Server database. User-defined messages are stored in a queue. A collection of queues is stored in a queue table. Create a queue table before creating a queue that depends on it.
-On the server side, procedures in the `DBMS_AQADM` package create and manage message queues and queue tables. Use the `DBMS_AQ` package to add messages to or remove messages from a queue or register or unregister a PL/SQL callback procedure. For more information about `DBMS_AQ` and `DBMS_AQADM`, see [DBMS_AQ](../../epas/11/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/#pID0E01HG0HA).
+On the server side, procedures in the `DBMS_AQADM` package create and manage message queues and queue tables. Use the `DBMS_AQ` package to add messages to or remove messages from a queue or register or unregister a PL/SQL callback procedure. For more information about `DBMS_AQ` and `DBMS_AQADM`, see [DBMS_AQ](../..//epas/latest/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/).
On the client side, the application uses the EDB.NET driver to enqueue and dequeue messages.
diff --git a/product_docs/docs/net_connector/7.0.4.1/index.mdx b/product_docs/docs/net_connector/7.0.4.1/index.mdx
index bf76485914e..81bba2f40ec 100644
--- a/product_docs/docs/net_connector/7.0.4.1/index.mdx
+++ b/product_docs/docs/net_connector/7.0.4.1/index.mdx
@@ -1,7 +1,7 @@
---
title: "EDB .NET Connector"
directoryDefaults:
- description: "EDB .NET Connector version 6.0.2.1 documentation and release notes."
+ description: "EDB .NET Connector version 7.0.4.1 documentation and release notes."
---
The EDB .NET Connector distributed with EDB Postgres Advanced Server provides connectivity between a .NET client application and an EDB Postgres Advanced Server database server. You can:
From 13fa36fb726204d55e616fdb8789cfef4b851c4a Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan
Date: Fri, 7 Jul 2023 09:18:05 +0100
Subject: [PATCH 05/19] Added note on presence check
Signed-off-by: Dj Walker-Morgan
---
product_docs/docs/tde/15/enabling_tde.mdx | 17 ++++++++++++++++-
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/product_docs/docs/tde/15/enabling_tde.mdx b/product_docs/docs/tde/15/enabling_tde.mdx
index 2637d54a259..e81c68d33a2 100644
--- a/product_docs/docs/tde/15/enabling_tde.mdx
+++ b/product_docs/docs/tde/15/enabling_tde.mdx
@@ -65,7 +65,8 @@ If you don't specify this parameter, the environment variable `PGDATAKEYUNWRAPCM
Use the special value `-` if you don't want to apply any key unwrapping command.
-
+
You must specify this parameter or the environment variable fallback if you're using data encryption. See [Securing the data encryption key](./key_stores/) for more information.
@@ -108,3 +109,17 @@ This example uses EDB Postgres Advanced Server 15 running on a Linux platform. I
data_encryption_key_unwrap_command = 'openssl enc -d -aes-128-cbc -pass pass:ok -in %p'
```
+## Checking for TDE in use using SQL
+
+The presence of TDE on a server can be determined by querying the `data_encryption_version` column of the `pg_control_init` table.
+
+A value of 0 means TDE is not enabled. Any non-zero value reflects the version of TDE in use. Currently, when TDE is enabled, this value will be 1.
+
+```sql
+# select data_encryption_version from pg_control_init;
+ data_encryption_version
+-------------------------
+ 1
+(1 row)
+```
+
From a431adc43c35c49f23e07457b6aadb4650773f40 Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com>
Date: Wed, 12 Jul 2023 12:55:21 +0100
Subject: [PATCH 06/19] Small fixes from reviews
---
product_docs/docs/tde/15/enabling_tde.mdx | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/product_docs/docs/tde/15/enabling_tde.mdx b/product_docs/docs/tde/15/enabling_tde.mdx
index e81c68d33a2..5021410961c 100644
--- a/product_docs/docs/tde/15/enabling_tde.mdx
+++ b/product_docs/docs/tde/15/enabling_tde.mdx
@@ -65,9 +65,6 @@ If you don't specify this parameter, the environment variable `PGDATAKEYUNWRAPCM
Use the special value `-` if you don't want to apply any key unwrapping command.
-
-
You must specify this parameter or the environment variable fallback if you're using data encryption. See [Securing the data encryption key](./key_stores/) for more information.
You can set this parameter only at server start.
@@ -109,7 +106,7 @@ This example uses EDB Postgres Advanced Server 15 running on a Linux platform. I
data_encryption_key_unwrap_command = 'openssl enc -d -aes-128-cbc -pass pass:ok -in %p'
```
-## Checking for TDE in use using SQL
+## Checking for TDE presence using SQL
The presence of TDE on a server can be determined by querying the `data_encryption_version` column of the `pg_control_init` table.
From 74955f08f1395248149b5158f132e883734bc6c6 Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com>
Date: Wed, 12 Jul 2023 15:36:03 +0100
Subject: [PATCH 07/19] Update product_docs/docs/tde/15/enabling_tde.mdx
Co-authored-by: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com>
---
product_docs/docs/tde/15/enabling_tde.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/product_docs/docs/tde/15/enabling_tde.mdx b/product_docs/docs/tde/15/enabling_tde.mdx
index 5021410961c..1167108a944 100644
--- a/product_docs/docs/tde/15/enabling_tde.mdx
+++ b/product_docs/docs/tde/15/enabling_tde.mdx
@@ -110,7 +110,7 @@ This example uses EDB Postgres Advanced Server 15 running on a Linux platform. I
The presence of TDE on a server can be determined by querying the `data_encryption_version` column of the `pg_control_init` table.
-A value of 0 means TDE is not enabled. Any non-zero value reflects the version of TDE in use. Currently, when TDE is enabled, this value will be 1.
+A value of 0 means TDE isn't enabled. Any non-zero value reflects the version of TDE in use. Currently, when TDE is enabled, this value is 1.
```sql
# select data_encryption_version from pg_control_init;
From 7935c90fca5c3a1bc39f5fe91110d83a5e4f29ea Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com>
Date: Thu, 13 Jul 2023 14:03:14 +0100
Subject: [PATCH 08/19] Quick fix for version number
Quick fix for version number .12 -> .19
---
product_docs/docs/tpa/23/rel_notes/index.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/product_docs/docs/tpa/23/rel_notes/index.mdx b/product_docs/docs/tpa/23/rel_notes/index.mdx
index adda416c9e9..68d9b69aa38 100644
--- a/product_docs/docs/tpa/23/rel_notes/index.mdx
+++ b/product_docs/docs/tpa/23/rel_notes/index.mdx
@@ -16,7 +16,7 @@ The Trusted Postgres Architect documentation describes the latest version of Tru
| Version | Release date |
| ---------------------------- | ------------ |
-| [23.12](tpa_23.19_rel_notes) | 12 Jul 2023 |
+| [23.19](tpa_23.19_rel_notes) | 12 Jul 2023 |
| [23.18](tpa_23.18_rel_notes) | 23 May 2023 |
| [23.17](tpa_23.17_rel_notes) | 10 May 2023 |
| [23.16](tpa_23.16_rel_notes) | 21 Mar 2023 |
From d1ed2dfda68186a6c70d4dc3b36255aec96f9f25 Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan
Date: Thu, 29 Jun 2023 16:09:37 +0100
Subject: [PATCH 09/19] First commit for Parallel Apply
Signed-off-by: Dj Walker-Morgan
---
product_docs/docs/pgd/5/index.mdx | 1 +
product_docs/docs/pgd/5/parallelapply.mdx | 55 +++++++++++++++++++++++
2 files changed, 56 insertions(+)
create mode 100644 product_docs/docs/pgd/5/parallelapply.mdx
diff --git a/product_docs/docs/pgd/5/index.mdx b/product_docs/docs/pgd/5/index.mdx
index d04701a29a6..82d22e1a248 100644
--- a/product_docs/docs/pgd/5/index.mdx
+++ b/product_docs/docs/pgd/5/index.mdx
@@ -39,6 +39,7 @@ navigation:
- scaling
- twophase
- tssnapshots
+ - parallelapply
- "#Reference"
- reference
---
diff --git a/product_docs/docs/pgd/5/parallelapply.mdx b/product_docs/docs/pgd/5/parallelapply.mdx
new file mode 100644
index 00000000000..aca40703a20
--- /dev/null
+++ b/product_docs/docs/pgd/5/parallelapply.mdx
@@ -0,0 +1,55 @@
+---
+title: Parallel Apply
+navTitle: Parallel Apply
+---
+
+### What is Parallel Apply?
+
+Parallel Apply is a feature of PGD that allows a PGD node to use multiple writers per subscription. This generally increases the throughput of a subscription and improves replication performance.
+
+The transactional changes from the subscription are written by the multiple Parallel Apply writers. However, each writer ensures that the final commit of its transaction does not violate the commit order as executed on the origin node. If there is a violation, an error is generated and the transaction can be rolled back.
+
+!!! Warning Possible deadlocks
+It may be possible that this out-of-order application of changes could trigger a deadlock. PGD currently resolves such deadlocks between Parallel Apply writers by aborting and retrying the transactions involved. If you experience a large number of such deadlocks, this is an indication that Parallel Apply is not a good fit for your workload and you should consider disabling it.
+!!!
+
+### Configuring Parallel Apply
+There are two variables which control Parallel Apply in PGD 5, [`bdr.max_writers_per_subscription`](/pgd/latest/reference/pgd-settings#bdrmax_writers_per_subscription) and [`bdr.writers_per_subscription`](/pgd/latest/reference/pgd-settings#bdrwriters_per_subscription). The default settings for these are 8 and 2.
+
+```plain
+bdr.max_writers_per_subscription = 8
+bdr.writers_per_subscription = 2
+```
+
+This gives each subscription two writers, but in some circumstances, the system may allocate up to 8 writers for a subscription.
+
+[`bdr.max_writers_per_subscription`](/pgd/latest/reference/pgd-settings#bdrmax_writers_per_subscription) can only be changed with a server restart.
+
+[`bdr.writers_per_subscription`](/pgd/latest/reference/pgd-settings#bdrwriters_per_subscription) can be changed, for a specific subscription, without a restart by halting the subscription using [`bdr.alter_subscription_disable`](/pgd/latest/reference/nodes-management-interfaces#bdralter_subscription_disable), setting the new value and then resuming the subscription using [`bdr.alter_subscription_enable`](/pgd/latest/reference/nodes-management-interfaces#bdralter_subscription_enable). First establish the name of the subscription using `select * from bdr.subscription`. For this example, the subscription name is `bdr_bdrdb_bdrgroup_node2_node1`.
+
+
+```sql
+SELECT bdr.alter_subscription_disable ('bdr_bdrdb_bdrgroup_node2_node1');
+
+UPDATE bdr.subscription
+SET num_writers = 4
+WHERE sub_name = 'bdr_bdrdb_bdrgroup_node2_node1';
+
+SELECT bdr.alter_subscription_enable ('bdr_bdrdb_bdrgroup_node2_node1');
+```
+
+### When to use Parallel Apply
+
+Parallel Apply is always on by default and for most operations, we recommend that it is left on.
+
+### When not to use Parallel Apply
+
+As of, and up to at least PGD 5.1, Parallel Apply should not be used with Group Commit, CAMO and eager replication. You should disable Parallel Apply in these scenarios. If you are experiencing a large number of deadlocks, you may also want to disable it.
+
+### Disabling Parallel Apply
+
+To disable Parallel Apply set [`bdr.writers_per_subscription`](/pgd/latest/reference/pgd-settings#bdrwriters_per_subscription) to 1.
+
+
+
+
From d40bdc60952613f3395d86f336f0f2173e6117db Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan
Date: Thu, 29 Jun 2023 16:13:01 +0100
Subject: [PATCH 10/19] Linked to choosing server
Signed-off-by: Dj Walker-Morgan
---
product_docs/docs/pgd/5/choosing_server.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/product_docs/docs/pgd/5/choosing_server.mdx b/product_docs/docs/pgd/5/choosing_server.mdx
index 9dd210f7b0b..ae7cdc72734 100644
--- a/product_docs/docs/pgd/5/choosing_server.mdx
+++ b/product_docs/docs/pgd/5/choosing_server.mdx
@@ -17,7 +17,7 @@ The following table lists features of EDB Postgres Distributed that are dependen
| [Subscribe-only nodes](nodes/#physical-standby-nodes) | Y | Y | Y |
| [Monitoring](monitoring/) | Y | Y | Y |
| [OpenTelemetry support](monitoring/otel/) | Y | Y | Y |
-| Parallel apply | Y | Y | Y |
+| [Parallel apply](parallelapply) | Y | Y | Y |
| [Conflict-free replicated data types (CRDTs)](consistency/crdt/) | Y | Y | Y |
| [Column-level conflict resolution](consistency/column-level-conflicts/) | Y | Y | Y |
| [Transform triggers](striggers/#transform-triggers) | Y | Y | Y |
From 862c6b3a00c920cc47588ca62f1d1624a0a1f52d Mon Sep 17 00:00:00 2001
From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com>
Date: Thu, 13 Jul 2023 12:14:04 -0400
Subject: [PATCH 11/19] A bit of cleanup to this topic
and to the new release text
---
.../edbplus_41.1_rel_notes.mdx | 2 +-
.../docs/edb_plus/41/06_command_summary.mdx | 110 +++++++++---------
2 files changed, 56 insertions(+), 56 deletions(-)
diff --git a/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.1_rel_notes.mdx b/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.1_rel_notes.mdx
index 2f33f164af7..69bc21a38e3 100644
--- a/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.1_rel_notes.mdx
+++ b/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.1_rel_notes.mdx
@@ -6,4 +6,4 @@ New features, enhancements, bug fixes, and other changes in EDB*Plus 41.1.0 incl
| Type | Description |
| ----------- | -------------------------------------------------------------- |
-| Enhancement | The `COLUMN` command in EDB\*Plus has been enhanced to provide support for the `NEW_VALUE` parameter. The `NEW_VALUE` parameter defines a variable to hold the column value in a given EDB*Plus session. |
+| Enhancement | The `COLUMN` command in EDB\*Plus now provides support for the `NEW_VALUE` parameter. The `NEW_VALUE` parameter defines a variable to hold the column value in a given EDB\*Plus session. |
diff --git a/product_docs/docs/edb_plus/41/06_command_summary.mdx b/product_docs/docs/edb_plus/41/06_command_summary.mdx
index 249c749b47e..a668e5f3384 100644
--- a/product_docs/docs/edb_plus/41/06_command_summary.mdx
+++ b/product_docs/docs/edb_plus/41/06_command_summary.mdx
@@ -19,7 +19,7 @@ The `ACCEPT` command displays a prompt and waits for keyboard input. The value f
ACC[EPT ] variable
```
-The following example creates a new variable named `my_name`, accepts a value of `John Smith`, and then displays the value using the `DEFINE` command.
+This example creates a new variable named `my_name`, accepts a value of `John Smith`, and then displays the value using the `DEFINE` command.
```sql
SQL> ACCEPT my_name
@@ -36,7 +36,7 @@ DEFINE MY_NAME = "John Smith"
A[PPEND ] text
```
-In the following example, a `SELECT` command is built in the SQL buffer using the `APPEND` command. Two spaces are placed between the `APPEND` command and the `WHERE` clause to separate `dept` and `WHERE` by one space in the SQL buffer.
+In this example, a `SELECT` command is built in the SQL buffer using the `APPEND` command. Two spaces are placed between the `APPEND` command and the `WHERE` clause to separate `dept` and `WHERE` by one space in the SQL buffer.
```sql
SQL> APPEND SELECT * FROM dept
@@ -55,9 +55,9 @@ SQL> LIST
C[HANGE ] FROM [ TO ]
```
-If `TO/` is specified, the first occurrence of text `FROM` in the current line is changed to text `TO`. If `TO/` is omitted, the first occurrence of text `FROM` in the current line is deleted.
+If you specify `TO/`, the first occurrence of text `FROM` in the current line is changed to text `TO`. If you omit `TO/`, the first occurrence of text `FROM` in the current line is deleted.
-The following sequence of commands makes line 3 the current line and then changes the department number in the `WHERE` clause from 20 to 30.
+This sequence of commands makes line 3 the current line and then changes the department number in the `WHERE` clause from 20 to 30.
```sql
SQL> LIST
@@ -109,7 +109,7 @@ COL[UMN] [column_name [CLE[AR] |
OFF...]]
```
-If the `COLUMN` command is specified with no other options, formatting options for current columns in effect for the session are displayed.
+If you specify the `COLUMN` command with no other options, formatting options for current columns in effect for the session are displayed.
If the `COLUMN` command is followed by a column name, then the column name can be followed by one of the following:
@@ -119,11 +119,11 @@ If the `COLUMN` command is followed by a column name, then the column name can b
`column_name`
- Name of a column in a table to which column formatting options apply. If no other options follow `column_name`, then the current column formatting option of `column_name`, if any, are displayed.
+ Name of a column in a table to which column formatting options apply. If no other options follow `column_name`, then the current column formatting options of `column_name`, if any, are displayed.
`CLEAR`
- The `CLEAR` option reverts all formatting options back to their defaults for `column_name`. If you specify the `CLEAR` option, it must be the only option specified.
+ The `CLEAR` option reverts all formatting options to their defaults for `column_name`. If you specify the `CLEAR` option, it must be the only option specified.
`format_spec`
@@ -133,7 +133,7 @@ If the `COLUMN` command is followed by a column name, then the column name can b
`n` is a positive integer that specifies the column width in characters within which to display the data. Data in excess of `n` wraps around with the specified column width.
- For numeric columns, `format_spec` is comprised of the following elements.
+ For numeric columns, `format_spec` is made up of the following elements.
| Element | Description |
| ------- | ------------------------------------------ |
@@ -151,9 +151,9 @@ If the `COLUMN` command is followed by a column name, then the column name can b
`NEW_V[ALUE]`
-This variable option is valid if specified alone or with other already supported options. A variable specified in the `COLUMN` command option is associated with the given column. The variable can contain the data value of a column or expression of a variable in the SQL `SELECT` list and can be used in the SQL script for the remainder of the session.
+This variable option is valid if specified alone or with other already supported options. A variable specified in the `COLUMN` command option is associated with the given column. The variable can contain the data value of a column or expression of a variable in the SQL `SELECT` list. You can use it in the SQL script for the rest of the session.
-To contain the `departmentnumber` value for the `deptno` column, a variable can be defined using the `NEW_VALUE` option:
+To contain the `departmentnumber` value for the `deptno` column, you can define a variable using the `NEW_VALUE` option:
```sql
SQL> column deptno new_value departmentnumber
@@ -175,15 +175,15 @@ SQL> INSERT INTO emp VALUES (1,'micheal','tester',7902,'17-DEC-80',800,NULL,'&de
The `NEW_V[ALUE]` variable has the following limitations:
-- Column values differ when they are seeded using the `NEW_VALUE` parameter for the "time with time zone" data type.
-- The `NEW_VALUE` variable prompts for the value if the corresponding column value is `NULL`. Oracle treats `NULL` and an empty string the same while EDB Postgres Advanced Server has a different behavior. Therefore, in EDB*Plus it prompts for the value.
-- The variable value doesn't show in the `COLUMN` header if the user references the `NEW_VALUE` variable in a `SELECT` query without an alias.
+- Column values differ when they're seeded using the `NEW_VALUE` parameter for the "time with time zone" data type.
+- The `NEW_VALUE` variable prompts for the value if the corresponding column value is `NULL`. Oracle treats `NULL` and an empty string the same, while EDB Postgres Advanced Server has a different behavior. Therefore, in EDB\*Plus it prompts for the value.
+- The variable value doesn't show in the `COLUMN` header if you reference the `NEW_VALUE` variable in a `SELECT` query without an alias.
`OFF | ON`
- If `OFF` is specified, formatting options revert to their defaults but are still available in the session. If `ON` is specified, the formatting options specified by previous `COLUMN` commands for `column_name` in the session are reactivated.
+ If you specify `OFF`, formatting options revert to their defaults but are still available in the session. If you specify `ON`, the formatting options specified by previous `COLUMN` commands for `column_name` in the session are reactivated.
-The following example shows the effect of changing the display width of the `job` column.
+This example shows the effect of changing the display width of the `job` column:
```sql
SQL> SET PAGESIZE 9999
@@ -234,7 +234,7 @@ EMPNO ENAME JOB
14 rows retrieved.
```
-The following example applies a format to the `sal` column.
+This example applies a format to the `sal` column:
```sql
SQL> COLUMN sal FORMAT $99,999.00
@@ -290,7 +290,7 @@ EMPNO ENAME JOB SAL
## CONNECT
-Change the database connection to a different user or connect to a different database. There must be no white space between any of the parameters following the `CONNECT` command.
+Change the database connection to a different user or connect to a different database. There must be no white space between any of the parameters following the `CONNECT` command. The syntax is:
```sql
CON[NECT] [/][@{ | } ]
@@ -300,7 +300,7 @@ Where:
`username` is a database user name with which to connect to the database.
- `password` is the password associated with the specified user name. If a `password` isn't provided but a password is required for authentication, a search is made for a password file, first in the home directory of the Linux operating system account invoking EDB\*Plus (or in the `%APPDATA%\postgresql\` directory for Windows) and then at the location specified by the `PGPASSFILE` environment variable. The password file is `.pgpass` on Linux hosts and `pgpass.conf` on Windows hosts. The following is an example on a Windows host:
+ `password` is the password associated with the specified user name. If you don't provide a `password` but a password is required for authentication, a search is made for a password file, first in the home directory of the Linux operating system account invoking EDB\*Plus (or in the `%APPDATA%\postgresql\` directory for Windows) and then at the location specified by the `PGPASSFILE` environment variable. The password file is `.pgpass` on Linux hosts and `pgpass.conf` on Windows hosts. The following is an example on a Windows host:
```text
C:\Users\Administrator\AppData\Roaming\postgresql\pgpass.conf
@@ -311,11 +311,11 @@ C:\Users\Administrator\AppData\Roaming\postgresql\pgpass.conf
!!! Note
When a password isn't required, EDB\*Plus doesn't prompt for a password, such as when the `trust` authentication method is specified in the `pg_hba.conf` file. For more information about the `pg_hba.conf` file and authentication methods, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html).
- `connectstring` is the database connection string. See [Using EDB\*Plus](04_using_edb_plus/#using_edb_plus) for more information on the database connection string.
+ `connectstring` is the database connection string. See [Using EDB\*Plus](04_using_edb_plus/#using_edb_plus) for more information about the database connection string.
- `variable` is a variable defined in the `login.sql` file that contains a database connection string. The `login.sql` file can be found in the `edbplus` subdirectory of the EDB Postgres Advanced Server home directory.
+ `variable` is a variable defined in the `login.sql` file that contains a database connection string. The `login.sql` file is in the `edbplus` subdirectory of the EDB Postgres Advanced Server home directory.
-In the following example, the database connection is changed to database `edb` on the localhost at port 5445 with username `smith`.
+In this example, the database connection is changed to database `edb` on the localhost at port 5445 with username smith.
```sql
SQL> CONNECT smith/mypassword@localhost:5445/edb
@@ -323,7 +323,7 @@ Disconnected from EnterpriseDB Database.
Connected to EnterpriseDB 14.0.0 (localhost:5445/edb) AS smith
```
-In this session, the connection is changed to user name `enterprisedb`. The host defaults to the localhost, the port defaults to 5444 (which isn't the same as the port previously used), and the database defaults to edb.
+In this session, the connection is changed to user name enterprisedb. The host defaults to the localhost, the port defaults to 5444 (which isn't the same as the port previously used), and the database defaults to `edb`.
```sql
SQL> CONNECT enterprisedb/password
@@ -339,13 +339,13 @@ The `DEFINE` command creates or replaces the value of a *user variable* (also ca
DEF[INE ] [ variable [ = text ] ]
```
-If the `DEFINE` command is given without any parameters, all current variables and their values are displayed.
+If you give the `DEFINE` command without any parameters, all current variables and their values are displayed.
If `DEFINE variable` is given, only `variable` is displayed with its value.
-`DEFINE variable = text` assigns `text` to `variable.text`, which can be optionally enclosed in single or double quotation marks. Quotation marks must be used if `text` contains space characters.
+`DEFINE variable = text` assigns `text` to `variable.text`, which you can optionally enclose in single or double quotation marks. Quotation marks must be used if `text` contains space characters.
-The following example defines two variables, `dept` and `name`.
+This example defines two variables, `dept` and `name`:
```sql
SQL> DEFINE dept = 20
@@ -371,7 +371,7 @@ The parameters specify the lines to delete from the SQL buffer. Two parameters s
`n`
- n is an integer representing the nth line.
+ `n` is an integer representing the nth line.
`n m`
@@ -379,13 +379,13 @@ The parameters specify the lines to delete from the SQL buffer. Two parameters s
`*`
- Current line
+ Current line.
`LAST`
- Last line
+ Last line.
-In the following example, the fifth and sixth lines containing columns `sal` and `comm`, respectively, are deleted from the `SELECT` command in the SQL buffer.
+This example deletes the fifth and sixth lines, which contain columns `sal` and `comm`, respectively, from the `SELECT` command in the SQL buffer.
```sql
SQL> LIST
@@ -423,7 +423,7 @@ DESC[RIBE] [ schema.]object
`schema`
- Name of the schema containing the object to be described.
+ Name of the schema containing the object to describe.
`object`
@@ -447,7 +447,7 @@ ED[IT ] [ filename[.ext ] ]
`filename[.ext ]`
- `filename` is the name of the file to open with an external editor. `ext` is the file name extension. If the file name extension is `sql`, then you can omit the `.sql`. `EDIT` always assumes a `.sql` extension on file names that are specified with no extension. If the `filename` parameter is omitted from the `EDIT` command, the contents of the SQL buffer are brought into the editor.
+ `filename` is the name of the file to open with an external editor. `ext` is the filename extension. If the extension is `sql`, then you can omit it. (`EDIT` assumes a `.sql` extension on filenames that are specified with no extension.) If you omit the `filename` parameter from the `EDIT` command, the contents of the SQL buffer are brought into the editor.
## EXECUTE
@@ -475,7 +475,7 @@ The `EXIT` command ends the EDB\*Plus session and returns control to the operati
[ COMMIT | ROLLBACK ]SUCCESS | FAILURE |WARNING]
```
-Returns an operating system dependent return code indicating successful operation, failure, or warning for `SUCCESS, FAILURE`, and `WARNING`, respectively. The default is `SUCCESS`.
+Returns an operating-system-dependent return code indicating successful operation, failure, or warning for `SUCCESS`, `FAILURE`, and `WARNING`, respectively. The default is `SUCCESS`.
`value`
@@ -487,7 +487,7 @@ Returns an operating system dependent return code indicating successful operatio
`COMMIT | ROLLBACK`
- If `COMMIT` is specified, uncommitted updates are committed upon exit. If `ROLLBACK` is specified, uncommitted updates are rolled back upon exit. The default is `COMMIT`.
+ If you specify `COMMIT`, uncommitted updates are committed upon exit. If you specify `ROLLBACK`, uncommitted updates are rolled back upon exit. The default is `COMMIT`.
## GET
@@ -499,15 +499,15 @@ GET filename[.ext ] [ LIS[T ] | NOL[IST ] ]
`filename[.ext ]`
- `filename` is the name of the file to load into the SQL buffer. `ext` is the file name extension. If the file name extension is `sql`, then you can omit the `.sql` extension. `GET` always assumes a `.sql` extension on file names that are specified with no extension.
+ `filename` is the name of the file to load into the SQL buffer. `ext` is the filename extension. If the extension is `sql`, then you can omit it. `GET` assumes a `.sql` extension on filenames that are specified with no extension.
`LIST | NOLIST`
- If `LIST` is specified, the content of the SQL buffer is displayed after the file is loaded. If `NOLIST` is specified, no listing is displayed. The default is `LIST`.
+ If you specify `LIST`, the contents of the SQL buffer are displayed after the file is loaded. If you specify `NOLIST`, no listing is displayed. The default is `LIST`.
## HELP
-The `HELP` command obtains an index of topics or help on a specific topic. The question mark `(?)` is synonymous with specifying `HELP`.
+The `HELP` command gets an index of topics or help on a specific topic. The question mark `(?)` is synonymous with specifying `HELP`.
```sql
{ HELP | ? } { INDEX | topic }
@@ -541,7 +541,7 @@ The `INPUT` command adds a line of text to the SQL buffer after the current line
I[NPUT ] text
```
-The following sequence of `INPUT` commands constructs a `SELECT` command.
+This sequence of `INPUT` commands constructs a `SELECT` command:
```sql
SQL> INPUT SELECT empno, ename, job, sal, comm
@@ -605,7 +605,7 @@ Use the `PASSWORD` command to change your database password.
PASSW[ORD] [user_name]
```
-You must have privileges to use the `PASSWORD` command to change another user's password. The following example uses the `PASSWORD` command to change the password for a user named `acctg`:
+You must have privileges to use the `PASSWORD` command to change another user's password. This example uses the `PASSWORD` command to change the password for a user named acctg:
```sql
SQL> PASSWORD acctg
@@ -623,7 +623,7 @@ The `PAUSE` command displays a message and waits for the user to press `ENTER`.
PAU[SE] [optional_text]
```
-`optional_text` specifies the text to display to the user. If `optional_text` is omitted, EDB Postgres Advanced Server displays two blank lines. If you double quote the `optional_text` string, the quotes are included in the output.
+`optional_text` specifies the text to display to the user. If you omit `optional_text`, EDB Postgres Advanced Server displays two blank lines. If you double quote the `optional_text` string, the quotes are included in the output.
## PROMPT
@@ -661,7 +661,7 @@ You can also use the following convention to include a comment:
```text
/*
- * This is an example of a three line comment.
+ * This is an example of a three-line comment.
*/
```
@@ -676,7 +676,7 @@ SAV[E] file_name
`file_name`
- `file_name` specifies the name of the file (including the path) where the buffer contents are written. If you don't provide a file extension, `.sql` is appended to the end of the file name.
+ `file_name` specifies the name of the file (including the path) where the buffer contents are written. If you don't provide a file extension, `.sql` is appended to the end of the filename.
`CREATE`
@@ -690,7 +690,7 @@ SAV[E] file_name
Include the `APPEND` keyword to append the contents of the SQL buffer to the end of the specified file.
-The following example saves the contents of the SQL buffer to a file named `example.sql`, located in the `temp` directory:
+This example saves the contents of the SQL buffer to a file named `example.sql`, located in the `temp` directory:
```sql
SQL> SAVE C:\example.sql CREATE
@@ -699,7 +699,7 @@ File "example.sql" written.
## SET
-Use the `SET` command to specify a value for a session-level variable that controls EDB\*Plus behavior. The following forms of the `SET` command are valid:
+Use the `SET` command to specify a value for a session-level variable that controls EDB\*Plus behavior. The following forms of the `SET` command are valid.
### SET AUTOCOMMIT`
@@ -803,7 +803,7 @@ SET LIN[ESIZE] width_of_line
### SET NEWPAGE
-Use the `SET NEWPAGE` command to specify how many blank lines are printed after a page break.
+Use the `SET NEWPAGE` command to specify how many blank lines to print after a page break.
```sql
SET NEWP[AGE] lines_per_page
@@ -859,11 +859,11 @@ The `SET PAUSE` command is most useful when included in a script. The command di
SET PAU[SE] {ON | OFF}
```
-If `SET PAUSE` is `ON`, the message `Hit ENTER to continue…` appears before each command is executed.
+If `SET PAUSE` is `ON`, the message `Hit ENTER to continue…` appears before each command executes.
### SET SPACE
-Use the `SET SPACE` command to specify the number of spaces to display between columns:
+Use the `SET SPACE` command to specify the number of spaces to display between columns.
```sql
SET SPACE number_of_spaces
@@ -871,7 +871,7 @@ SET SPACE number_of_spaces
### SET SQLPROMPT
-Use `SET SQLPROMPT` to set a value for a user-interactive prompt:
+Use `SET SQLPROMPT` to set a value for a user-interactive prompt.
```sql
SET SQLP[ROMPT] "prompt"
@@ -969,11 +969,11 @@ The `SPOOL` command sends output from the display to a file.
SP[OOL] output_file | OFF
```
-Use the `output_file` parameter to specify a path name for the output file.
+Use the `output_file` parameter to specify a pathname for the output file.
## START
-Use the `START` command to run an EDB\*Plus script file. `START` is an alias for `@` command.
+Use the `START` command to run an EDB\*Plus script file. `START` is an alias for the `@` command.
```sql
STA[RT] script_file
@@ -1004,17 +1004,17 @@ WHENEVER SQLERROR
If EDB Postgres Advanced Server encounters an error while executing a SQL command or PL/SQL block, EDB\*Plus performs the action specified in the `WHENEVER SQLERROR` command:
- Include the `CONTINUE` clause to perform the specified action before continuing.
+- Include the `CONTINUE` clause to perform the specified action before continuing.
- Include the `COMMIT` clause to commit the current transaction before exiting or continuing.
+- Include the `COMMIT` clause to commit the current transaction before exiting or continuing.
- Include the `ROLLBACK` clause to roll back the current transaction before exiting or continuing.
+- Include the `ROLLBACK` clause to roll back the current transaction before exiting or continuing.
- Include the `NONE` clause to continue without committing or rolling back the transaction.
+- Include the `NONE` clause to continue without committing or rolling back the transaction.
- Include the `EXIT` clause to perform the specified action and exit in case of an error.
+- Include the `EXIT` clause to perform the specified action and exit in case of an error.
- Use the following options to specify a status code that EDB\*Plus returns before exiting:
+Use the following options to specify a status code that EDB\*Plus returns before exiting:
```sql
[SUCCESS|FAILURE|WARNING|n|sub_variable]
From ad0d07e50ea7d519e9abcc32fc927bd69bc78b7f Mon Sep 17 00:00:00 2001
From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com>
Date: Thu, 13 Jul 2023 12:15:31 -0400
Subject: [PATCH 12/19] Update 06_command_summary.mdx
---
product_docs/docs/edb_plus/41/06_command_summary.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/product_docs/docs/edb_plus/41/06_command_summary.mdx b/product_docs/docs/edb_plus/41/06_command_summary.mdx
index a668e5f3384..f83c7ae75b6 100644
--- a/product_docs/docs/edb_plus/41/06_command_summary.mdx
+++ b/product_docs/docs/edb_plus/41/06_command_summary.mdx
@@ -55,7 +55,7 @@ SQL> LIST
C[HANGE ] FROM [ TO ]
```
-If you specify `TO/`, the first occurrence of text `FROM` in the current line is changed to text `TO`. If you omit `TO/`, the first occurrence of text `FROM` in the current line is deleted.
+If you specify `TO/`, the first occurrence of the text `FROM` in the current line is changed to text `TO`. If you omit `TO/`, the first occurrence of the text `FROM` in the current line is deleted.
This sequence of commands makes line 3 the current line and then changes the department number in the `WHERE` clause from 20 to 30.
From a587aa14a2e49ea2697c7729dce86dab3b600f05 Mon Sep 17 00:00:00 2001
From: Kashif Zeeshan
Date: Mon, 10 Jul 2023 17:00:05 +0500
Subject: [PATCH 13/19] Connect CDC Guide
Connect CDC Guide
---
.../02-PartnerInformation.mdx | 12 +
.../03-SolutionSummary.mdx | 14 +
.../04-Configuratingpreciselyconnectcdc.mdx | 50 +++
.../05-Usingpreciselyconnectcdc.mdx | 309 ++++++++++++++++++
.../06-CertificationEnvironment.mdx | 10 +
.../PreciselyConnectCDC/07-Support.mdx | 42 +++
.../PreciselyConnectCDC/Images/46.png | 3 +
.../Images/ConnectCDCSolutionSummary.png | 3 +
.../Images/PartnerProgram.png | 3 +
.../PreciselyConnectCDC/Images/Process.png | 3 +
.../Images/availabletables.png | 3 +
.../Images/configureepas.png | 3 +
.../Images/confirmtablesontarget.png | 3 +
.../PreciselyConnectCDC/Images/connectcdc.png | 3 +
.../Images/copyrequest.png | 3 +
.../Images/datatransformation1.png | 3 +
.../Images/datatransformation2.png | 3 +
.../Images/distributetables.png | 3 +
.../Images/distributionmodel.png | 3 +
.../PreciselyConnectCDC/Images/distrmodel.png | 3 +
.../Images/doneprepareuserdatabase.png | 3 +
.../PreciselyConnectCDC/Images/idpassword.png | 3 +
.../Images/idpassword1.png | 3 +
.../Images/installmetabase.png | 3 +
.../Images/metabasesucces.png | 3 +
.../Images/modelcommit.png | 3 +
.../Images/newdistribution.png | 3 +
.../PreciselyConnectCDC/Images/newhost.png | 3 +
.../PreciselyConnectCDC/Images/newmodel.png | 3 +
.../PreciselyConnectCDC/Images/newserver.png | 3 +
.../PreciselyConnectCDC/Images/pgAdmin.png | 3 +
.../Images/pgAdmincopydone.png | 3 +
.../Images/pgAdmincopydone2.png | 3 +
.../Images/pgAdmintargettables.png | 3 +
.../PreciselyConnectCDC/Images/pgadming.png | 3 +
.../Images/prepareuserdatabase.png | 3 +
.../Images/prepareuserdatabase2.png | 3 +
.../Images/prepareuserdatabasesuccess.png | 3 +
.../Images/refreshtables.png | 3 +
.../Images/replicationrequest.png | 3 +
.../Images/replicationrequest2.png | 3 +
.../Images/replicationrequest3.png | 3 +
.../Images/rpuserpassword.png | 3 +
.../PreciselyConnectCDC/Images/schema2.png | 3 +
.../Images/schematoreplicate.png | 3 +
.../Images/selecttableforreplication.png | 3 +
.../Images/successserver.png | 3 +
.../Images/tablemappings.png | 3 +
.../Images/targetmetabasecreated.png | 3 +
.../Images/targetpgadmin.png | 3 +
.../Images/targetserver.png | 3 +
.../Images/targetserverlogin.png | 3 +
.../Images/targetserveruserpass.png | 3 +
.../Images/targettablescreen.png | 3 +
.../Images/targetuserpassword.png | 3 +
.../Images/targtemetbase.png | 3 +
.../Images/tstconnection.png | 3 +
.../Images/userpassword.png | 3 +
.../PreciselyConnectCDC/Images/validmodel.png | 3 +
.../PreciselyConnectCDC/index.mdx | 14 +
src/pages/index.js | 23 +-
61 files changed, 616 insertions(+), 17 deletions(-)
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/02-PartnerInformation.mdx
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/03-SolutionSummary.mdx
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/04-Configuratingpreciselyconnectcdc.mdx
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/05-Usingpreciselyconnectcdc.mdx
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/06-CertificationEnvironment.mdx
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/07-Support.mdx
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/46.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/ConnectCDCSolutionSummary.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/PartnerProgram.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/Process.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/availabletables.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/configureepas.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/confirmtablesontarget.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/connectcdc.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/copyrequest.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/datatransformation1.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/datatransformation2.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/distributetables.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/distributionmodel.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/distrmodel.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/doneprepareuserdatabase.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/idpassword.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/idpassword1.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/installmetabase.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/metabasesucces.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/modelcommit.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newdistribution.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newhost.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newmodel.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newserver.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmin.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmincopydone.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmincopydone2.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmintargettables.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgadming.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/prepareuserdatabase.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/prepareuserdatabase2.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/prepareuserdatabasesuccess.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/refreshtables.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/replicationrequest.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/replicationrequest2.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/replicationrequest3.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/rpuserpassword.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/schema2.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/schematoreplicate.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/selecttableforreplication.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/successserver.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/tablemappings.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetmetabasecreated.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetpgadmin.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetserver.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetserverlogin.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetserveruserpass.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targettablescreen.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetuserpassword.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targtemetbase.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/tstconnection.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/userpassword.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/Images/validmodel.png
create mode 100644 advocacy_docs/partner_docs/PreciselyConnectCDC/index.mdx
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/PreciselyConnectCDC/02-PartnerInformation.mdx
new file mode 100644
index 00000000000..4e1aa84fc81
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/02-PartnerInformation.mdx
@@ -0,0 +1,12 @@
+---
+title: 'Partner Information'
+description: 'Details of the partner'
+
+---
+| | |
+| ----------- | ----------- |
+| **Partner Name** | Precisely |
+| **Partner Product** | Precisely Connect CDC (Change Data Capture) |
+| **Web Site** | https://www.precisely.com/ |
+| **Version** | Precisely Connect CDC V5.8 |
+| **Product Description** | Precisely Connect CDC (Change Data Capture) provides real-time data replication and change data capture functionality. Integrate data seamlessly from legacy systems into next-gen cloud and data platforms with one solution. Seamless data access and collection, Precisely Connect CDC helps you take control of your data from mainframe to cloud. Integrate data through batch and real-time ingestion for advanced analytics, comprehensive machine learning and seamless data migration. Precisely Connect CDC leverages the expertise Precisely has built over decades as a leader in mainframe sort and IBM i data availability and security. Access to all your enterprise data for the most critical business projects is ensured by support for a wide range of sources and targets for all your ETL and change data capture (CDC) needs including EDB Postgres Advanced Server and PostgreSQL. |
\ No newline at end of file
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/03-SolutionSummary.mdx b/advocacy_docs/partner_docs/PreciselyConnectCDC/03-SolutionSummary.mdx
new file mode 100644
index 00000000000..59089ef5405
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/03-SolutionSummary.mdx
@@ -0,0 +1,14 @@
+---
+title: 'Solution Summary'
+description: 'Explanation of the solution and its purpose'
+---
+
+Precisely Connect CDC (Change Data Capture) provides real-time data replication and change data capture functionality. Precisely Connect CDC real-time replication ensures that databases are in-sync for reporting, analytics, and data warehousing. You can replicate changes as they happen across hierarchical data stores (IMS, VSAM), relational databases, streaming frameworks, and the cloud.
+
+Precisely Connect CDC supports EDB Postgres Advanced Server and PostgreSQL databases in different modes as either a source or target database for real-time data replication and change data capture functionality.
+
+
+ 
+
+
+EDB Postgres Advanced Server and PostgreSQL can be either the Source Database or Target Database in the diagram dependent on your configuration.
\ No newline at end of file
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/04-Configuratingpreciselyconnectcdc.mdx b/advocacy_docs/partner_docs/PreciselyConnectCDC/04-Configuratingpreciselyconnectcdc.mdx
new file mode 100644
index 00000000000..fb221639d72
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/04-Configuratingpreciselyconnectcdc.mdx
@@ -0,0 +1,50 @@
+---
+title: 'Configuration'
+description: 'Walkthrough on configuring the integration'
+---
+
+## Prerequisites
+
+Implementing Precisely Connect CDC with EDB Postgres Advanced Server requires the following components:
+
+!!! Note
+ The EDB Postgres Advanced Server, EDB Postgres Extended Server and PostgreSQL Server products will be referred to as Postgres Distribution. The specific Distribution type will be dependent upon customer need or preference.
+
+- Precisely supported source and target systems. The source, target or both can be your Postgres Distribution(s). In our example we will be using EDB Postgres Advanced Server for both the source and target database.
+- Precisely Connect CDC software.
+- PostgreSQL management tool such as pgAdmin or Postgres Enterprise Manager. In our example we will use pgAdmin. This tool will be used to verify that the data is being replicated as expected.
+
+## Configuring your PostgreSQL Distribution
+
+These components are needed before integrating PostgreSQL Distribution with Precisely Connect CDC:
+
+1. Two running instances of EDB Postgres Advanced Server.
+
+2. pgAdmin must be installed on the Source and Target EDB Postgres Advanced Server instances.
+
+3. A running instance of Precisely Connect CDC.
+
+
+
+## Enable WAL Archiving
+
+The following steps demonstrate how to enable WAL Archiving on the Source EDB Postgres Advanced Server instance, which is required for Precisely Connect CDC’s replication functionality.
+
+1. Go to the installation directory of EDB Postgres Advanced Server (e.g `C:\Program Files\edb\as14\`).
+
+2. Go to the data directory and open the postgresql.conf file.
+
+3. Modify the following settings as per the given values.
+
+```yaml
+archive_mode = on
+wal_level = logical
+archive_command = 'copy "%p" "C:\\archive_wal_directory\\%f"'
+max_replication_slots = 20
+
+```
+
+4. Restart the EDB Postgres Advanced Server Source instance.
+
+!!! Note
+ No configuration e.g WAL Archiving is required on Target EDB Postgres Advanced Server instance.
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/05-Usingpreciselyconnectcdc.mdx b/advocacy_docs/partner_docs/PreciselyConnectCDC/05-Usingpreciselyconnectcdc.mdx
new file mode 100644
index 00000000000..f82cde1d236
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/05-Usingpreciselyconnectcdc.mdx
@@ -0,0 +1,309 @@
+---
+title: 'Using'
+description: 'Walkthrough of example usage scenarios'
+---
+
+After you have configured your EDB Postgres Distribution, as stated in the Configuring section, you will be able to then use Precisely CDC's Replication functionality. For the examples in this guide, the replication functionality is demonstrated using EDB Postgres Advanced Server.
+
+- Configure Postgres Distribution as a Source Instance in Connect CDC Director
+ - Setup and configuration of EDB Postgres Advanced Server as a source instance for Connect CDC Director.
+- Configure Postgres Distribution as Target Instance in Connect CDC Director
+ - Setup and configuration of EDB Postgres Advanced Server as target instance to Connect CDC Director.
+- Create Distribution on Connect CDC Director
+ - Define how data will be replicated from source to target in a Model.
+- Save the Model
+ - Save, validate and commit the Model created for Replication.
+- Execute Copy Replication using Connect CDC MonCon
+ - Execute the Copy Replication to copy all the data from the Source Tables to the Target Tables.
+- Create Replication Distribution using Connect CDC Director
+ - Replicate all the changes made on the Source Tables to the Target Tables.
+- Execute Replication using Connect CDC MonCon
+ - Replication distribution will replicate all the changes done on the Source Tables to the Target Tables.
+
+With Precisely Connect CDC you also have the ability to “Transform” your data as you replicate it from a source to target using Data Transformation. See the section on “Data Transformation” on how to enable this feature.
+
+- Data Transformation
+ - Modify the source data you are distributing or even create or derive the data you distribute to the target system.
+
+
+## Configure Postgres Distribution as a Source Instance in Connect CDC Director
+
+The following steps demonstrate the setup and configuration of EDB Postgres Advanced Server as a source instance for Connect CDC Director.
+
+1. Open Connect CDC Director.
+
+2. Click `New` option.
+
+3. Right click `Hosts, Servers, Tables` and select `New Host`.
+
+4. Enter information for the `Host`, `Host` is the machine where Connect CDC Director is running.
+
+
+
+5. Right Click on the newly added `Host` and select `Test Connection`, a success message will be displayed.
+
+6. Right Click on the newly added `Host` and select `New Server`.
+
+7. Enter Connection Information for EDB Postgres Advanced Server as `Source` Instance (Server name is where the database name is given).
+
+
+
+8. Right Click on the newly added `Server` and select `Install Source Metabase`.
+
+9. Provide EDB Postgres Advanced Server Source Instance User and Password on `User ID and Password` Screen.
+
+10. Provide password of `rpuser` (refer to the user name and password given on `New Server` Screen) when prompted on the User ID and Password screen.
+
+!!! Note
+ `rpuser` is the replication user added by default by Precisely Connect CDC.
+
+11. Click Ok on `Install Source Metabase` screen.
+
+12. A success message will be displayed once the `Source Metabase` is created on the EDB Postgres Advanced Server `Source` Instance.
+
+13. Open pgAdmin and connect to your EDB Postgres Advanced Server Source instance, navigate to Schemas and under the Schemas `rpuser` Schema has been created.
+
+
+
+14. Navigate back to Connect CDC Director and right Click on the newly added Server and select `Test Connection`. A success message will be displayed.
+
+15. Right Click on the newly added `Server` and select `Prepare User Database`, this will add the replication user to the public database.
+
+16. On `Database/Schema name` Screen provide the schema name for the schema you wish to replicate. In our example we are using schema `public`.
+
+17. On the `User ID and Password` Screen, provide EDB Postgres Advanced Server Source Instance `User` and `Password`.
+
+18. Click Ok on `Prepare User Database` Screen.
+
+19. A success message will be displayed once the `Prepare User Database` operation is successful.
+
+20. Right Click on the newly added `Server` and select `Refresh Available Tables`.
+
+21. Click on the Refresh list and then select schema `public` and click ok.
+
+
+
+22. To display the available tables click newly added `Server` —> `Tables` —> `Available Tables` —> `Public` (Schema name), a list of available tables will be displayed.
+
+
+
+## Configure Postgres Distribution as Target Instance in Connect CDC Director
+
+The following steps demonstrate the setup and configuration of EDB Postgres Advanced Server as target instance to Connect CDC Director.
+
+1. Right click `DBMS Servers` and `New Server`.
+
+2. Provide Connection Information for the EDB Postgres Advanced Server Target Instance.
+
+
+
+3. Right Click on the newly added `Server` and select `Install Target Only Metabase`.
+
+4. Provide EDB Postgres Advanced Server Target Instance User and Password on `User ID and Password` Screen.
+
+5. Provide password of `rpuser` (refer to the user name and password given on `New Server` Screen) when prompted on the `User ID and Password` screen.
+
+6. Click Ok on `Install Target Only Metabase` screen.
+
+7. A success message will be displayed once the `Target Only Metabase` is created.
+
+8. Open pgAdmin and connect to EDB Postgres Advanced Server `Target` Instance, and under Schemas `rpuser` Schema is created.
+
+
+
+9. Right Click on the newly added `Server` and select `Prepare User Database`, this will add the replication user to EDB Postgres Advanced Server Target Instance.
+
+10. On `Database/Schema Name` provide schema name `public`.
+
+11. On `User ID and Password` Screen, provide EDB Postgres Advanced Server Target Instance user and password.
+
+12. Click Ok on the `Prepare User Database` screen.
+
+13. A success message will be displayed once the `Prepare User Database` is successful.
+
+## Create Distribution on Connect CDC Director
+
+The following steps demonstrate the creation of Distribution which will define how data will be replicated from source to target. In our case from EDB Postgres Advanced Server source to EDB Postgres Advanced Server target.
+
+1. Open Connect CDC Director.
+
+2. Right click on `Distributions` and select `New Distribution`.
+
+3. Enter Distribution information e.g `distribution name`, `description` etc and click ok.
+
+
+
+4. Go to Source DBMS `Server` —> `Tables` —> `Available Tables` —> `Public` (Schema name).
+
+5. Select the table(s) to replicate using the checking box in front of them and right click and select `Select for Distribution` —> `All Checked Tables`.
+
+
+
+6. On the `Distributed Tables` Screen, select the `Target Server` under `Select one or more target servers` and select `Create tables on target` option and select the distribution under `Select a Distribution` option and click ok.
+
+
+
+7. On Connect CDC Director Screen, select Yes.
+
+8. On the `Target Tables` Screen, enter the Target Schema against each table and Click Next.
+
+
+
+9. On `Target Server Login Details` Screen, enter EDB Postgres Advanced Server Target Instance user and password and click test connect. Once successful, click Add and then click `Create`.
+
+
+
+10. Once done, click `Finish`.
+
+11. To confirm the tables are created on `Target Server`, click the `Target DBMS Server` —> `Tables` —> `Receiving Tables`, the list of the tables will be displayed which are available on `Source DBMS Server`.
+
+
+
+12. Open pgAdmin and connect to EDB Postgres Advanced Server Target Instance, and under Schema `public`, the tables will be created.
+
+
+
+13. Mappings of tables setup for replication from EDB Postgres Advanced Server Source Instance to EDB Postgres Advanced Server Target Instance will be created under `Distributions` —> `Mappings`.
+
+
+
+14. Open `Distributions` —> `Newly Created Distribution` —> `Requests` —> `New Request` —> `Copy`. Copy will copy/replicate all the data in tables from EDB Postgres Advanced Server Source Instance to EDB Postgres Advanced Server Target Instance.
+
+15. Provide required information and click Ok on `Copy Request Properties` Screen.
+
+
+
+## Save the Model
+
+The Model created in the above steps needs to be saved, validated and committed before the Replication can be performed.
+
+1. To save the Model, click `File` and select `Save` option and provide the name for the `Model`.
+
+2. Right Click `Enterprise Data Movement Model` and select `Validate` to validate the Model.
+
+3. No error will be displayed if the Model is valid.
+
+
+
+4. Right Click `Enterprise Data Movement Model` and select `Commit` —> `Full`.
+
+
+
+5. Click Ok on `Commit Model` Screen. This will create the `Model` files.
+
+## Execute Copy Replication using Connect CDC MonCon
+
+Connect CDC MonCon is a GUI application, separate from the Connect CDC Director, that you use for monitoring and control functions. We will use Connect CDC MonCon to execute the Copy Replication. Copy Replication will copy all the data from the Source Tables to the Target Tables.
+
+1. Open Connect CDC MonCon.
+
+2. Click `Model` —> `New Model` from Menu.
+
+3. Provide `Hostname/IP` and select the saved `Model` from the drop down list.
+
+
+
+4. In the `Request` Section, select the `Distribution Model` that was created for copying data created in the above steps and right click and select `start`.
+
+
+
+5. Click on `Process` to see the progress.
+
+
+
+6. Open pgAdmin once the copy operation is completed successfully and connect the EDB Postgres Advanced Server Target Instance and check the tables and the data is copied to the tables.
+
+
+
+
+
+## Create Replication Distribution using Connect CDC Director
+
+Once the Copy replication operation is successful then a Replication option will be executed which will replicate all the changes made on the Source Tables to the Target Tables.
+
+1. Open Connect CDC Director.
+
+2. Create the `Replication Request` from `Distributions` —> `Newly Created Distribution` —> `Requests` —> `New Request` —> `Replication`.
+
+3. Enter the name and press `Ok`.
+
+
+
+
+
+4. Save the changes in the `Model`.
+
+5. Right Click `Enterprise Data Movement Model` and select `Validate` to validate the Model.
+
+6. Right Click `Enterprise Data Movement Model` and select `Commit` —> `Full`.
+
+7. Click Ok on `Commit Model` Screen. This will create the Model files.
+
+## Execute Replication using Connect CDC MonCon
+
+Replication distribution will replicate all the changes done on the Source Tables to the Target Tables.
+
+1. Open Connect CDC MonCon.
+
+2. As the Model is updated in the Connect CDC Director to add the `Replication Distribution`, click on the `Model Update`, this will add the `Replication Distribution` to the Connect CDC MonCon Interface.
+
+3. The replication request will be displayed once the `Model` is updated successfully.
+
+
+
+4. In the `Request` Section, select the `Distribution Model` created for Replication and right click and select `Start`.
+
+
+
+5. On the `Source Instance`, update the data to be replicated in the `Source Tables`.
+
+6. On the `Target Instance`, check data in the `Target Tables`, data will be updated there.
+
+
+
+## Data Transformation
+
+Precisely Connect CDC has options that let you modify the source data you are distributing or even create or derive the data you distribute. You can use predefined functions to accomplish these data transformations or you can construct your own operations or functions.
+
+For example, to express source currency values in terms of a different currency, you specify the transformation algorithm to use for that column mapping. For some common transformations, the algorithm is supplied as a predefined Connect CDC function.
+
+The algorithms you specify are known in the Connect CDC Director as expressions. The Connect CDC Expression Handler parses them and then creates runtime code that calculates the result for the expressions.
+
+In addition to or instead of calls to predefined functions, expressions may have an arbitrary number of constants, column references, and calculations on those constants and columns and functions. Their results must be compatible in type and length with the target column.
+
+### Steps to demonstrate data transformations
+
+The following steps demonstrate data transformations.
+
+1. Open Connect CDC Director.
+
+2. Go to `Source DBMS Server` —> `Tables` —> `Sending Tables`.
+
+3. Select the table(s) to perform data transformation using the checking box in front of them and right click and select `Properties` —> `Mappings`.
+
+4. On the `Mapping` tab, you define the column mappings for each of your target tables with respect to the source tables. The `Mapping` tab displays the corresponding columns in the `Target Column` and `Source Data` columns in each row. Connect CDC Director automatically mapped target columns to source columns that have the same name.
+
+When the Connect CDC Director maps a source table to a same-named target table, it also associates individual source table columns with same-named target table columns. You then select which of these column pairings you want to include in your data distribution, which additional column pairings you want to arrange, and what type of data transformation, if any, you want to assign to each column pairing.
+
+Mappings Tab has the following options
+
+ - Receiving server list : The name of the target server is displayed.
+ - Receiving table list : The name of the target table is displayed. If it does not (for example, because its name does not match your source table’s), select the target table from the Receiving table list. The list includes all tables in the list of Available tables for the target server. Any table name with [M]preceding it is already mapped to a source table.
+
+The Mapping tab grid displays each target table column and its datatype as well as its default corresponding source column, if any. Copy column under Method in the grid means the source column value is to be distributed without any special handling or transformation.
+
+ - Target Column : Contains all the columns in the target table.
+ - Datatype : Datatype of the column for both Source and Target tables as per the mapping defined between source and target table.
+ - Source Data : Contains all the columns in the Source table.
+ - DKey : This column identifies the Distribution Key. By default, DKey is marked for the Primary key. You can deselect the default and add as many check marks as necessary.
+ - Method : It contains a list of data transformation functions.
+
+5. In our example, click on `Method` drop down list for the target column loc and select lower case, this data transformation will convert the data in loc column of target table to lower case after the replication is done.
+
+
+
+6. Perform the replication from Connect CDC MonCon.
+
+7. On the Target Instance, check data in the Target Table dept, data will be transformed for column loc and it will be stored as lower case.
+
+
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/PreciselyConnectCDC/06-CertificationEnvironment.mdx
new file mode 100644
index 00000000000..e7eb95e39b3
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/06-CertificationEnvironment.mdx
@@ -0,0 +1,10 @@
+---
+title: 'Certification Environment'
+description: 'Overview of the Certification Environment'
+---
+
+| | |
+| ----------- | ----------- |
+| **Certification Test Date** | June 12, 2023 |
+| **EDB Postgres Advanced Server** | 15,14,13,12 |
+| **Precisely Connect CDC** | 5.8 |
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/07-Support.mdx b/advocacy_docs/partner_docs/PreciselyConnectCDC/07-Support.mdx
new file mode 100644
index 00000000000..d61d02a3bfc
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/07-Support.mdx
@@ -0,0 +1,42 @@
+---
+title: 'Support and Logging Details'
+description: 'Details of the Support process and logging information'
+---
+
+## Support
+
+Technical support for the use of these products is provided by both EDB and Precisely. A proper support contract is required to be in place at both EDB and Precisely. A support ticket can be opened on either side to start the process. If it is determined through the support ticket that resources from the other vendor is required, the customer should open a support ticket with that vendor through normal support channels. This will allow both companies to work together to help the customer as needed.
+
+## Logging
+
+**EDB Postgres Advanced Server Logs:**
+
+Navigate to the `Data` directory in your chosen EDB Postgres Advanced Server instance and from here you can navigate to `log`, `current_logfiles` or you can navigate to the `postgresql.conf` file where you can customize logging options or enable `edb_audit` logs.
+
+**PostgreSQL Logs**
+
+The default log directories for PostgreSQL logs vary depending on the operating system:
+
+- Debian-based system: `/var/log/postgresql/postgresql-x.x.main.log. X.x.`
+
+- Red Hat-based system: `/var/lib/pgsql/data/pg_log`
+
+- Windows: `C:\Program Files\PostgreSQL\9.3\data\pg_log`
+
+**Precisely Logs**
+
+To collect the logs from your Precisely Connect CDC instance:
+
+**Get logs with Connect CDC Director**
+
+1. Open Connect CDC Director.
+
+2. Click the Tools button.
+
+3. Log File name and location will be displayed under Log File.
+
+**Get logs with Connect CDC MonCon**
+
+1. Open Connect CDC MonCon.
+
+2. The Connect CDC MonCon log file is located in the Connect CDC program directory in the kernel subdirectory. The name of the file is moncon.log.
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/46.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/46.png
new file mode 100644
index 00000000000..5f058139a66
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/46.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:017096c26e329899f34e4563923251b2e586d6cdd81df124e7b19915a8881552
+size 128108
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/ConnectCDCSolutionSummary.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/ConnectCDCSolutionSummary.png
new file mode 100644
index 00000000000..0f5ff512b88
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/ConnectCDCSolutionSummary.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:05a170f7afba609350fc4fdd07c2397a31e267424f5144127e28ed007409cfa7
+size 145973
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/PartnerProgram.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/PartnerProgram.png
new file mode 100644
index 00000000000..a51f268a007
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/PartnerProgram.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6dddb2403778294d50b9c500a3b961fc5ed0aa764d4c425cd44c1c90193915e5
+size 9855
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/Process.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/Process.png
new file mode 100644
index 00000000000..fa9463c897f
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/Process.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:598cf89fa0ccd9d5ba1ce07da9a052e7b24c120b3900cdee9a89e9ba074ed8de
+size 447896
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/availabletables.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/availabletables.png
new file mode 100644
index 00000000000..afe04a48b2d
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/availabletables.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9212ae60696227d4efd97cd8ae219d6f46e6291f58f6eb9614c8928b7ae619de
+size 79242
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/configureepas.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/configureepas.png
new file mode 100644
index 00000000000..36ed6645947
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/configureepas.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a763c0c16e37b20553375c3bc29af239d504997cfa01a0e14e9ae80d05872c7c
+size 282726
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/confirmtablesontarget.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/confirmtablesontarget.png
new file mode 100644
index 00000000000..311c8a3bf6d
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/confirmtablesontarget.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:53ad803beceedf525c3a2050045935fd0b6c3f79213faf0638686494b6fb2ae1
+size 108765
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/connectcdc.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/connectcdc.png
new file mode 100644
index 00000000000..6c15e7486e2
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/connectcdc.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4723df1f375a1a1256739db46c3a7b1b7ad49d8171b76735107a71a7f4205151
+size 221704
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/copyrequest.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/copyrequest.png
new file mode 100644
index 00000000000..c5882bd9d2b
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/copyrequest.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bc40cfc3d9fe61406798f6ebf1da5070201fad1a2a42981d715f1cb87f2172c5
+size 486060
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/datatransformation1.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/datatransformation1.png
new file mode 100644
index 00000000000..afe7ed5e7b3
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/datatransformation1.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:35cd405b8215d160045deb5ba9d6e22694ab0abb27778f13d6e18288710c5c7f
+size 295027
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/datatransformation2.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/datatransformation2.png
new file mode 100644
index 00000000000..aee80b16608
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/datatransformation2.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e4c07d05626c54b99cbe8194b6309ec1b2793a8cdbb929d986b00648f2d64190
+size 23002
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/distributetables.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/distributetables.png
new file mode 100644
index 00000000000..ed85e65f256
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/distributetables.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e98cc7bfb8c8395fcf48e7014e8829a0e8cc63664c8236c8dc9f4e62f39eebaa
+size 423974
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/distributionmodel.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/distributionmodel.png
new file mode 100644
index 00000000000..222cd6aeff0
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/distributionmodel.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8855131923a3b92d3f5e5328f97b1dfa63f83613733f65d33790df70f97f8ede
+size 117871
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/distrmodel.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/distrmodel.png
new file mode 100644
index 00000000000..8987f5b7d1f
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/distrmodel.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9a717b288b9c3962cde94c6cc5eac38cd26f5a5f090e8661910bf92c3a6bf5d1
+size 112401
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/doneprepareuserdatabase.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/doneprepareuserdatabase.png
new file mode 100644
index 00000000000..d82bebce152
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/doneprepareuserdatabase.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1edfe6224f5881b9b8d9fbe415e4af8e1cb81e1a430ae29c6d1b23b3c074efa3
+size 154078
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/idpassword.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/idpassword.png
new file mode 100644
index 00000000000..eded44faaef
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/idpassword.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eca36c1b44203214b4af58cc2521d755150993e97faea4f01e4a3d1e21f52ab4
+size 167480
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/idpassword1.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/idpassword1.png
new file mode 100644
index 00000000000..e8eb88e6231
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/idpassword1.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a476d692a16eb27fe740f42000ac5e45d880a5ebd0b6b05e4674d3989ecb103f
+size 149009
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/installmetabase.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/installmetabase.png
new file mode 100644
index 00000000000..3c4772a5665
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/installmetabase.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:697a13d4ca020eefcbee340798b93cc5532498a5760379247e6ee37a21bf5aab
+size 151162
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/metabasesucces.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/metabasesucces.png
new file mode 100644
index 00000000000..fa105e9d328
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/metabasesucces.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:02bbd82c37b2cd92078e69a12cc8a6a775fac1ce3c9c0e794624e0f764d4e854
+size 209522
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/modelcommit.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/modelcommit.png
new file mode 100644
index 00000000000..dec70295128
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/modelcommit.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:43ce2b390bc540d06fd1951e2e2b2ec1839cfbfda97ca4435d3c36543a5b162c
+size 71404
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newdistribution.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newdistribution.png
new file mode 100644
index 00000000000..f049157ddb1
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newdistribution.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b0f8f06be1f3b54d5dc40e727baa81e0752679f206a19544ea9c3d3d3c823d80
+size 250121
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newhost.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newhost.png
new file mode 100644
index 00000000000..244fc54be26
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newhost.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a3cd641a3bb449f430bc8a833641255eb8a2348d140cfa0843e0d4f68eceaf98
+size 326706
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newmodel.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newmodel.png
new file mode 100644
index 00000000000..eea570c9870
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newmodel.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:45105c6405a07c5ac7db47ee581b3f69466749159af79b22c053fbd2a4a641d9
+size 26064
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newserver.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newserver.png
new file mode 100644
index 00000000000..7b9fc822cba
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newserver.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:202380596427834808a0e962d65014a3ffec4fdb07f90cea4e1f69273e46a353
+size 273513
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmin.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmin.png
new file mode 100644
index 00000000000..b3f7fe2a595
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmin.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4f9c1b4a8d055f2d07a19623f205237223f0afd64820f27081a19c7b81ca298e
+size 227956
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmincopydone.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmincopydone.png
new file mode 100644
index 00000000000..a8e29d38dd6
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmincopydone.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9b066ed53b91068f25135942b6cc4f82ef4719f905c65cd1f500a8cc1a750f81
+size 309209
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmincopydone2.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmincopydone2.png
new file mode 100644
index 00000000000..0b20c48bc76
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmincopydone2.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:69f1a71ee406d775142f79a5acea409271e8822c27e3442f9b8824168a2fbab4
+size 203771
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmintargettables.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmintargettables.png
new file mode 100644
index 00000000000..1e50d44b1ea
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmintargettables.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d709ae70a27fecd29908da1eb8cd5245561dc231a40d205ea5849eeddbf1c29e
+size 378740
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgadming.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgadming.png
new file mode 100644
index 00000000000..244ff865c6c
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgadming.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:84398eca6458d0526b163b9cc77f2157d4bb72de0067d0e9c5c822cce62b33b2
+size 815995
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/prepareuserdatabase.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/prepareuserdatabase.png
new file mode 100644
index 00000000000..37440f69834
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/prepareuserdatabase.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:64cca6a322e171597429d208bc731629ee3c64632ae995ee3dfb55d27ca98f7c
+size 133038
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/prepareuserdatabase2.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/prepareuserdatabase2.png
new file mode 100644
index 00000000000..93c996aa93c
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/prepareuserdatabase2.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d63b9e8df8c508ef32be3ff259910b87910925d469a46271d81646131dd21786
+size 169470
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/prepareuserdatabasesuccess.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/prepareuserdatabasesuccess.png
new file mode 100644
index 00000000000..e2bcb30aa05
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/prepareuserdatabasesuccess.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6bbe7b797c644470b55e77c372196a101b980f8fc6e5aacccd6f120b7710f69f
+size 143003
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/refreshtables.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/refreshtables.png
new file mode 100644
index 00000000000..c5301ff59b8
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/refreshtables.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:22bdab449adb17c612ebc70fedf4648a94d8f17f02bef7f33ccc3968aa85d589
+size 117829
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/replicationrequest.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/replicationrequest.png
new file mode 100644
index 00000000000..2c5123532d0
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/replicationrequest.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ae95f48725dd1816af7a7f4210b0bde05e67f255598ab6c18f05bdd056769834
+size 320931
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/replicationrequest2.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/replicationrequest2.png
new file mode 100644
index 00000000000..bfffe0a1b54
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/replicationrequest2.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bcc0a9e584c117121a609b284913fc24d05450f315506ec06a92cd54f2ec2b90
+size 103502
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/replicationrequest3.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/replicationrequest3.png
new file mode 100644
index 00000000000..a5dc100f879
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/replicationrequest3.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:11019ee1e6b55600f3a7e650ff6dd85f20ad39d5fdaa61652c6e881911f72697
+size 302984
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/rpuserpassword.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/rpuserpassword.png
new file mode 100644
index 00000000000..a38a1b3da4c
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/rpuserpassword.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:33677444e85173529aa84198c5ebd5c4cf62b57852e39a40ec4c4e82c62bd7ee
+size 165191
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/schema2.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/schema2.png
new file mode 100644
index 00000000000..16787e0971c
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/schema2.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8f82bcd57cbc9faec15a2112affe214520961f49ef2ead4417e08b7acf43d444
+size 161006
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/schematoreplicate.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/schematoreplicate.png
new file mode 100644
index 00000000000..3830b3f5466
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/schematoreplicate.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:03faa24ebf5ed5c5126932f4984e3965583fa3cb8215a8b36ba002b69cc713a0
+size 166108
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/selecttableforreplication.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/selecttableforreplication.png
new file mode 100644
index 00000000000..e80defa57ca
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/selecttableforreplication.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d754b326a4f82657674a6a6f85c635d3af6ca010b3f994f61a02055c7f919140
+size 78060
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/successserver.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/successserver.png
new file mode 100644
index 00000000000..46bd342c450
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/successserver.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:21f26f5e3b97b61d3c2b7a8ca888b550dbcd28d94f96564962f7fa45514449a3
+size 156896
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/tablemappings.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/tablemappings.png
new file mode 100644
index 00000000000..38373af9de7
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/tablemappings.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b334d85a9758fbe66e880d378dd628fd7e9281b71f55cf5c631506a53c61c06
+size 147751
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetmetabasecreated.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetmetabasecreated.png
new file mode 100644
index 00000000000..d5d5309d752
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetmetabasecreated.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f149074b969fe73725d2ffc050632f15a2e47ee98f99ad658930d45d7a097e15
+size 219070
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetpgadmin.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetpgadmin.png
new file mode 100644
index 00000000000..418960f570b
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetpgadmin.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1a778c2cc7e80f1bbfda32edf0e71a184be98a8722158de6a850e2e7b7f27286
+size 196041
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetserver.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetserver.png
new file mode 100644
index 00000000000..f4f7cefbf1c
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetserver.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fa4e4fed3af628d426d46c4c49d9b2510acfaf648a590ce0c17be55fd1618d86
+size 336615
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetserverlogin.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetserverlogin.png
new file mode 100644
index 00000000000..7eb80123fad
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetserverlogin.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ae03cfcbd63a2263e0a7bcc14e03e44f89ee8cf8e2bbce47516cd14e8c2c7dff
+size 201823
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetserveruserpass.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetserveruserpass.png
new file mode 100644
index 00000000000..963052e6d58
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetserveruserpass.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b779bda93404f12dccf6527886380c97d9fb941dda07a1c001f0fb2e2e41af91
+size 162190
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targettablescreen.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targettablescreen.png
new file mode 100644
index 00000000000..548b48bdc2c
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targettablescreen.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0d0e70f6b9b850d3a168dbfa7a0154299dcbb3671374ffc8c40478249378a2a8
+size 201077
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetuserpassword.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetuserpassword.png
new file mode 100644
index 00000000000..579ad52ed1e
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetuserpassword.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:88e9959514ccfe347dee28efd866c42835e54aed8ddea189d6d0800907eb74f1
+size 183019
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targtemetbase.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targtemetbase.png
new file mode 100644
index 00000000000..584ce684c97
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targtemetbase.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f8f708139bd3a21a11265a0aee36c4e7df1d547efc6c81fc16cea690543f7430
+size 146618
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/tstconnection.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/tstconnection.png
new file mode 100644
index 00000000000..560e1741614
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/tstconnection.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:def4fec442032a4f079ffaf9211248ed093002b06f314dbadbc22b6e9b48aa3e
+size 163218
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/userpassword.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/userpassword.png
new file mode 100644
index 00000000000..e85cbbf8073
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/userpassword.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd39e3b1d907383607983367ac44916709c2344f06e9e63eb10245590cf73329
+size 169547
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/validmodel.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/validmodel.png
new file mode 100644
index 00000000000..bf2fbe81d2a
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/validmodel.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8ed067a14422aecfdc1bd539bfbf7c2076c3538b363d59951e6d79ab697fcee8
+size 158841
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/index.mdx b/advocacy_docs/partner_docs/PreciselyConnectCDC/index.mdx
new file mode 100644
index 00000000000..b2f757e2f42
--- /dev/null
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/index.mdx
@@ -0,0 +1,14 @@
+---
+title: 'Precisely Connect CDC Implementation Guide'
+indexCards: simple
+directoryDefaults:
+ iconName: handshake
+---
+
+
+ 
+
+EDB GlobalConnect Technology Partner Implementation Guide
+Precisely Connect CDC
+
+This document is intended to augment each vendor’s product documentation in order to guide the reader in getting the products working together. It is not intended to show the optimal configuration for the certified integration.
diff --git a/src/pages/index.js b/src/pages/index.js
index d40544d0e55..95144fe6c97 100644
--- a/src/pages/index.js
+++ b/src/pages/index.js
@@ -174,7 +174,7 @@ const Page = () => (
PG Failover Slots
-
+
Language Pack
@@ -185,7 +185,7 @@ const Page = () => (
to="/biganimal/latest/free_trial/"
className="nested-link"
>
- Quick Start
+ Free Trial
(
- Security
+ Data Movement
-
- Hashicorp Vault
-
-
- Hashicorp Vault Transit Secrets Engine
-
-
- Imperva Data Security Fabric
-
-
- Thales CipherTrust Manager
-
-
- Thales CipherTrust Transparent Encryption
+
+ Precisely Connect CDC
+
Other
From 34df1b20bfbc0e76479393ede47065be0297c276 Mon Sep 17 00:00:00 2001
From: Kashif Zeeshan
Date: Wed, 12 Jul 2023 11:57:35 +0500
Subject: [PATCH 14/19] Changes as per Review.
Changes as per Review.
---
.../PreciselyConnectCDC/05-Usingpreciselyconnectcdc.mdx | 4 ----
.../PreciselyConnectCDC/Images/distributetables.png | 4 ++--
.../PreciselyConnectCDC/Images/distributionmodel.png | 4 ++--
.../PreciselyConnectCDC/Images/newdistribution.png | 4 ++--
.../partner_docs/PreciselyConnectCDC/Images/newhost.png | 4 ++--
.../partner_docs/PreciselyConnectCDC/Images/newserver.png | 4 ++--
.../partner_docs/PreciselyConnectCDC/Images/pgAdmin.png | 4 ++--
.../PreciselyConnectCDC/Images/pgAdmintargettables.png | 4 ++--
.../partner_docs/PreciselyConnectCDC/Images/tablemappings.png | 4 ++--
.../partner_docs/PreciselyConnectCDC/Images/targetserver.png | 4 ++--
10 files changed, 18 insertions(+), 22 deletions(-)
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/05-Usingpreciselyconnectcdc.mdx b/advocacy_docs/partner_docs/PreciselyConnectCDC/05-Usingpreciselyconnectcdc.mdx
index f82cde1d236..8c43357aa5c 100644
--- a/advocacy_docs/partner_docs/PreciselyConnectCDC/05-Usingpreciselyconnectcdc.mdx
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/05-Usingpreciselyconnectcdc.mdx
@@ -209,8 +209,6 @@ Connect CDC MonCon is a GUI application, separate from the Connect CDC Director,
5. Click on `Process` to see the progress.
-
-
6. Open pgAdmin once the copy operation is completed successfully and connect the EDB Postgres Advanced Server Target Instance and check the tables and the data is copied to the tables.
@@ -249,8 +247,6 @@ Replication distribution will replicate all the changes done on the Source Table
3. The replication request will be displayed once the `Model` is updated successfully.
-
-
4. In the `Request` Section, select the `Distribution Model` created for Replication and right click and select `Start`.
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/distributetables.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/distributetables.png
index ed85e65f256..7108eb1526b 100644
--- a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/distributetables.png
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/distributetables.png
@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
-oid sha256:e98cc7bfb8c8395fcf48e7014e8829a0e8cc63664c8236c8dc9f4e62f39eebaa
-size 423974
+oid sha256:e4ae5a0cbf3c2039a66d953cb8cc209f7f29756ee2626345524966ab9c8b11fe
+size 409132
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/distributionmodel.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/distributionmodel.png
index 222cd6aeff0..2bc1fb2fd27 100644
--- a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/distributionmodel.png
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/distributionmodel.png
@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
-oid sha256:8855131923a3b92d3f5e5328f97b1dfa63f83613733f65d33790df70f97f8ede
-size 117871
+oid sha256:96c5ae76ec0baf709c39e1bd816d67ee98daae6c30e04a8c363e5cee68d7585d
+size 105364
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newdistribution.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newdistribution.png
index f049157ddb1..e3695957585 100644
--- a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newdistribution.png
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newdistribution.png
@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
-oid sha256:b0f8f06be1f3b54d5dc40e727baa81e0752679f206a19544ea9c3d3d3c823d80
-size 250121
+oid sha256:72c7a6108df685e3ddeff499d508d3998b98e3094956db39dd18b7213a6748b7
+size 246630
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newhost.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newhost.png
index 244fc54be26..e44e49fdbde 100644
--- a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newhost.png
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newhost.png
@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
-oid sha256:a3cd641a3bb449f430bc8a833641255eb8a2348d140cfa0843e0d4f68eceaf98
-size 326706
+oid sha256:b03a566d838bf21e0cf7a5886f67ce5c66598ddadfbec2c5b0c7eb80a56fb0a1
+size 299544
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newserver.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newserver.png
index 7b9fc822cba..5d0f5d8961f 100644
--- a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newserver.png
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/newserver.png
@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
-oid sha256:202380596427834808a0e962d65014a3ffec4fdb07f90cea4e1f69273e46a353
-size 273513
+oid sha256:8228cfa911a16032ab80425ccd51bc73d7296f395b8fd04a4d538c8ea00df1f8
+size 270427
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmin.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmin.png
index b3f7fe2a595..c81d2215452 100644
--- a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmin.png
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmin.png
@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
-oid sha256:4f9c1b4a8d055f2d07a19623f205237223f0afd64820f27081a19c7b81ca298e
-size 227956
+oid sha256:bc5679e0b72eecb7797fbc5dba0c3f4243222cc4a9cd15156942208b709b1569
+size 424178
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmintargettables.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmintargettables.png
index 1e50d44b1ea..519535e79fe 100644
--- a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmintargettables.png
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/pgAdmintargettables.png
@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
-oid sha256:d709ae70a27fecd29908da1eb8cd5245561dc231a40d205ea5849eeddbf1c29e
-size 378740
+oid sha256:69cfd330932801c3ac6e213dc8b011b55d95674ed266f68966a77235313b2af1
+size 833657
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/tablemappings.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/tablemappings.png
index 38373af9de7..ce2db60f436 100644
--- a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/tablemappings.png
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/tablemappings.png
@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
-oid sha256:8b334d85a9758fbe66e880d378dd628fd7e9281b71f55cf5c631506a53c61c06
-size 147751
+oid sha256:e4f54674ed3a82428063c4fb5bb6d7cfd027a3bfdb80b952f0d264f8ec0fd50c
+size 142239
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetserver.png b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetserver.png
index f4f7cefbf1c..4424aaa74d8 100644
--- a/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetserver.png
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/Images/targetserver.png
@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
-oid sha256:fa4e4fed3af628d426d46c4c49d9b2510acfaf648a590ce0c17be55fd1618d86
-size 336615
+oid sha256:6b071a6baae40bd2da09d8914ea22dff2c22fb00bbe6650b8f24a12241cfb548
+size 314099
From 6e5f23596f509ffbd5e9efebd7085d6a9da1317e Mon Sep 17 00:00:00 2001
From: jkitchens32 <106532490+jkitchens32@users.noreply.github.com>
Date: Thu, 13 Jul 2023 11:28:12 -0400
Subject: [PATCH 15/19] Scott final updates
---
.../PreciselyConnectCDC/05-Usingpreciselyconnectcdc.mdx | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/advocacy_docs/partner_docs/PreciselyConnectCDC/05-Usingpreciselyconnectcdc.mdx b/advocacy_docs/partner_docs/PreciselyConnectCDC/05-Usingpreciselyconnectcdc.mdx
index 8c43357aa5c..759f1aaf89b 100644
--- a/advocacy_docs/partner_docs/PreciselyConnectCDC/05-Usingpreciselyconnectcdc.mdx
+++ b/advocacy_docs/partner_docs/PreciselyConnectCDC/05-Usingpreciselyconnectcdc.mdx
@@ -7,8 +7,8 @@ After you have configured your EDB Postgres Distribution, as stated in the Confi
- Configure Postgres Distribution as a Source Instance in Connect CDC Director
- Setup and configuration of EDB Postgres Advanced Server as a source instance for Connect CDC Director.
-- Configure Postgres Distribution as Target Instance in Connect CDC Director
- - Setup and configuration of EDB Postgres Advanced Server as target instance to Connect CDC Director.
+- Configure Postgres Distribution as a Target Instance in Connect CDC Director
+ - Setup and configuration of EDB Postgres Advanced Server as a target instance to Connect CDC Director.
- Create Distribution on Connect CDC Director
- Define how data will be replicated from source to target in a Model.
- Save the Model
@@ -87,9 +87,9 @@ The following steps demonstrate the setup and configuration of EDB Postgres Adva
-## Configure Postgres Distribution as Target Instance in Connect CDC Director
+## Configure Postgres Distribution as a Target Instance in Connect CDC Director
-The following steps demonstrate the setup and configuration of EDB Postgres Advanced Server as target instance to Connect CDC Director.
+The following steps demonstrate the setup and configuration of EDB Postgres Advanced Server as a target instance to Connect CDC Director.
1. Right click `DBMS Servers` and `New Server`.
From 7e7e53d89b9325312356f0c050538d5f53833588 Mon Sep 17 00:00:00 2001
From: drothery-edb
Date: Thu, 13 Jul 2023 13:05:45 -0400
Subject: [PATCH 16/19] fixed stray erroneous updates to docs home page
---
src/pages/index.js | 11 ++++-------
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/src/pages/index.js b/src/pages/index.js
index 95144fe6c97..af55ae6df99 100644
--- a/src/pages/index.js
+++ b/src/pages/index.js
@@ -174,7 +174,7 @@ const Page = () => (
PG Failover Slots
-
+
Language Pack
@@ -185,7 +185,7 @@ const Page = () => (
to="/biganimal/latest/free_trial/"
className="nested-link"
>
- Free Trial
+ Quick Start
(
Data Movement
-
+
Precisely Connect CDC
-
Other
@@ -370,9 +369,7 @@ const Page = () => (
Esri ArcGIS Pro and Esri ArcGIS Enterprise
-
- HPE
-
+ HPE
Nutanix AHV
From 64e636af10e631bac5b1850deb5f41f6a7ef8342 Mon Sep 17 00:00:00 2001
From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com>
Date: Thu, 13 Jul 2023 13:07:19 -0400
Subject: [PATCH 17/19] added missing word
and did a little bit of other cleanup
---
.../efm/4/04_configuring_efm/05_using_vip_addresses.mdx | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/product_docs/docs/efm/4/04_configuring_efm/05_using_vip_addresses.mdx b/product_docs/docs/efm/4/04_configuring_efm/05_using_vip_addresses.mdx
index e0beeb9e914..abd20bc8902 100644
--- a/product_docs/docs/efm/4/04_configuring_efm/05_using_vip_addresses.mdx
+++ b/product_docs/docs/efm/4/04_configuring_efm/05_using_vip_addresses.mdx
@@ -84,9 +84,9 @@ When instructed to ping the VIP from a node, use the command defined by the `pin
You see 100% packet loss.
!!!important
- Failover Manager uses the exit code of the ping command to determine whether or not the address was reachable. In this case the exit code isn't zero. If using a command other than, it must return a non-zero exit code if the address isn't reachable.
+ Failover Manager uses the exit code of the ping command to determine whether the address was reachable. In this case, the exit code isn't zero. If you're using a command other than ping, it must return a non-zero exit code if the address isn't reachable.
-2. Run the `efm_address add4` command on the Primary node to assign the VIP, and then confirm with ip address:
+2. Run the `efm_address add4` command on the primary node to assign the VIP, and then confirm with ip address:
```text
# efm_address add4 eth0 172.24.38.239/24
@@ -109,7 +109,7 @@ When instructed to ping the VIP from a node, use the command defined by the `pin
No packet loss occurs.
!!!Important
- Failover Manager uses the exit code of the ping command to determine whether or not the address was reachable. In this case the exit code is zero. If using a command other than ping, it must return a zero exit code if the address is reachable.
+ Failover Manager uses the exit code of the ping command to determine whether the address was reachable. In this case, the exit code is zero. If you're using a command other than ping, it must return a zero exit code if the address is reachable.
4. Use the `efm_address del` command to release the address on the primary node and confirm the node was released with ip address:
@@ -146,7 +146,7 @@ When instructed to ping the VIP from a node, use the command defined by the `pin
...
```
-After the test steps above, release the VIP from any nonprimary node before attempting to start Failover Manager.
+After these test steps, release the VIP from any nonprimary node before attempting to start Failover Manager.
!!! Note
The network interface used for the VIP doesn't have to be the same interface used for the Failover Manager agent's `bind.address` value. The primary agent drops the VIP as needed during a failover, and Failover Manager verifies that the VIP is no longer available before promoting a standby. A failure of the bind address network leads to primary isolation and failover.
From 734ff42a0432664f13bca72591f0511c7a10fa1d Mon Sep 17 00:00:00 2001
From: jkitchens32 <106532490+jkitchens32@users.noreply.github.com>
Date: Thu, 13 Jul 2023 13:51:51 -0400
Subject: [PATCH 18/19] Update key_stores.mdx
Trying to add clarification around the Hashicorp pieces in the TDE Docs.
---
product_docs/docs/tde/15/key_stores.mdx | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/product_docs/docs/tde/15/key_stores.mdx b/product_docs/docs/tde/15/key_stores.mdx
index b05a485a0e0..12be55f08e7 100644
--- a/product_docs/docs/tde/15/key_stores.mdx
+++ b/product_docs/docs/tde/15/key_stores.mdx
@@ -62,7 +62,7 @@ You can use the key store in an external key management system to manage the dat
- Amazon AWS Key Management Service (KMS)
- Google Cloud - Cloud Key Management Service
-- HashiCorp Vault
+- HashiCorp Vault (KMIP Secrets Engine and Transit Secrets Engine)
- Microsoft Azure Key Vault
- Thales CipherTrust Manager
@@ -132,7 +132,7 @@ PGDATAKEYWRAPCMD='crypt encrypt gcp --out=%p --location=global --keyring=pg-tde
PGDATAKEYUNWRAPCMD='crypt decrypt gcp --in=%p --location=global --keyring=pg-tde --key=pg-tde-master-1 --project your-project-123456'
```
-### HashiCorp Vault example
+### HashiCorp Vault Transit Secrets Engine example
```shell
# enable once
From 342733e086d8f79ba83b55cb0a25c7736d520091 Mon Sep 17 00:00:00 2001
From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com>
Date: Thu, 13 Jul 2023 14:20:04 -0400
Subject: [PATCH 19/19] Update
product_docs/docs/net_connector/7.0.4.1/12_using_advanced_queueing.mdx
---
.../docs/net_connector/7.0.4.1/12_using_advanced_queueing.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/product_docs/docs/net_connector/7.0.4.1/12_using_advanced_queueing.mdx b/product_docs/docs/net_connector/7.0.4.1/12_using_advanced_queueing.mdx
index e454478d310..80029584880 100644
--- a/product_docs/docs/net_connector/7.0.4.1/12_using_advanced_queueing.mdx
+++ b/product_docs/docs/net_connector/7.0.4.1/12_using_advanced_queueing.mdx
@@ -7,7 +7,7 @@ title: "Using advanced queueing"
EDB Postgres Advanced Server advanced queueing provides message queueing and message processing for the EDB Postgres Advanced Server database. User-defined messages are stored in a queue. A collection of queues is stored in a queue table. Create a queue table before creating a queue that depends on it.
-On the server side, procedures in the `DBMS_AQADM` package create and manage message queues and queue tables. Use the `DBMS_AQ` package to add messages to or remove messages from a queue or register or unregister a PL/SQL callback procedure. For more information about `DBMS_AQ` and `DBMS_AQADM`, see [DBMS_AQ](../..//epas/latest/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/).
+On the server side, procedures in the `DBMS_AQADM` package create and manage message queues and queue tables. Use the `DBMS_AQ` package to add messages to or remove messages from a queue or register or unregister a PL/SQL callback procedure. For more information about `DBMS_AQ` and `DBMS_AQADM`, see [DBMS_AQ](/epas/latest/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/).
On the client side, the application uses the EDB.NET driver to enqueue and dequeue messages.