Installing a Database Server as a Separate Instance or into a Shared Instance with Multiple Databases

Installation and Upgrade > Installation and Configuration Guide > Database Installation > Installing a Database Server as a Separate Instance or into a Shared Instance with Multiple Databases

Windchill customers often have other relational databases for other business systems. For administration and cost purposes, you can consider installing the database for Windchill on the same physical server as other relational databases (either as a different instance, or another database schema in an existing instance). The following table provides the PTC recommendations on several common database installation options using one physical server with Windchill.

Database Installation Options on One Physical Server	PTC Recommended?	Pros	Cons
1. One Database Instance	Recommended for production Windchill database	Better performance and reliability through lack of contention with other business systems or applications for system resources	• Requires additional hardware • Requires additional database licenses
2. Multiple Windchill Database Instances	Recommended for non-production Windchill databases (e.g. test, development, & training) Data files for each instance should be located on separate disks Acceptable for production and non-production Windchill databases for small deployments on a server with adequate resources	• Reduces the number of required database licenses • May reduce system maintenance (e.g. backup) • Variable load and availability less important since system is not business critical system	• May require more system memory • Performance and availability of each application may vary due to resource contention • Application and database upgrades may be delayed or more difficult if the required database versions conflict
3. Multiple Windchill and Non-Windchill Database Instances	Not recommended for more than one business critical enterprise application Not recommended when optimal performance and availability are desired	• Reduces the number of required database licenses- May reduce system maintenance (e.g. backup) • Variable load and availability less important since system is not business critical system	• May require more system memory • Performance and availability of each application may vary due to resource contention • Application and database upgrades may be delayed or more difficult if the required database versions conflict
4. One Database Instance, Two or More Windchill Database Schemas	Not recommended	NA	NA
5. One Database Instance, One or more Windchill Schemas and One or more Non-Windchill Database Schemas	Not recommended	NA	NA

Was this helpful?