Skip to main content

SQL Servers 20 steps after start or re-start

This was always in my mind, what happened when we start or restart sql server services from os service panel. There are long list of activities process out to get connected with database. These are below :
1. Server process ID allocation and with Authentication mode.
2. Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQL2012\MSSQL\Log\ERRORLOG'.
3. Registry startup parameters setting for master, error,log -d,-e, -l
4. SQL Server detected cpu and cores and allocating as per licenses and configuration .
5. SQL Server is starting at normal priority base (=7). 
6. SQL Server Detecting RAM and allocating to server as per awe and configured. 
7. SQL Server Detecting Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0 for NUMA configuration.
8. Starting up database 'master' and do transactions rolled forward in database 'master' (1:0).
9. SQL Server Audit is starting the audits. 
10. SQL Trace ID 1 was started by login "sa".
11. A self-generated certificate was successfully loaded for encryption.
12 SQL Server detecting and starting network configuration port and propery, pipe, named pipe and Dedicated administrator connection.
13. Then SQL Server is now ready for client connections. 
14. Starting up database 'msdb'.
15. Starting up database 'ReportServer$SQL2012'.
16. Starting up database 'model'.
17. Clearing tempdb database.
18. The Database Mirroring endpoint is in disabled or stopped state.
19. Service Broker manager has started.
20. Starting up user database, transactions rolled forward in database.

Now SQL Server is ready to use.


Popular posts from this blog

mongoDB error : aborting after fassert() failure

What to do when facing errors on mongoDB “aborting after fassert() failure” I like errors, in mongoDB this is the first error I faced and luckily many times. This error i faced during restoring name-space on local and restarting db system. I am still searching the exact root cause of this issue but i am able to resolve the current problem through below steps. Remove all relevant namespace files from data-file route path.. Now repair mongo instance using mongod process. mongod --repair ////////// execute command from bin folder path  Then start server using mongd process, if started server successfully then .. mongod  ////////// execute command from bin folder path Restore last backups as normal process. Now check database by connecting mongo shell. Thanks for reading,  Please comment your experience if you faced and also share knowledge if you have better steps to resolve...  

SQL71562: external references are not supported when creating a package from this platform

Last week I got this error from one of developer who was trying to deploy his project from Testing server to SQL Azure QA server. He was using “Deploy Database to SQL Azure” option from SSMS Tool-Task option. After connecting to SQL Azure portal when operation started to deployment below errors occurs. Validation of the schema model for data package failed. Error SQL71562: Error validating element has an unresolved refrence to object xx.dbo.xxxx external refrences are not supported when creating a package from this platform . Reason: The reason of the this error was; some functions of project was dependent on master database and only single database was being deploy to SQL Azure. DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references So, this error was coming. Solution : I suggested him to create those function to locally

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription