# Which MS SQL License to be used +CAL OR CORE Based

**URL:** <https://forum.inductiveautomation.com/t/which-ms-sql-license-to-be-used-cal-or-core-based/36123>\
**Category:** Ignition\
**Created:** [June 28, 2020, 7:58am UTC](https://forum.inductiveautomation.com/t/which-ms-sql-license-to-be-used-cal-or-core-based/36123 "2020-06-28T07:58:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rajendrashukla1001](https://avatars.discourse-cdn.com/v4/letter/r/73ab20/32.png) [@rajendrashukla1001](https://forum.inductiveautomation.com/u/rajendrashukla1001)\
**Post date:** [June 28, 2020, 7:58am UTC](https://forum.inductiveautomation.com/t/which-ms-sql-license-to-be-used-cal-or-core-based/36123/1 "2020-06-28T07:58:45Z")

</div>

We have two ignition redundant setup using 30 K OPC TAGs on each system. Both System utilizes common SQL Database to log the data.

Question is which is the preferred type of SQL Setup and license.

Standard SQL vs Enterprise Edition .  
+CAL OR CORE Based licenses.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [June 28, 2020, 5:55pm UTC](https://forum.inductiveautomation.com/t/which-ms-sql-license-to-be-used-cal-or-core-based/36123/2 "2020-06-28T17:55:24Z")

</div>

> [@rajendrashukla1001](#):
>
> Question is which is the preferred type of SQL Setup

I recommend PostgreSQL. As a bonus, you get perfect timezone-aware data handling in JDBC. Not available in MS SQL.

> [@rajendrashukla1001](#):
>
> and license.

None required.

At this point I would normally put "[/snark]" to acknowledge that I really didn't answer the question you asked, but in this case I'm answering the question(s) you _ **will** _ ask after you go down the MS SQL road.....

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [June 29, 2020, 11:56am UTC](https://forum.inductiveautomation.com/t/which-ms-sql-license-to-be-used-cal-or-core-based/36123/3 "2020-06-29T11:56:10Z")

</div>

As with most things, the answer is ‘it depends’.

Unless you’re going with high availability setup, go with Standard.  
Unless you have a limited number of users or devices, or need external access, (outside the network), go with CORE.

That said, I second the PostgreSQL recommendation, for the same reasons.

---

<div class="post-metadata">

**Author:** ![Sanderd17](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sanderd17/32/8735_2.png) [@Sanderd17](https://forum.inductiveautomation.com/u/Sanderd17)\
**Post date:** [June 29, 2020, 12:13pm UTC](https://forum.inductiveautomation.com/t/which-ms-sql-license-to-be-used-cal-or-core-based/36123/4 "2020-06-29T12:13:05Z")

</div>

We normally use MS SQL due to client requests. This also means our client generally already has a database installed that we should connect to.

That said, it’s more important to configure your tags and historian correctly instead of getting a more expensive license. When you consider your deadbands and polling times during development, you can store a lot of useful data before it becomes too hard for the database.