upgrade for database master failed because upgrade step  sqlagent100_msdb_upgrade.sql encountered error 200, state 7, severity 25.

    SQL upgrade from SQL Server 2008 R2 SP3 32 bit to SQL Server 2012 SQL upgrade from 2008 R2 to 2012 Script level upgrade for database ‘master’ failed because upgrade step ‘sqlagent100_msdb_upgrade.sql’ encountered error 200, state 7, severity 25. This is a serious error condition which  might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the ‘master’ database,  it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective  actions and re-start the database so that the script upgrade steps run to completion.   2019-07-30 17:26:10.38 spid8s      Error:…

  • AutoMon,  DBA

    DBA AutoMon configure Database Centralized management server CMS

    Setup Database Centralized management server CMS DBA AutoMon This is a series of post which will have lot of posts and scripts, which will help DBAs to do proactive work – consolidation and quickly understand the environments. Some background and thanks to my senior DBA Roshan Joe Joseph, we have started together this automation and scripts in year 2008, when we don’t have much tools and where the client could not invest money to buy a tool. We started the DBA AutoMon and planned to build a front end GUI, we could not finish that due to family, personal life and different company career. In most of the service based…

  • DBA

    Log shipping LSN mismatch issue The log in this backup set begins at LSN , which is too recent to apply to the database

    How to troubleshoot LSN mismatch issue in log shipping I have got an email, how to fix for log shipping, I already have a post for alwayson https://www.sqlserverblogforum.com/alwayson/how-to-solve-the-lsn-mismatch-in-sql-server/ For log shipping: you will have entry like this in the job error Message 2019-12-21 21:09:45.39 *** Error: The file ‘\LAPTOP-ISGUKEUC\Backup_Copy\T_20191221153913.trn’ is too recent to apply to the secondary database ‘T’.(Microsoft.SqlServer.Management.LogShipping) *** 2019-12-21 21:09:45.39 *** Error:   The log in this backup set begins at LSN 31000000048600001, which is too recent to apply to the database. An earlier log backup that includes LSN 31000000048200001 can be restored. RESTORE LOG is terminating abnormally.(.Net SqlClient Data Provider) *** Following is the code to find…

  • DBA

    SQL server registered server CMS usage

    SQL server registered server usage It is very useful for DBAs and junior DBAs to collect information from all the servers, reports etc. Example: Collect all the logins, jobs, larger database size from all the 300+ servers etc. It is per user, each one needs to create their own category version wise or environment wise. Make sure, the query will run all the servers, try to use select mostly, if you are performing and DDL or DML verify it before running, since it will make changes in all the servers. You can also use centralized management server, it is for all users.

  • DBA,  Performance

    Parameter sniffing problem PSP SQL server database capture and analysis options

    Being a DBA we could see many of PSP parameter sniffing problem is SQL server database. I have seen many of it, following is the way to capture and analysis. Issue 1 – We had issue for one of the important claim data loads every night, which suddenly running long time to load the data. Issue 2 – The website is going unresponsive state daily once or twice By default SQL server will sniffing the parameter, meaning the SQL engine will store the plan in cache for any parameters the same plan will be used in the future. It is good most of the time, since parameter Sniffing is useful…