We have a 300 GB database that I am test restoring to a new SQL Server 2016 instance, on a virtual Windows 2016 server, used for testing purposes.
The VM has 32 GB RAM, running on a 1 socket CPU with 10 logical processors. (E5 - 2670 , 2,6GHz). Not sure about the power setting, will check that with the guys who set up the VM.
The first time I restored, I did it from a
.bak- file from a 2014 instance.
The second time (still running) I did it from a backup made on the SQL Server 2016 instance.
Both times it took over an hour before the "5 percent processed" message was shown. Before that the percentage was on 0% (using a script that shows progress of restore). The restore was finished after about 2 hours the first time. I especially wonder why it takes so long for the process indicator starts going. What is going on in when that stays on 0%?
Is this is normal on a SQL Server 2016 instance, or could something be wrong? On the production server, a restore will go much faster, but it is difficult to compare since the prod is a dedicated server with multiple spindles, while the test-server is a virtual server.