SqlServerWriter missing when VSSadmin list writers command is run

In this blog, I will discuss about what to do when : 1. we run Vssadmin list writers command and sqlserverwriter is missing and  2. Also, there is no error message in Application event logs and 3. Also, SQLserver VSS writer service is running Here are the steps you need to follow to resolve such…

9

Troubleshoot high CPU issue without using profile traces

  The scope of these issues is very wide but I would discuss about the approach which I follow to resolve these issues. I have resolved more than 50% of the cases by using this approach without even looking at profiler traces. I hope this will help you troubleshooting issues in your environment. It’s specific…

6

In SQL server, How to see the standby file path when we restore the database in standby mode:

  I was answering to the questions on Social.msdn.microsoft.com forum site, Someone posted the question :  How to see the standby file path when we restore the database in standby mode:  I checked lots of DMVs e.g. msdb..restorefile, msdb..restorehistory etc. but couldn’t find any place to get the standby file name. I Spent around 1-2 hours…

1

Perfmon counters missing for newly added database in sql server 2005

Hello Everyone! Recently I was working on a scenario in which we were not able to see any perfmon counters for newly added database. Evertytime we had to rebuild all the perfmon counters for sql server to get the perfmon counters of new database. It was just a workaround but we wanted to have a permanent resolution….


Data Capturing and Analysis using SQL Server 2008 Activity Monitor and SQL DMV’s

In this blog, I will be sharing a unique instance of data capturing and analysis using SQL Activity monitor ,SQL DMV’s and also their correlation. We usually tend to see Activity monitor for a quick understanding of SQL health and resource consumption. Here is a scenario very close to Network IO in Activity monitor. Below…


SQL Server encounters memory pressure and generate 701 Error due to incorrect configuration of Service Broker

Here is one of the rare scenario on SQL Server memory issue (701 error) caused due service broker misconfiguration or incorrectly used, causing memory object OBJECTSTORE_SERVICE_BROKER to grow and not releasing memory back. Below is the memory error, we observed in SQL Server error log followed by DBCC MEMORYSTATUS output. You will see below error…

1