Skip to Main Content
AVEVA™ Products Feedback Portal

Welcome to our new feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, select the product of your interest in the left column. Then take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas will first be moderated before they are made visible to other users of this portal.

This page is for feedback for specific AVEVA solutions, excluding PI Systems and Data Hub. For links to these other feedback portals, please see the tab RESOURCES below.

Portfolio area Enterprise SCADA Server
Products Datapump
Created by Angel Mario Moreno Arcos
Created on Mar 12, 2024

Datapump: Include Port number as an argument to DPDirect process command line

Datapump main process is DPDirect. Two of the arguments are source and destination SQL Services to pump data from one SQL to the other. The most common syntax uses to be like:

DPdirect -i 40 -S :MS:<SrcHistorical>\OASYSHDB -D <system>:MS:<DstHistorical>\OASYSHDB -Z DPdirect_<DBName>_<system>.log -C DPGroup = '<groupName>'

The connection initially goes to 1433 port on destination to resolve the current port in which the instance is listening, usually 20010, and then the connection is established.
For cyber security reasons, standard SQL port 1433 uses to be closed on most of the systems so, in order to make it work, the destination port 20010 must be specified in some way.
Other related applications, like DPutil allows including the port number in the command line, as an example:

dputil -K -S <HistoricalSrv>,20010\OASYSHDB

But using DPDirect, this syntax is not accepted.
Is there any special way to specify the port number or simply is not accepted?
The way to solve this issue has been creating aliases for the source and the destination server instances, following MS directions:
https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/create-or-delete-a-server-alias-for-use-by-a-client?view=sql-server-ver16

But it would be great if this port argument is included on DPDirect in same way as the other DPump related applications.
Thank you so much in advance

User Persona SCADA Administrator, IT/Network Administrator, Developer / Integrator
  • Attach files