I have a question: when you added the file, did you set the size? Because in the existing image, this option is not visible. While I was testing, when IFI was disabled and I added the file to the database, it was created in under a second.
By the way, my laptop's hard drive is an SSD.
Suggestion: If possible, including the codes you tested in the article would make it much more complete.
I appreciate the suggestion. I usually do add the code blocks, but I missed this one! I added a 12.5 GB data file since that is the size of the existing data files. Whenever you add a data file, it is important to make the new file the same size as the existing data files so that the allocations can round robin across the files. If the file sizes are unequal, SQL Server follows proportional fill algorithm, filling the files based on the empty space, which can create a hotspot.
Point: When adding a new data file, make it the same size as the existing data files.
I have a question: when you added the file, did you set the size? Because in the existing image, this option is not visible. While I was testing, when IFI was disabled and I added the file to the database, it was created in under a second.
By the way, my laptop's hard drive is an SSD.
Suggestion: If possible, including the codes you tested in the article would make it much more complete.
I appreciate the suggestion. I usually do add the code blocks, but I missed this one! I added a 12.5 GB data file since that is the size of the existing data files. Whenever you add a data file, it is important to make the new file the same size as the existing data files so that the allocations can round robin across the files. If the file sizes are unequal, SQL Server follows proportional fill algorithm, filling the files based on the empty space, which can create a hotspot.
Point: When adding a new data file, make it the same size as the existing data files.
Thanks, will try this for a migration I'll be doing next week