I'm doing a test upgrade from 15.1.3 to 15.2.15 and are performing the ANSI conversion separate from the DBupgrader. The conversion never finishes converting our 17 million row (7.5GB) Activity table. When I say never finishes, I mean that after a week of SQL grinding away, it's still working on that table. ASI tech support says this process should take hours, not days. The database log file was very small at the beginning but has grown to 9GB even though my database is set to Simple for this process.
DB server specs:
dual quad core CPU
70GB free on 150GB drive.
SQL 2005 SP4
iMIS database size is 67GB
App server is separate box but we're not seeing hardly any resources being used during this conversion. We are running the ConvertTablestoANSI.exe on the app server.
What we're seeing is that eventually SQL server consistently spikes at 96% CPU on that box and stays at that level. It also takes most the RAM on that box as SQL usually does. The Activity_bak is being created and I've seen at least 4.9 million rows being copied to the Activity table. Later on in the process, if we try to login to SQL Studio to see how large the new Activity table has grown, we get a time out error on the connection. Both these servers are VMs so we've stopped the process and reverted back to snapshots twice but have gotten the same result after each time we've
Has anyone experienced poor performance on the ANSI conversion? Any suggestions as to options we should try would be greatly appreciated!
Second Baptist Church Houston