:::: MENU ::::

Posts Categorized / Performance Tunning and Optimization

  • Jan 14 / 2010
  • 0
DBA best practices, dbDigger, Performance Tunning and Optimization, Publications of Atif Shehzad on MSSQLTips.com

Working with READ ONLY databases in SQL Server

If any of database is not meant to change, then it may be considered as good candidate for READ ONLY database. It is an important concept and requires proper analysis of pros and cos. My article related to Working with READ ONLY databases in SQL Server is published on following address. Due to copy right restrictions i will not publish it here. You may visit it at Working with READ ONLY databases in SQL Server

  • Dec 23 / 2009
  • 0
DBA best practices, dbDigger, Performance Tunning and Optimization, Publications of Atif Shehzad on MSSQLTips.com

Best practices for ALTER table operations in SQL Server

ALTER table operations are very important and may have far reaching effect. Such operations require extensive planning and analysis. My article related to Best practices for ALTER table operations in SQL Server is published on following address. Due to copy right restrictions i will not publish it here. You may visit it at Best practices for ALTER table operations in SQL Server

  • Jun 18 / 2009
  • 0
DBA best practices, dbDigger, Performance Tunning and Optimization, Publications of Atif Shehzad on MSSQLTips.com, Transaction log files

Move SQL Server transaction log files to a different location via T-SQL and SSMS

My article related to Move SQL Server transaction log files to a different location via T-SQL and SSMS is published on following address. Due to copy right restrictions i will not publish it here. You may visit it at Move SQL Server transaction log files to a different location via T-SQL and SSMS

  • Jun 06 / 2009
  • 0
kill SQL Server process
DBA Interview questions, dbDigger, Performance Tunning and Optimization

Use Kill command to terminate a SQL Server process

Some times it is required to get rid of an orphaned session or to end a session for removal of dead locks. SQL Server provides kill command for this purpose. You required System process ID (SPID) for this purpose. SPID may be get from sysprocesses or sys.sysprocesses
For example to get rid of an orphaned session with SPID 49, we have to issue following command.

Kill 49
GO

This powerful command has some restrictions associated with it. You can not kill your own process. So suicide is not permitted. Also it is not purposeful to kill the processes with following values under cmd column of sysprocesses or sys.sysprocesses.

  • AWAITING COMMAND
  • CHECKPOINT SLEEP
  • LAZY WRITER
  • LOCK MONITOR
  • SIGNAL HANDLER

Click here to read further about options associated with kill command

Consult us to explore the Databases. Contact us