# \[BUG-5606\] Unable to delete unused Datasource History Provider

**URL:** <https://forum.inductiveautomation.com/t/bug-5606-unable-to-delete-unused-datasource-history-provider/38966>\
**Category:** Ignition Early Access\
**Created:** [September 23, 2020, 5:00am UTC](https://forum.inductiveautomation.com/t/bug-5606-unable-to-delete-unused-datasource-history-provider/38966 "2020-09-23T05:00:47Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![nader.chinichian](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nader.chinichian/32/9261_2.png) [@nader.chinichian](https://forum.inductiveautomation.com/u/nader.chinichian)\
**Post date:** [September 23, 2020, 5:00am UTC](https://forum.inductiveautomation.com/t/bug-5606-unable-to-delete-unused-datasource-history-provider/38966/1 "2020-09-23T05:00:47Z")

</div>

Hi  
As it shown in below I setup and called my Database connection to ‘DB’ but before that I had another database connection call ‘MySQL’ and even though I delete that connection I still have it in my history provider list and I can’t delete it.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/c/0c816e95ea4d1d4cf9916770ac22e908952fcc41.png)

---

<div class="post-metadata">

**Author:** ![johannes.bo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/johannes.bo/32/27628_2.png) [@johannes.bo](https://forum.inductiveautomation.com/u/johannes.bo)\
**Post date:** [March 9, 2022, 8:06pm UTC](https://forum.inductiveautomation.com/t/bug-5606-unable-to-delete-unused-datasource-history-provider/38966/2 "2022-03-09T20:06:03Z")

</div>

Did you find any solution?

---

<div class="post-metadata">

**Author:** ![avaughn](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/avaughn/32/38972_2.png) [@avaughn](https://forum.inductiveautomation.com/u/avaughn)\
**Post date:** [March 9, 2022, 9:35pm UTC](https://forum.inductiveautomation.com/t/bug-5606-unable-to-delete-unused-datasource-history-provider/38966/3 "2022-03-09T21:35:02Z")

</div>

This is a bug that we’re aware of. This happens if the database connection is disabled before deleting it. The easiest workaround is to re-create a database connection with the same name as the original connection and then delete it.

---

<div class="post-metadata">

**Author:** ![nader.chinichian](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nader.chinichian/32/9261_2.png) [@nader.chinichian](https://forum.inductiveautomation.com/u/nader.chinichian)\
**Post date:** [March 10, 2022, 4:30am UTC](https://forum.inductiveautomation.com/t/bug-5606-unable-to-delete-unused-datasource-history-provider/38966/4 "2022-03-10T04:30:45Z")

</div>

For OPC UA/DA connection in system tag provider, there are also leftover of deleted OPC Connection.

---

<div class="post-metadata">

**Author:** ![johannes.bo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/johannes.bo/32/27628_2.png) [@johannes.bo](https://forum.inductiveautomation.com/u/johannes.bo)\
**Post date:** [March 10, 2022, 7:05am UTC](https://forum.inductiveautomation.com/t/bug-5606-unable-to-delete-unused-datasource-history-provider/38966/5 "2022-03-10T07:05:38Z")

</div>

I have tried that, but in my case it results in an additional tag history instance ;-). -Which in turn is removed when I remove the database connection, but not removing the “problem”-instance (even when having the same name)  
-Will this give me any issues, leaving an orphan history provider in my application?  
-Are there any other way of cleaning up?

---

<div class="post-metadata">

**Author:** ![avaughn](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/avaughn/32/38972_2.png) [@avaughn](https://forum.inductiveautomation.com/u/avaughn)\
**Post date:** [March 10, 2022, 2:19pm UTC](https://forum.inductiveautomation.com/t/bug-5606-unable-to-delete-unused-datasource-history-provider/38966/6 "2022-03-10T14:19:30Z")

</div>

Looks like we have another ticket already for this as well.

---

<div class="post-metadata">

**Author:** ![avaughn](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/avaughn/32/38972_2.png) [@avaughn](https://forum.inductiveautomation.com/u/avaughn)\
**Post date:** [March 10, 2022, 2:21pm UTC](https://forum.inductiveautomation.com/t/bug-5606-unable-to-delete-unused-datasource-history-provider/38966/7 "2022-03-10T14:21:11Z")

</div>

No, this shouldn’t cause any issues. The other option is to remove the provider directly from the internal database. For this, we do recommend reaching out to Support to take care of.

---

<div class="post-metadata">

**Author:** ![SBL\_MC](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sbl_mc/32/56813_2.png) [@SBL\_MC](https://forum.inductiveautomation.com/u/SBL_MC)\
**Post date:** [May 6, 2022, 8:42am UTC](https://forum.inductiveautomation.com/t/bug-5606-unable-to-delete-unused-datasource-history-provider/38966/8 "2022-05-06T08:42:22Z")

</div>

Hi all,

We cannot delete any “Datasource History provider” (from now on DHP), even with valid SQL connections.

Adding a DHP is no longer an option? Adding a DB Table historian (DTH) twice, makes the first one convert into a DHP. If I then delete the second DTH the first DHP is disabled. I have to disable it in the edit-view and enable it again.

I’m confused. 😂 8.1.15

---

<div class="post-metadata">

**Author:** ![avaughn](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/avaughn/32/38972_2.png) [@avaughn](https://forum.inductiveautomation.com/u/avaughn)\
**Post date:** [May 10, 2022, 5:41pm UTC](https://forum.inductiveautomation.com/t/bug-5606-unable-to-delete-unused-datasource-history-provider/38966/9 "2022-05-10T17:41:43Z")

</div>

@SBL_MC I didn’t see any of this behavior during my testing, so I’m not sure if you’re running into the same bug or may be running into something different. I would suggest getting in contact with support to take a deeper dive into what’s going on here.

[https://support.inductiveautomation.com/hc/en-us](https://support.inductiveautomation.com/hc/en-us)

---

<div class="post-metadata">

**Author:** ![avaughn](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/avaughn/32/38972_2.png) [@avaughn](https://forum.inductiveautomation.com/u/avaughn)\
**Post date:** [May 10, 2022, 5:45pm UTC](https://forum.inductiveautomation.com/t/bug-5606-unable-to-delete-unused-datasource-history-provider/38966/10 "2022-05-10T17:45:03Z")

</div>

Also, I looked into the bug ticket and it looks like it should be fixed in 8.1.17. This is from the 8.1.17 rc1 release notes.

```auto
Deleting a disabled database connection will now also delete the associated historical provider.

```
