Windchill Modeler

Performance Guidelines
Document
Copyright © 2021 PTC Inc. and/or Its Subsidiary Companies. All Rights
Reserved.
User and training guides and related documentation from PTC Inc. and its
subsidiary companies (collectively "PTC") are subject to the copyright laws of the
United States and other countries and are provided under a license agreement that
restricts copying, disclosure, and use of such documentation. PTC hereby grants to
the licensed software user the right to make copies in printed form of this
documentation if provided on software media, but only for internal/personal use
and in accordance with the license agreement under which the applicable software
is licensed. Any copy made shall include the PTC copyright notice and any other
proprietary notice provided by PTC. Training materials may not be copied without
the express written consent of PTC. This documentation may not be disclosed,
transferred, modified, or reduced to any form, including electronic media, or
transmitted or made publicly available by any means without the prior written
consent of PTC and no authorization is granted to make copies for such purposes.
Information described herein is furnished for general information only, is subject
to change without notice, and should not be construed as a warranty or
commitment by PTC. PTC assumes no responsibility or liability for any errors or
inaccuracies that may appear in this document.
The software described in this document is provided under written license
agreement, contains valuable trade secrets and proprietary information, and is
protected by the copyright laws of the United States and other countries. It may
not be copied or distributed in any form or medium, disclosed to third parties, or
used in any manner not provided for in the software licenses agreement except
with written prior approval from PTC.
UNAUTHORIZED USE OF SOFTWARE OR ITS DOCUMENTATION CAN
RESULT IN CIVIL DAMAGES AND CRIMINAL PROSECUTION.
PTC regards software piracy as the crime it is, and we view offenders accordingly.
We do not tolerate the piracy of PTC software products, and we pursue (both
civilly and criminally) those who do so using all legal means available, including
public and private surveillance resources. As part of these efforts, PTC uses data
monitoring and scouring technologies to obtain and transmit data on users of
illegal copies of our software. This data collection is not performed on users of
legally licensed software from PTC and its authorized distributors. If you are
using an illegal copy of our software and do not consent to the collection and
transmission of such data (including to the United States), cease using the illegal
version, and contact PTC to obtain a legally licensed copy.
Important Copyright, Trademark, Patent, and Licensing Information: See
the About Box, or copyright notice, of your PTC software.
UNITED STATES GOVERNMENT RIGHTS
PTC software products and software documentation are “commercial items” as
that term is defined at 48 C.F.R. 2.101. Pursuant to Federal Acquisition Regulation
(FAR) 12.212 (a)-(b) (Computer Software) (MAY 2014) for civilian agencies or

2
the Defense Federal Acquisition Regulation Supplement (DFARS) at 227.7202-1
(a) (Policy) and 227.7202-3 (a) (Rights in commercial computer software or
commercial computer software documentation) (FEB 2014) for the Department of
Defense, PTC software products and software documentation are provided to the
U.S. Government under the PTC commercial license agreement. Use, duplication
or disclosure by the U.S. Government is subject solely to the terms and conditions
set forth in the applicable PTC software license agreement.
PTC Inc., 121 Seaport Blvd, Boston, MA 02210 USA

3
About this guide
Introduction
This document provides instructions, tips and tricks, and best practices to the
system/database administrator that result in enhancing the performance of
Windchill Modeler. The guidelines present in this document also help customers
plan their deployment. Some of the topics included in this document are:
• Optimal configuration options for installation
• Recommendations for multi-user management
• SQL Server optimization tips
• Optimizing Modeler for better performance
• General troubleshooting tasks

Technical Support
Contact PTC Technical Support through the PTC website or by phone if you
encounter problems using this product or the product documentation. The PTC
eSupport portal provides the resources and tools to support your implementation:
https://support.ptc.com/appserver/cs/portal/. For complete support details, see the
PTC Customer Support Guide. You must have a Service Contract Number (SCN)
before you can receive technical support. If you do not know your SCN, see
“Preparing to contact TS” on the Processes tab of the PTC Customer Support
Guide. This topic describes how to locate your SCN.

