In every migration, some things must be considered.
After all you must analyze the bad performance with MSSQL; MSSQL is a good DB but if you dont have a maintance plan or the configuration is wrong, you can have very bed performance. Also, if you dont understand this, you run the risk of having poor performance even on the new system.
Otherwise, on MSSQL the resource use depeds on the licence, for example the express you can use 4 core and 1GB of ram.
Oracle Exadata is use for very big DB (on terabyte scale) and I dont know if its 100% compatible with IIQ. About me, Oracle Exadata for iiq is like use a ferrari to go to the supermarket.
In conclusion, a migration it a very complex process that requeried a deep analysis and you run the risk to corrupt ot lost the data. Oracle has some tools can help you like Oracle SQL Developer Migration Workbench. Oracle GoldenGate and Oracle Data Integrator for migration. Oracle Real Application Testing for testing.
I dont want stop you, but I want to suggest you to find the cause of bad performace and if you don’t have 5-10TB of DB and billions of records, Exadata is very underutilized.
Oracle Exadata is not officially suported, also I’ve tried once and it does not work well.
Exadata tends to update itself make patches and this complete breaks the IIQ side.