We decided on SQL Server for Windchill and not Oracle.

[DamianCastillo]

We are using SQL Server for some other enterpises functions and decided to stick with the same platform for Windchill.

Does anyone have feedback on using Windchill with SQL Server?

Are there any differences/advantages in using SQL vs Oracle or vice versa?

Thanks for any feedback.

"Too many people walk around like Clark Kent, because they don't realize they can Fly like Superman"

[rpassolt]

One disadvantage is that you can't migrate another 3.4 database into a SQL system. We've had several customers acquire companies who have 3.4, but they went SQL so they have to export from 3.4 and bulk load into Windchill. You lose history and it takes a lot more time than the 3.4 to Windchill migrator. Other than that our customers have been happy with SQL.

[DamianCastillo]

We have no prior system. Going from Network folders to Windchill 10.1

🙂

In Reply to Rick Passolt:

One disadvantage is that you can't migrate another 3.4 database into a SQL system. We've had several customers acquire companies who have 3.4, but they went SQL so they have to export from 3.4 and bulk load into Windchill. You lose history and it takes a lot more time than the 3.4 to Windchill migrator. Other than that our customers have been happy with SQL.

"Too many people walk around like Clark Kent, because they don't realize they can Fly like Superman"

[rpassolt]

Understood, but if you acquire a company who is on 3.4 and you are on Windchill with SQL then you will have to export from their 3.4 and bulk load from the network, which is a pain. It would be nice if PTC would come out with a tool that would allow 3.4 to go into a SQL system (and maybe they are going to soon...no clue).

Best regards,

Rick

[DamianCastillo]

Rick,

Good point. Although we don't see this as something we need to worry about, it happens all the time in business. Having a nice way to move things over is something they probably would eventually provide.

It's not like SQL is not popular. 🙂

In Reply to Rick Passolt:

Understood, but if you acquire a company who is on 3.4 and you are on Windchill with SQL then you will have to export from their 3.4 and bulk load from the network, which is a pain. It would be nice if PTC would come out with a tool that would allow 3.4 to go into a SQL system (and maybe they are going to soon...no clue).

Best regards,

Rick

"Too many people walk around like Clark Kent, because they don't realize they can Fly like Superman"

[dips52]

The switch from SQL to Oracle was not possible before as Rick said but it can now be done. You must first migrate from Intralink to PDMLink using an Oracle database and then you can migrate from Oracle to SQL.

We have completed this procedure with pain and effort as the underlying problem wasn't the database or Windchill but a Windows issue. This bug has been fixed by Microsoft and a patch was given to complete the migration.

Regarding your question, the only benefits from using Oracle instead are that:

1) If you are migrating from 3.4 the process is a lot smoother and does not reuiqre a DB migration also once complete

2) PTC are equipped to support you better if you're on Oracle than SQL. (This is from experience)

I have seen no curcial issues with both platforms, SQL transaction log files can be a nuisance as they stop the DB from running if full. Both simple enough from a backup perspective as WTBackup performs the same way.

We would always suggest Oracle unless there is a real business need for SQL.