4
Hardware guidelines
The following sections outline the minimum hardware specifications for
deploying Windchill Modeler in different scenarios. For optimum performance,
PTC recommends using at least 32 GB RAM and utilizing SSDs (solid state
drives) for the computer that will host the Modeler Server and SQL Server.
When it comes to storage and performance, PTC recommends solid state drives
(SSDs). These are faster than conventional hard disk drives (HDDs) and are also
more reliable and use less power. When considering disk speed in terms of
sequential or random read/write speeds, SSDs are 2 to 5 times faster than
conventional hard disks. Note that the SSDs in question here are write-intensive
SSDs and not the usual read-intensive SSDs.
For information on SQL Server requirements and prerequisites, refer to the
Microsoft help topic:
Hardware and Software Requirements for Installing SQL Server 2017
For information about how much free disk space is required for each installation
type, see the Modeler Release Notes.

Windchill Modeler Client or Standalone Installation

For Client Only and Standalone installations of Modeler, we recommend a
computer with the following minimum specifications:
• Windows PC with a 3 GHz i5 processor
• 8 GB RAM recommended
• SVGA graphics, 1280x1024 minimum, 256 colors
• Supported Windows operating system - For more information, see the Modeler
Release Notes.
If the Client Only or Standalone installation is integrated with a Requirements
Management tool requiring both Modeler and the Requirements Management tool
to be running simultaneously, you should add the recommendations for CPU
throughput and RAM.
If you are using ACS to generate large quantities of code, or a Reverser to reverse
engineer large quantities of code, we recommend you use a computer that has 16
GB of RAM or more.

Windchill Modeler Server – Workgroup Deployment:

For Server Only installations supporting multi-user access of small models by up
to five concurrent users, we recommend a computer with the following minimum
specifications:
• Windows PC with a 3 GHz i5 or Xeon processor
• 8 GB RAM recommended (for SQL Server 2017 Express)

5
• SVGA graphics, 800x600 minimum, 256 colors.
• Supported Windows operating system - for more information, see the Modeler
Release Notes.

Windchill Modeler Server – Enterprise Deployment

If you want to support a greater number of concurrent users, or if you want to
store large models (for example, models that make a Database larger than 1 GB)
on a Modeler server, the recommended specifications may not provide a
satisfactory performance when performing operations that process a large number
of objects, such as check in and check out operations and versioning of models.
To maintain a good performance with a greater number of concurrent users or
large models, we make the following minimum recommendations:
• 3 GHz Xeon multi-core processor.
• 16 GB RAM recommended (for SQL Server 2017 Standard)
• Use fast SCSI disks (15,000 RPM) or equivalents.
• If you are using a RAID disk array, configure it as RAID 0. The RAID 5
configuration is not recommended because it performs poorly with large
numbers of small disk writes.
• Enable Write-caching on disks. Performance can be substantially improved by
enabling Write-caching, but if you do this ensure that the server has an
Uninterruptible Power Supply.
The following table suggests the minimum number of processor cores and the
minimum size of RAM that we recommend to support different numbers of users.
Number of Users Processor Cores RAM
10 4 16 GB
25 6 16 GB
50 6 32 GB
100 8 32 GB
200 8 32 GB

Note
Ensure that you have a working, regular backup procedure in place for your
models.
For more information, see topic “Setting up a backup procedure” in the online
help.

6 Windchill Modeler Performance Guidelines Document

Microsoft Remote Desktop Services and Citrix MetaFrame
Installations
If you set up a Modeler server and client on a Microsoft Remote Desktop Services
or Citrix MetaFrame computer, that computer must be powerful enough to run the
server and client software, along with any add-ins the remote clients choose to
use.
The following table suggests the minimum number of process cores and the
minimum size of RAM that we recommend to support different numbers of users.
Number of Users Processor Cores RAM
10 6 32 GB
25 8 32 GB
50 12 64 GB
100 12 64 GB
For more information on SSDs and HDDs, see here.

