September 30, 2025 at 3:53 pm
I have run into a very strange issue restoring a large, partitioned database. I get the following when attempt to restore the database:
Msg -2, Level 11, State 0, Line 0
Execution Timeout Expired.
The timeout period elapsed prior to completion of the operation or the server is not responding.
The timeout occurs after exactly 30 seconds.
All servers are in AWS using EC2 instances with EBS drives.
Operating system: Windows 2019 Data Center
SQL Server: SQL Server 2019 Enterprise build 15.0.4440.1
Using SSMS, tried 20.2.1 and 21.4.8 on Amazon WorkSpaces and also locally from within an rdp session on the server. Also tried copying the backup from the S3 gateway backup location to a local drive. Nothing seems to make any difference.
My restore command is "RESTORE DATABASE xyz FROM DISK = '...\xyz.bak' WITH NORECOVERY.
Please note: Just running RESTORE VERIFYONLY will also throw this error
Database is partitioned by month and has 43 partitions.
Total database size is 3.6 TB
Compressed backup is 978 GB.
This seems like a bug. Does anyone have any experience with this issue? I thought I check here before opening a case with MS.
I've been a SQL Server DBA for over 30 years, started with version 4.21a. In all that time, I've never seen this issue.,
October 1, 2025 at 9:41 am
Did you try to show the restore internals in the sql server errorlog file ?
DBCC TRACEON(3004, 3605, -1);
-- trace flag 3014 provides even more backup/restore information
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data and code to get the best help
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
October 1, 2025 at 12:39 pm
i think you might be running the command in an application other than SSMS/sqlcmd or a Sql agent job, right? a python/PowerShell/dotnet command could potentially create a sql command object with a default of 30 second timeout.
SSMS defaults to zero/wait for ever.
if you ARE using SSMS, then if you go to Tools>>Query Execution>>SQL Server, there is an Execution time-out field....is it set to 30 instead of 0?
Lowell
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply