Before the upgrade, temporarily resize your Temp database to be at least as big as your GL30000 table (that sounds like your largest table). The upgrade process copies tables to temp, applies any changes to them and then copies them back to the production table. Depending on how your autogrowth options are set on your temp database, you could spend a very long time incrementally growing the Temp database on disk.
Do a full database backup and then change your Recovery Model from Full to Simple on your production database. This will turn off logging saving you time during the upgrade. When the upgrade is complete, flip your recovery model back to full.
If your database server is a Virtual Machine instead of a physical server, see if you have free ram available in your VM environment and consider temporarily allocating it to your database server. SQL Server will use all of the memory that you throw at it, loading more of your database in memory and saving you physical disk IOs. Again, after the upgrade resize your memory allocation back to its original size.
Rich LaMarche · Senior IT Specialist
16 South Golden St, Norwich, CT 06360
Office: 860-823-4170 • Cell: 860-908-9188
You Can Rely On Us! • Live Support 24/7/365:860-887-2555
CONFIDENTIALITY NOTICE: This communication, including any accompanying attachments and documents, is intended only for the use of the intended recipient and may contain confidential and/or proprietary information. If you are not the intended recipient, you are hereby notified that any use, disclosure, copying, dissemination, or distribution of any information derived from this communication is strictly prohibited and may constitute a violation of the Federal Electronics Communications Privacy Act. If you have received this communication in error, you must immediately delete and/or destroy this communication after notifying the sender by return email of your receipt of this communication.