Disk Space Requirements

Refer to the Release Notes for guidance on disk space for installing Windchill
Modeler.

SQL Server performance

Using Enterprise/Standard Edition of SQL Server Installation on SSDs results in
better performance than on HDDs. With SQL Server 2017, the primary useful new
feature is Automatic Plan Correction (which relies on the Query Store feature
introduced in SQL Server 2016 and enhanced in SQL 2017). This feature helps
detect and automatically correct various query plan stability issues. Apart from
Automatic Plan Correction, there are other enhancements in SQL Server 2017,
such as smart differential backup, smart transaction log backup, improved backup
performance for small databases on high-end servers, and improved tempdb
diagnostics and monitoring among others.
To read more about Microsoft SQL Server 2017, you can refer to the following
links:
• What's new in SQL Server 2017
• Automatic tuning

Modeler architecture and deployment options

There are different deployment options and installation configurations for
Windchill Modeler:
• Individual user deployment

7
 This is the simplest option and is suitable for individual users or test
environments. This deployment utilizes the standalone configuration.
• Production – workgroup deployment
This option is suitable for production environments and can support small and
medium sized workgroups. This deployment options utilizes client/server
configuration.
• Production – enterprise deployment
This option is suitable for production environments and can support small and
medium sized workgroups. This deployment options utilizes client/server
configuration.

Individual User Deployment

This deployment type utilizes the Standalone installation configuration and allows
the Windchill Modeler Server and Client to run on a single computer. The
following diagram shows how the components of a Standalone installation work
together.
Use the Standalone configuration only when you have a requirement to run the
client software and the server software in a single user environment, that is, a
requirement to use local databases. A Standalone installation can also access
remote databases if required.
PTC recommends using SQL Server Express as a database for this type of
deployment. SQL Server Express is bundled with Windchill Modeler and can be
automatically installed with Windchill Modeler.

8 Windchill Modeler Performance Guidelines Document

If only the client software is required, perform a Client Only installation in
preference to a Standalone installation as this will have less effect on the
computer's resources.

Production – Workgroup Deployment

This deployment option utilizes a client/server installation configuration and
allows multiple users to share and work with models that are stored in databases
on a server. PTC recommends using this deployment when working in a small and
medium sized workgroup environment.
Client computers are installed with only the software required for developing
models (including software for add-ins), while the server computers are installed
with only the software required for managing databases and storing models.

9
The client software can access models stored in databases on many servers
through Model Explorer. In a client/server configuration, perform the server
installation before performing any client installations.

If only the client software is required, perform a Client Only installation in

preference to a Standalone installation as this will have less effect on the
computer's resources.

Production – Enterprise Deployment

To ensure optimum performance for distributed locations or where network
performance is not acceptable, application virtualization (Microsoft Remote
Desktop Services (RDS) or Citrix MetaFrame) should be used. This requires RDS
to be enabled or Citrix Server to be installed on the Windchill Modeler Server or
another server. Windchill Modeler Client must also be installed on this computer
and be able to access the Windchill Modeler Server.
For clients in distributed locations, RDS must be enabled or Citrix Client installed,
and they must be able to access the computer with RDS or Citrix Server.
Windchill Modeler Client does not need to be installed, as access to Windchill
Modeler is provide virtually.
PTC recommends using this deployment for optimum performance when working
in a large, distributed enterprise environment.

10 Windchill Modeler Performance Guidelines Document

PTC recommends using SQL Server Standard as a database for this type of
deployment for optimum performance. This must be installed before installing
Windchill Modeler, or an existing SQL Server Standard instance can be used.
During installation of Windchill Modeler, a database will be created and
configured in the selected SQL Server instance.

Network recommendations
In this topic, we will discuss how to set up trusted domains, how to work on a
standalone installation even when you are disconnected from the network, and
how to disable virus checkers while installation.

Setting up trusted domains

If your client has only one domain, then there is no issue of a trusted domain.
If a Modeler client and server are in different domains, you must set up read/write
trust between the two domains.
The method for setting up trusted domains is demonstrated in the following
example.
• The Server is named server1 and is in a domain named ServerDom.
• The Client is named client1 and is in a domain named ClientDom.
Domain ClientDom has read/write trust to domain ServerDom, which means that
any one from domain ClientDom can read and write resources to domain
ServerDom.

11
To work with Modeler, you must have a read/write trust between the two domains.
The client's domain ClientDom must be able to write to the ModelerATF share
directories on the server in domain ServerDom.
Make sure that the necessary trust relationships and permissions are set up by your
domain administrator.
If your Modeler client has two domains configured as child and parent domains,
and there is a trust relationship between the child and parent, then consider the
following:
• If Modeler is installed in the child domain, then SQL service must be executed
from the parent domain to enable access for both the domains.
• If Modeler is installed in the parent domain, then Modeler can not access the
users/groups that are in the child domain.

Making a standalone installation work when disconnected

from the network
If you want to be able to use a Standalone installation when the computer is
disconnected from the network, you must perform the task that applies to your
computer setup so that the SQL Server database can use TCP/IP.
If your computer is disconnected from the network, Windows may disable TCP/IP.
For more information, see The Modeler license stops working when disconnected
from the network.
If you are using a server-based floating license and you want Modeler to be
licensed when disconnected from the network, you must borrow the license you
require. For information about borrowing licenses, see the following topics:
• Borrowing a license from a server-based floating license.
• License borrowing — frequently asked questions.
• Returning a borrowed license to a sever-based floating license.

To Make a Standalone Installation Work when Disconnected from the

Network:
The computer name and DNS suffix must contain only valid characters. You may
also need to prevent the network card from going in to standby mode.
1. Display the system information about your computer:

12 Windchill Modeler Performance Guidelines Document

 • Under Windows 10, Windows 8.1, Windows 7 or Windows Server 2012,
from the Control Panel Category view, click the System and Security link,
and then click the System link.
• Under Windows Server 2008, from the Control Panel Home view, click the
System and Maintenance link, and then click the System link.
2. The computer name is shown by the Full Computer Name label.
3. Ensure the characters of the computer name are letters, numbers or hyphens. If
other character types are included, rename the computer name using only
letters, numbers or hyphens.
4. Display the Primary DNS suffix of your computer: click the Change Settings
link, click Change, and then click More.
5. Ensure the characters of the DNS suffix are letters, numbers or hyphens. If
other character types are included, rename the computer name using only
letters, numbers or hyphens.
6. If you have changed the computer name or DNS suffix, save the changes and
restart your computer.

To Prevent the Network Card from Going in to Standby Mode:

1. In Windows Explorer, right-click This PC, Computer or My Computer, and then
click Manage.
2. For Windows Server 2008 only, in the left pane, expand Diagnostics.
3. In the left pane, select Device Manager.
4. In the right pane, expand Network Adaptors.
5. Right-click your network adaptor, and then click Properties.
6. Click the Power Management tab.
If there is not a Power Management tab on the dialog, your network card is not
under power management and you can abandon this procedure.
7. Clear the Allow the computer to turn off this device to save power check box.
8. Click OK.
9. Close the Server Management window/Computer Management window.

Disabling virus checkers during installation

Virus checkers can cause problems when copying many files to a computer. Stop
virus checkers before installing Modeler.
We have experienced problems installing Modeler when the following virus
checkers and applications are running; PC-Cillin, McAfee, WinGuard and NIC
Diagnostics.

13
Use of Citrix/Remote desktops
If you are running Modeler over a slow network, you can improve its performance
by hiding the following parts of the Modeler user interface when not in use:
• The Property Pages
• Status Bar
Direct access of Models on another site can result in poor performance when there
is a WAN or firewall between the Modeler client and server. Using Microsoft
Terminal Server or Citrix MetaFrame can resolve this problem because the
Modeler server and client software reside on the same site.
When the latency of the connection between the Modeler client and server is such
that the performance of Modeler is not acceptable to you, you may be able to
access the models on the Modeler server directly by using Microsoft Remote
Desktop Services (RDS) or Citrix MetaFrame (Citrix).
In this scenario, the latency of the connection is not fast enough for an acceptable
performance of Modeler, but it is fast enough to support RDS or Citrix. When this
is the case, you can use RDS or Citrix to run the Modeler client software on the
Modeler server site. Remote users run the Modeler client software through RDS
or Citrix client software.
The following diagram illustrates a potential configuration for working across
sites in this way.

The following table summarizes the advantages and disadvantages of working

across sites in this way:

14 Windchill Modeler Performance Guidelines Document

Advantages Disadvantages
• Greatly reduces network traffic • You require a permanent connection
across sites. between the sites, but it does not
• Direct access of the model, so have to be a high-bandwidth low-
changes are immediately seen by latency connection.
other users of the model. • You need to install Microsoft
• No need to install Modeler on the Remote Desktop Services or Citrix
client computers. MetaFrame.

The following table outlines the steps for setting up the sites:
Step Consideration
1. On the server site, perform a You must perform a Server installation
Modeler Server installation. to install the floating license software.
The SQL Server and Floating License
Server software can reside on any site
computer.
2. On the server site, install the
Microsoft Remote Desktop Services/
Citrix MetaFrame server software and
the Modeler client software.
3. Set up a floating license for clients.
Define the default user settings.
4. Each user that wants to run Modeler
uses the Microsoft Remote Desktop
Services/Citrix MetaFrame remote
client software to run Modeler from the
Microsoft Remote Desktop Services/
Citrix MetaFrame computer.

Agile modeling using a multi-user model

Very often the point of modeling is to improve the communication between
people, that is, we want to use modeling to effectively share information about our
system between multiple stakeholders; often with different disciplinary skills and
backgrounds. This is especially true in the early phases of a project when it is
important to be able to propose and challenge ideas and make the appropriate
choices. This includes the ability to make corrections and restructure the model
without a formal change authorization process, and to be able to evolve the model
structure in collaboration with other users in a flexible way.

15
Modeler supports agile modeling using a server-based database providing a
collaborative modeling environment where modifications automatically propagate
to all active client sessions and yet where the user can selectively apply Modeler
CM features to control access and modification rights to a model and to track why
changes occurred.
To manage simultaneous access, the locking and unlocking of the model data is
performed automatically at the finest level of granularity. For example, when you
modify the Parameter of an Operation of a Class of a Package of a Model,
Modeler automatically locks (and then unlocks) just that Parameter item.

Usage
Modeler provides a turnkey solution for multi-user modeling using its relational
database and active data dictionary.

Benefits
Agile re-structuring: With Modeler, you can easily change the package structure in
a model as the project evolves without having to restructure and change the access
controls in an external CM tool. The ability to restructure model content can
increase modeling productivity, particularly in early lifecycle phases when the
structure of a system is still evolving.
Robustness: Multi-user ensures that model consistency is maintained at all times.
This ensures consistency of the model regardless of the number of users and
without mandating unnecessary process constraints.
Granularity and locking: When you begin to modify the location, name,
properties, or associations of an item, Modeler automatically applies a lock on the
item and then releases it when you complete your modification. The fine
granularity and transaction-based approach to locking, reduces the potential for
multi-user conflicts.
Usability: Multi-user support provides an effective and integrated platform for
coping with fluctuations and increases in project team size without enforcing
process change. Importantly, it enables a wide team, including non-software
stakeholders, to access and edit the model without requiring training in complex
software-orientated external CM systems and processes.
Reduced complexity and overheads: An integrated solution reduces the total cost
of ownership, including co-installation and support costs of complex external CM
tools.

