Try this one – Query: SELECT database_name = DB_NAME(database_id) , log_size_mb = CAST(SUM(CASE WHEN type_desc=”LOG” THEN size END) * 8. / 1024 AS DECIMAL(8,2)) , row_size_mb = CAST(SUM(CASE WHEN type_desc=”ROWS” THEN size END) * 8. / 1024 AS DECIMAL(8,2)) , total_size_mb = CAST(SUM(size) * 8. / 1024 AS DECIMAL(8,2)) FROM sys.master_files WITH(NOWAIT) WHERE database_id = … Read more
You could try setting the database to single user mode. https://stackoverflow.com/a/11624/2408095 use master ALTER DATABASE BOSEVIKRAM SET SINGLE_USER WITH ROLLBACK IMMEDIATE ALTER DATABASE BOSEVIKRAM MODIFY NAME = [BOSEVIKRAM_Deleted] ALTER DATABASE BOSEVIKRAM_Deleted SET MULTI_USER
SELECT name, create_date, modify_date FROM sys.objects WHERE type=”P” ORDER BY modify_date DESC The type for a function is FN rather than P for procedure. Or you can filter on the name column.
if not exists (select * from sysobjects where name=”cars” and xtype=”U”) create table cars ( Name varchar(64) not null ) go The above will create a table called cars if the table does not already exist.
SSMS in general uses several connections to the database behind the scenes. You will need to kill these connections before changing the access mode. First, make sure the object explorer is pointed to a system database like master. Second, execute a sp_who2 and find all the connections to database ‘my_db’. Kill all the connections by … Read more
If you happen to be using Windows 8 and up, here’s how to get to it: The newer Microsoft SQL Server Configuration Manager is a snap-in for the Microsoft Management Console program. It is not a stand-alone program as used in the previous versions of Microsoft Windows operating systems. SQL Server Configuration Manager doesn’t appear … Read more
Updated For MS SQL Server 2012 and above USE [master]; DECLARE @kill varchar(8000) = ”; SELECT @kill = @kill + ‘kill ‘ + CONVERT(varchar(5), session_id) + ‘;’ FROM sys.dm_exec_sessions WHERE database_id = db_id(‘MyDB’) EXEC(@kill); For MS SQL Server 2000, 2005, 2008 USE master; DECLARE @kill varchar(8000); SET @kill=””; SELECT @kill = @kill + ‘kill ‘ … Read more
Looks like you have a query that is taking longer than it should. From your stack trace and your code you should be able to determine exactly what query that is. This type of timeout can have three causes; There’s a deadlock somewhere The database’s statistics and/or query plan cache are incorrect The query is … Read more