Start and stop an SAP Central instance : WINDOWS / SQLSERVER

Hello,
Here is the second part of this SAP BC admin for beginners blog series: How to start/stop an SAP instance on WINDOWS/SQLServer

 Stop SAP & SQLServer
Connect to the operating system as sidadm,

• Start the SAP Management console :

• Stop the diagnostic agent ( DAA )

Right click on the instance and select stop  : Enter the requested passwordThis instance is made of a few processes and should stop within a few seconds.The diagnostic instance is then stopped.

• Stop the SAP instance :

Right click on the instance and select stop :This is the SAP applicative instance. Here, Solution manager in this example.
It is made of ABAP and JAVA processes.
Stopping this SAP instance will take more time, up to a few minutes.You can check the ABAP processes shutdown here :You can check the JAVA processes shutdown here :The SAP instance is then fully stopped :

• Stop the SQLServer database instance using SQL Server Management Studio as user sidadm :

The authentification to the database is done through the windows operating system authentification:Once connected, right click on the SID database and do the following choices:The database is then stopped.

• You can stop the instance in order to perform a full stop :

The application and database are then stopped. You can stop the server now.

If you need to perform a full stop without rebooting in order to do a kernel upgrade for example, you can manually stop the following services :Right click each service and stop it :The services are now stopped. Everything related to SAP and its database is stopped.

We now deal with the SAP instance startup.

Connect to the server  as user sidadm and do as follows :
SAP services restart :SQLServer services restart :You can then use the SQL Server management Studio to restart the database :

Note : the database was previously brought offline. The sidadm user uses the SID database as its primary logon database.
This means you’ll have to logon to the database instance as user “sa” through SQL Server Authentification :Then you can bring the SID database online :The database is then up and running.
You can restart the SAP instances using the SAP MMC :Startup of the Diagnostics agent :This instance starts instantly.
We start the SAP SID instance :The SID instance startup can take up to several minutes, especially if you also have an J2ee instance running in case of a dual stack system.
Still you can check the instance startup here :
ABAP partJAVA part :Once everything is started correctly, everything should be green :The SAP instance is then fully started and can be used.