16 Windchill Modeler Performance Guidelines Document

Recommendations
To exploit the benefits of Modeler's multi-user client/server architecture, you will
need to deploy Modeler in its Client/Server configuration rather than in
Standalone configuration. In a Client/Server configuration clients are installed on
separate machines and access is provided to central databases through network
connectivity.
For large teams (50+), or a Wide Area Network (WAN) where clients connect to
the server through routers or firewalls that degrade throughput, a practical
optimization for network utilization issues is to deploy Microsoft Remote Desktop
Services or Citrix as this will reduce network traffic. Due to the network lag
introduced by routers, this may also improve performance for local users who are
not connected to the server on the same Local Area Network (LAN).
To make appropriate use of this architecture it is strongly recommended that Full
Logging is enabled and the database is backed up regularly.
For more information about Full Logging, refer to the following SQL Server help
topic:
Recovery Models
It is also prudent to periodically test the integrity of the back up processes by
exercising the restoration capabilities.
If users are opening diagrams for read-only purposes, then it is recommended they
select the Open Diagrams Read-only check-box in the Tools Options dialog.

Breaking large projects into subsystem and

component specific models
When working with very large projects, it is not always practical to model the
complete system in a single model, because the size of the resulting model can
result in performance problems.
Typically, a large system comprises a number of subsystems and components, and
those subsystems can be modeled in separate models. It is good practice to
consider how best to allocate subsystems to different models before starting a
project. If a model becomes too large and it contains two or more subsystems, you
can move one or more subsystems to a different model.

Usage
If you want to move a subsystem or component to a different model, use Package
Import/Export or the Component Sharing Wizard to move the subsystem or
component Package to a different model. The Component Sharing Wizard has the
advantage of identifying any dependencies that the Package has.

17
Benefits
Model size: Breaking large projects into subsystem and component specific
models results in smaller more manageable models.
Scalability: Large projects can be modeled without individual models becoming
too large.
User access: When a model contains only a subsystem or component, access to
that subsystem or component can be controlled at the model level.

Recommendations
Ensure that each subsystem or component has its own Package.
When deciding how to assign subsystems to models, you should consider the
following factors:
• How large each subsystem is likely to be.
• Which users require access to the different subsystems.
• How connected the different subsystems have to be. You cannot create
Modeler links between subsystems that are in different models.
When a subsystem or component is likely to be reused:
• Ensure that the subsystem or component is modeled in its own Package, so
that it can be easily copied or moved.
• Consider using PTC Integrity Asset Library to create the subsystem or
component as a reusable asset. For more information about PTC Integrity
Asset Library, see the PTC website.
When breaking down a model that has become too large, consider moving
subsystems that have the fewest links to other subsystems first. When using the
Component Sharing Wizard to move a Package, the Component Sharing Wizard
can identify links to items that are outside of the Package.
When a system and its subsystems are modeled in more than one model, it is good
practice to version all the models at the same time. Failure to do so can result in
version skew.
PTC’s Asset Library is one good example of breaking a model into subsystems for
better management.

Asset library
Asset Library is a web-hosted systems and software engineering asset
management system that is provided by PTC.
In conjunction with Modeler, Asset Library is used for breaking what could be
large and cumbersome models into smaller models, which can represent the same
modular structure as your system-of-systems, or service-oriented and component-

18 Windchill Modeler Performance Guidelines Document

