Property Size is not available for Database '[tempdb]'


Situation:
Many times, DBA try to view the TEMPDB properties but they get the following error:




The user is unable to view the TEMPDB property even if he has proper rights on the SQL Server instance. In fact, sometimes SYSADMIN role user is also unable to view the property and getting the same error.

Solution:

 For user databases, this error can be resolved by changing the database ownership. We can run this command to check the Database ownership:

sp_hepldb 'database name'

user databases ownership can be SET by using the following command:

USE 'db name'
go
sp_changedbowner 'sa'

However, you can not change ownership of SYSTEM databases (tempdb, master, model & msdb) through the sp_changedbowner command. 'sa' is the default owner of all the system databases.

I workaround this problem and found that this error frequently arises when tempdb is highly utilised and lots of contention is there on tempdb. In this scenario, SQL server is unable to read the database properties. I would recommend you to wait for some time until db contention is there and try after that. 
Another reason for this error is the corrupted tempdb files. In this scenario, check db health by running DBCC CHECKDB command. In my case, I found a couple of errors that represents the corrupted tempdb files. To resolved this issue, I stopped the SQL Server service and deleted the tempdb files and then started the SQL Server service. This process would recreate the new files on the underlying disk storage system and I was able to see the db properties after that.


Comments

Post a Comment

Popular posts from this blog

Split backup files for faster SQL Backups

Image
Situation: SQL backups for large database are always be a challenging task. Depending upon the available system resources, a typical 5 TB database backup may take 6 - 7 hrs to complete. In addition to this, it is very difficult for DBAs to copy a single large backup file over the network. Solution: SQL Server provides a flexibility to split single backup file to multiple files. This would allow SQL server to split the workload by creating multiple threads. The advantages of this is backups will run faster and creates smaller files that can be easily copied across the network. Additionally, in most of the cases, Database administrator takes compressed backups which reduce the backup file size. However, for large database backups, overall backups time would be large as SQL server uses single thread to complete the backup operation. In a critical production environment it is always be a requirement to complete the backups before business starts next day. This would ensure the succe...
Read more

Resolve SQL Server I/O bottleneck issues

Image
Situation: Nowadays, most of the SQL Server environment is running on virtualized environment.  VMWare, Hyperviser, Xen, Elastic compute cloud etc. are the most popular virtualization platform available in the market. As per the recommended best practice, we should have separate dedicated drives for  SQLTemp, SQLData, SQLLog, SQLBinary & SQLBackups. All these drives should be presented as individual LUNs to provide the best I/O throughput to the SQL Server. In-spite of implementing these best practices, SQL Server frequently encounters disk I/O latencies issues in most of the environments. We can see following error in the SQL Server error logs: SQL Server has encountered xxx occurrence(s) of I/O requests taking longer than 50 seconds to complete on file [D:\MSSQL\MSSQL.1\MSSQL\Data\MyProdDB.mdf] in database [database].  The OS file handle is 0x00000000.  The offset of the latest long I/O is: 0x00000000000000 Solution: There are many...
Read more