![]() Then we also were able to start SQL service normally. ![]() We were successfully able to shutdown SQL by using above command from SSMS query. I ran below magical query to shutdown SQL service. In above situation, it was in stopping state, still we were able to make connection to SQL Server and able to run queries. ![]() ![]() Looks like the “Change Pending” state is shown in SQL Server Configuration manager when actual service is in stopping or starting state. When we right click, we don’t see any option to do anything. Finally, they decided to stop SQL instance via SQL Server Configuration Manager, the state changed as “Change Pending”.įrankly speaking, I have never seen this state in configuration manager. They were in panic situation due to release pressure and so they changed the recovery model of the database to simple, to shrink the tempdb file. While doing that the tempdb database got full. So that added a few new columns to an existing table. ![]() My next oblivious question was what was done in the SQL Server to come to this state? They told me that they had some major release of the application and there were some changes needed in the database as well. As soon as I joined the call with them, they showed me below. Recently, one of my clients contacted me for an issue about Change Pending State where they were having issues where SQL Server. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |