We've been on Windchill PDMLink for managing our Pro/E / Creo CAD data for nearly 4 years. We've grown to approximately 50 users, but still use it primarily as a CAD vault. We are in the process of upgrading from 10.0 M030 to 11.0 M010, are planning implementation of Change and Configuration Management and on the horizon plan to connect PLM to ERP (Infor Syteline). As the reach of the system grows and it becomes even more critical, we're considering the need for a MS SQL DBA to really optimize and maintain the various databases (those of PLM, ERP, various other internally created databases) as well as best define which is the master owner of each slice of information and how the systems can share information.
For Windchill, I've been asked to summarize what the regular tasks for a DBA would be and how much time it would consume. In going back and reading through PTC's "Best Practice Activities for Windchill System Monitoring and Maintenance", I've constructed the following (below) - but the time requirements for a SQL DBA are purely a guess. Keep in mind, doing the basics outlined in the PTC doc have kept it running smoothly with minimal intervention....but as we seek to better use the system and the information in it (not just the CAD files it manages), that's not going to suffice.
I'm looking for feedback both on the content and time required for a DBA's regular tasks for Windchill when used as PLM (not just CAD vault) and interconnected with other systems such as ERP.
Windchill PDMLink 10.0 M030, soon 11.0 M010
all servers running MS Windows, hosted on VMware 6.0
Veeam used for backup and replication
Regards,
Erik Gifford
G.W. Lisk Co., Inc.