June 29, 2023 at 9:14 am
This issue could be caused by SQL Server taking additional time to perform initialization tasks after the service starts. Here's a possible solution:
Open the SQL Server Configuration Manager.
Go to SQL Server Services.
Right-click on your SQL Server instance and select Properties.
In the Properties window, go to the Advanced tab.
Look for the "Startup Parameters" field and click on it.
Add the following parameter at the end of the existing parameters: -T4022
Click OK to save the changes.
Restart the SQL Server service.
The -T4022 parameter enables trace flag 4022, which will log additional information during startup. Review the error log file again (/var/opt/mssql/log/) to see if any specific tasks or issues are causing the delay. Adjustments may be needed based on the information logged.
I hope it will help.
Thanks
Raavikant
June 29, 2023 at 1:16 pm
Ravi, thanks for the suggestion. How do I run the configuration tool on Linux?
Thanks
Tom
June 29, 2023 at 1:23 pm
Ravi, I managed to do the following
sudo /opt/mssql/bin/mssql-conf traceflag 4022 on
However, it didn't give any extra info.
When run
systemctl status mssql-server.service
Active: active (running) since Thu 2023-06-29 13:19:25 UTC; 3s ago
Howerver on the errorlog
2023-06-29 13:21:06.07 spid29s [32767]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 1. ConcurrentSGAMUpdate: 1, CleanupUnderUserTransaction: 0. TranLevelPVS: 0
2023-06-29 13:21:06.08 spid43s Starting up database 'dmlvts'.
2023-06-29 13:21:06.08 spid42s Starting up database 'msdb'.
as you can see, it starts about 2 mins later than the service.
Rgs
Tom
June 29, 2023 at 6:54 pm
Does SQL on linux do a JIT compilation of the binaries?
Viewing 4 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply