You are viewing limited content. For full access, please sign in.

Question

Question

Workflow SQL database migration

asked on July 3, 2019

Hello,

 

When a database that forms uses to lookup changes locations to resolve the lookup changes we simply have to change the data source in forms Administration. We have a scenario where a client has 100s of workflows and they want to move to a new SQL server. Changing the SQL server connection to the workflow database itself is simple using the configuration manager. My concern is that we will have to update each external table and each workflow with a task that touches the database. Is there a way around manually doing this?

 

Thanks,

0 0

Answer

SELECTED ANSWER
replied on July 15, 2019

Yes, the connection is in the data source, not in the query.

0 0

Replies

replied on July 4, 2019

Hi Drew,

Is your main concern that you have a large number of data sources to update? Or a large number of workflows all pointing to the same few data sources? 

We recently migrated our databases and had about 50 workflows actively using a connection to SQL.

We used the Workflow Administration Console, under "External Objects" you'll find "Data Sources". If you don't have too many you could just update the data source here to point to the new database. You can also check which Workflows are using a data source from this page. I don't believe you have to update each individual Workflow after making changes here.

Thanks,

Dom

0 0
replied on July 9, 2019

Hey Dominic,

 

My experience has been when we change the external source, we still have to go to each workflow and change these connections. The goal is to streamline the Workflow migration process as much as possible.

 

Regards,

0 0
replied on July 9, 2019

Workflow uses data sources just like Forms. Changing the connection in the data source definition (from the Workflow Admin Console) should be sufficient.

0 0
replied on July 15, 2019

Thanks Miruna,

 

I will let the client know. If this does not work as expected I will open a case with LF support.

0 0
replied on July 15, 2019

Sorry I have a follow up question. Does that include custom queries?

0 0
SELECTED ANSWER
replied on July 15, 2019

Yes, the connection is in the data source, not in the query.

0 0
replied on August 22, 2019

We recently went through this with a client. We updated the Data Source in the Workflow Administration Console. The next day they reported multiple issues. We looked into the instances and the instances were still trying to do lookups using the old server information for the data source. I had to go into each workflow and refresh the connection in order for it to take affect.

1 0
replied on November 19, 2019

If a scenario like this happens should we open a case?

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.