Skip to main content
N
NK_134718471-Visitor
1-Visitor
May 12, 2025
Solved

Licensing Recommendations for Windchill on Windows Server 2022

  • May 12, 2025
  • 1 reply
  • 1094 views

Hello everyone,


We are planning a Windchill deployment on an HPE DL320 Gen11 with Windows Server 2022 Standard. We’ll have about 15 users and no Active Directory—this server is dedicated solely to Windchill.

Could you recommend:
1. Windows Server licensing:
• Core‐based packs vs. CALs—what’s the minimum we need for 15 users?
2. SQL Server Standard edition & licensing model:
• Which SQL Server Standard version is best (2019, 2022, etc.) for Windchill?
• Core‐based licensing vs. Server + CALs—what would you choose at this scale?

Any insights or links to PTC/Microsoft licensing guides would be much appreciated. Thank you!

Best answer by mmeadows-3

You really need to talk to a Microsoft software provider.  Database licensing requirements are convoluted and periodically change as technology changes: physical, virtual, cloud, etc..  So, talk to your Microsoft vendor about what SQL Server licensing you can use and is more cost effective with your hardware, user count, and intended usage.

 

For example:

As a "Development" system, you might be able to get by with Developer Edition if you meet Microsoft's criteria.  The key requirement is that it does not include any production data.  So, no cloning of production unless production is just a business configuration.  There may be other limitations depending on the use case.

 

You might be able to build an empty Dev system with business configuration using either:

 

If it is SQL Server Standard Edition, you can figure out if core or Server + CAL licensing is more cost effective for from the Internet.  But still talk to your Microsoft representative to ensure your hardware, user count, and use case are covered.

 

Note: There is a known performance issue running Windchill 13.0 with SQL Server 2022.
https://www.ptc.com/en/support/article/CS425173

The article reads like it can't be fixed for Windchill 13.0, but is fixed for Windchill 13.1.  So, if this is a 13.0 environment, you might want to use SQL Server 2019.

1 reply

J
Jimwang16-Pearl
16-Pearl
May 13, 2025

1. For Windchill license, you can refer to article https://www.ptc.com/en/support/article/CS277240.

2.. For Windows Server and SQL Server licensing, you have to check the vendor or Microsoft Support

N
NK_134718471-VisitorAuthor
1-Visitor
May 14, 2025

Thanks for your reply! I actually came across that article earlier and was hoping to get a bit more specific guidance here, especially around the SQL licensing side. But I appreciate you taking the time to respond — thank you!

M
mmeadows-316-PearlAnswer
16-Pearl
May 14, 2025

You really need to talk to a Microsoft software provider.  Database licensing requirements are convoluted and periodically change as technology changes: physical, virtual, cloud, etc..  So, talk to your Microsoft vendor about what SQL Server licensing you can use and is more cost effective with your hardware, user count, and intended usage.

 

For example:

As a "Development" system, you might be able to get by with Developer Edition if you meet Microsoft's criteria.  The key requirement is that it does not include any production data.  So, no cloning of production unless production is just a business configuration.  There may be other limitations depending on the use case.

 

You might be able to build an empty Dev system with business configuration using either:

 

If it is SQL Server Standard Edition, you can figure out if core or Server + CAL licensing is more cost effective for from the Internet.  But still talk to your Microsoft representative to ensure your hardware, user count, and use case are covered.

 

Note: There is a known performance issue running Windchill 13.0 with SQL Server 2022.
https://www.ptc.com/en/support/article/CS425173

The article reads like it can't be fixed for Windchill 13.0, but is fixed for Windchill 13.1.  So, if this is a 13.0 environment, you might want to use SQL Server 2019.

    Terms & ConditionsCookie settingsAccessibility statement