Skip to main content
To homepage To homepage
Solved

Keep Business Unit Data but Remove Data Source

  • April 2, 2026
  • 5 replies
  • 39 views
J
Visitor

In 20.10, is there a way to remove a data source but keep the tables with the data that were created from it? I’m trying to eliminate my last CData data source that pulled legacy data in from an old MS Access database. I tried to remove the data source, but in doing so, it attempts to delete the loaded tables in the Business Unit. I still need to be able to use and reference the legacy data that was loaded but I no longer have access to the legacy MS Access database to re-load it with a non-CData connector.

Best answer by rory.smith

Hi,

as far as I am aware deleting the source will always delete the tables selected, even if you explicitly Guard BU tables for Deploy and Execution, even if they are History tables. You will need to take all tables you want to keep into a Datawarehouse layer, and Guard them for Deploy and Execute.

In the past, you would never need to remove the source but Guard the it for Deploy and Execute to keep the data. I guess it would be great if:

  • removing a source does not automatically remove tables but allows you to guard the tables that would otherwise be deleted. Resulting in a “source” without a provider
  • it is possible to “deactivate” CData sources but allow you to keep the source in the BU so you avoid this issue

5 replies

rory.smith
TimeXtender Xpert
Forum|alt.badge.img+8
  • rory.smith
  • TimeXtender Xpert
  • Answer
  • April 3, 2026

Hi,

as far as I am aware deleting the source will always delete the tables selected, even if you explicitly Guard BU tables for Deploy and Execution, even if they are History tables. You will need to take all tables you want to keep into a Datawarehouse layer, and Guard them for Deploy and Execute.

In the past, you would never need to remove the source but Guard the it for Deploy and Execute to keep the data. I guess it would be great if:

  • removing a source does not automatically remove tables but allows you to guard the tables that would otherwise be deleted. Resulting in a “source” without a provider
  • it is possible to “deactivate” CData sources but allow you to keep the source in the BU so you avoid this issue
R
Problem Solver
  • RLB
  • Problem Solver
  • April 3, 2026

Also, removing a source does not warn you if the associated table(s) is/are used in table mappings in a DWH layer.

And it would be nice if you could change the provider to a different type instead of having to create new datasources.

Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Thomas Lind
  • Community Manager
  • April 7, 2026

Hi ​@jbena 

There is no way to delete a data source without loosing the tables. Ideally you have data in another area such as the DWH. This is what should be guarded, then it wouldn’t affect anything to delete the data source.

The only way to avoid this, is to change the data source to something not CData, set it to guard on delete and execute and save. Don’t synchronize that should remove the tables despite the guard.

R
Problem Solver
  • RLB
  • Problem Solver
  • April 7, 2026

The only way to avoid this, is to change the data source to something not CData, set it to guard on delete and execute and save.

In thought that was not possible though?

Thomas Hjermitslev
Community Manager

Hi ​@RLB, it should be possible as follows: 

  • Right click the data source, click Change Provider, and choose another provider, e.g. SQL Server or Excel. It doesn't really matter which one since you won’t really be using it. Enter some dummy information in the required fields and click OK.
  • When asked if you want to synchronize, click No.
  • Right click the data source, click Data Source Settings and enable Guard on Deployment and Guard on Execution (prevents the data source from being deployed or executed, i.e. leaving the data as-is).

Hope this helps.

    Terms and ConditionsAccessibility statement