based applications. Modeler Asset models are published into Asset Library as
'black (or gray) boxes' with a sub-set of the models meta-data. These Assets can
then be used and reused in other Modeler models. The links held in both Modeler
and Asset Library provide a traceable link from the master Asset model (and its
version) to its Asset in an Asset Library and then on to any number of models that
use this Asset. This model chaining can run to any depth of model hierarchy.
As well as this Bottom-Up approach to Asset mining and reuse (or consumption),
the integration also enables Top-Down modular design. Tentative systems can be
modeled and then Asset Library can be searched for suitable Assets. Where they
exist they can be used, as above. Where they don't, the tentative 'black box' design
can be published into Asset Library as an 'Asset Specification' to be provided.
Then, a designer in the role of the Asset supplier can import the Asset
specification into their model as a starting point for design. This import can not
only include the 'black box' interfaces, ports, etc. but also Requirements, Variation
Points and other specification artifacts. This approach to Asset Specification for
Assets which are yet designed provides a powerful, architected, modular design
solution.
The preceding introduction has described the first publication and use for an
Asset. In real life, things change and Assets are updated over time. The integration
has been designed for change. When an Asset changes in Asset Library all of the
interested designers, who have used that Asset in their models, are automatically
notified of the change in an email. They can then review the changes and decide if
they want to apply the updated Asset information to their model. Once updated,
they can then use all of the Asset enhancements in their design.
The web based Asset Library may not always be available, particularly if you take
your Modeler models off-line. After you have published or used an Asset in your
Modeler model there is no need to remain connected to the Asset library as the
model contains the elements it needs to continue to function. You only need to be
able to connect to an Asset library while you are publishing or reusing Assets, or
navigation through the linked Assets and models.
This Help provides information for using the Asset Library integration from
Modeler.
The Asset Library integration is used by installing the Asset Library Bridge and
adding the Asset profile to each model that requires the integration. After setting
up the Asset Library integration the following additions are made to Modeler:
• The Asset Library pane is added so that you can quickly publish, find and
reuse Assets from within the Modeler environment.
• The Asset stereotype is available for creating new Assets in the model. This
also adds the Assets tab to the Property Pages of an Asset.
• The Asset submenu is available on the Model and on Assets.
For detailed information about using Asset Library, please refer to Asset Library
in online help.

19
Model Manager overview
Model Manager executes the model functionalities from the server and not from
the client. It is used to schedule operations such as backing up, importing, and
exporting models that can be performed out of working hours.
Model Manager is a web application that allows users to login to a Modeler server
and perform common database and model management tasks on that Modeler
Server.
Executing tasks on the Modeler Server, instead of the Modeler Client,
significantly improves performance of many operations.
Key features include:
• Perform common database management tasks including start, stop and
upgrade.
• Perform common model management tasks including export, import, new
version and upgrade profiles.
• Streamlined user experience for initiating, executing, monitoring and
managing tasks.
• Tasks can be scheduled to execute at specific times (for example outside of
working hours) in order to minimize the performance impact on the Modeler
Servers and users.
• Scheduled tasks can also be set to recurring, allowing routine management
tasks to be executed on a regular basis.
• Database and model access permissions are respected when using Model
Manager.

20 Windchill Modeler Performance Guidelines Document

Managing SQL log files
In Modeler, the logs files are usually not deleted, but are truncated on an as-
needed basis.
If your server has run out of disk space, you can try to regain some disk space by
truncating the log files. You can do this in Model Explorer by right-clicking the
database and selecting Backup ▶ Backup and Truncate Log.
You can also perform the same operation using SSMS by running the following
stored procedure on the master database:
EXECUTE spTruncateDatabaseLog <DBname>

Note
The above stored procedure works only if the log file size is greater than 2
GB. If it is, then the log file size is truncated to 64 MB.

For more information about stored procedures, refer to the SQL Server help topic
on how to execute a stored procedure:
For more information about backing up and deleting log files, see the
Administration chapter of the Modeler help.

Optimizing database performance

To improve performance, you can use the optimize database command to rebuild
or reorganize indexes based on the fragmentation in the indexes of tables. It is
recommended that you should execute the optimize command after performing
large transactions such as importing a huge database, cloning a database,
importing huge models, and also after performing backup and restore operations
on a database.

Note
The optimize command is available only to Administrators.

You can optimize a database by using one of the following tools:

• Model Explorer
See Optimizing a database (Model Explorer) on page 22.
• ScfUtils command Line
See Optimizing a database through ScfUtils (Model Explorer) on page 22.

21
• Model Manager
• SQL Server Management Studio
For more information about transaction logs, refer to the following help topic for
SQL Server:
The Transaction Log

Optimizing a database (Model Explorer)

To optimize a database
1. Start Model Explorer.
2. Locate the Database that you want to optimize:
a. Expand the SQL icon.
b. Expand the Server that owns the database you want to optimize.
If the Server that owns the Database is not shown, add the Server to Model
Explorer.
For more information, refer to Adding a server to Model Explorer.
c. If the Database you want to optimize is not shown, show the server's
databases, and optionally bookmark the database.
For more information, refer to Showing a server's databases.
3. Right-click the database you want to optimize, and then click Optimize.
4. Confirm that the Database optimized successfully message
appears.

Optimizing a database through ScfUtils (Model Explorer)

ScfUtils provides a command line interface for performing Model Explorer
functions.
You can optimize a database through ScfUtils.
If you have installed Modeler to the default locations, ScfUtils resides in the
following location:
C:\Program Files (x86)\Windchill Modeler\Modeler\Exe\
SCFUtils.exe
For information about optimizing a database through Model Explorer, refer to
Optimizing a database (Model Explorer) on page 22.

Syntax:
ScfUtils -optimizedb Enterprise "<database-ref>"

22 Windchill Modeler Performance Guidelines Document

Where:
• <database-ref> specifies the reference to a database for optimization.

Enter the database reference in the following format: \\SQL\<instance-

name>\<database>

Example:
ScfUtils -optimizedb Enterprise "\\SQL\Server1@MODELER\ModelsDB"

Other SQL optimization techniques

Occurrences of deadlock may also result in degrading server/database
performance. In such cases, the SQL engine automatically terminates lower
priority queries, but sometimes, priorities are set the same for all SQL queries.
Therefore, in such cases, query identification and termination can be done through
SSMS or you can also restart the SQL engine service. You should also consider
the possibility that the deadlock issue is not due to a Modeler-related query but
with the SQL engine; in such cases, you must restart the SQL engine service.

Windchill Modeler OSLC server performance

To improve server performance, follow the instructions provided in topic Modeler
OSLC Server Performance Enhancement.

Performance troubleshooting
Update statistics
You can use the UPDATE STATISTICS query to update optimization statistics
on a table or an indexed view. You can also execute the sp_updatestats
stored procedure to update the statistics if the default updates are not too frequent.
For more information on Update Statistics, see:
• Update Statistics (Transact-SQL)
• Update Statistics

Process Lock/Deadlock
A deadlock results when two or more transactions lock the same resources. You
can execute the sp_who2 stored procedure to determine which processes are
blocking or creating the deadlock.

Compatibility Levels
When you migrate a database from an older version of SQL server, the database
does not automatically change its compatibility level. All of the query optimizer
changes are gated to the latest database compatibility level. Therefore, execution

23
plans are not changed right at point of upgrade but rather when a user changes the
COMPATIBILITY_LEVEL database option to the latest available. This gating
capability provided by the database compatibility level, in combination with
Query Store, gives you a great level of control over the query performance in the
upgrade process.
The compatibility level can be set through SSMS:
Click Database ▶ Properties ▶ Options and set the COMPATIBILITY_LEVEL to
the latest.
For more information on Compatibility Levels, see the following:
• ALTER DATABASE (Transact-SQL) Compatibility Level
• Change the Database Compatibility Level and use the Query Store

Miscellaneous tasks for tuning up a database

The following are a few links from Microsoft SQL that may help you optimize
your database for optimum performance:
• Monitor and tune for performance
• Performance Dashboard
• Performance monitoring and tuning tools

24 Windchill Modeler Performance Guidelines Document