This blog is about another common error reported by many DBA to me. He faced error related to create file in OS.
Here is the text of the message.
SQL SERVER – Login Failed – Error: 18456, Severity: 14, State: 38 – Reason: Failed to Open the Explicitly Specified Database
Error 18456 State 38: failed to open the explicitly specified database. The login worked and the database did not. The four usual causes.
SQL SERVER – The Cluster Resource ‘SQL Server’ Could Not be Brought Online Due to an Error Bringing the Dependency Resource
Installing a second SQL Server 2012 instance on my Windows cluster failed: the cluster resource ‘SQL Server’ could not be brought online. Here is the fix.
SQL SERVER – AlwaysOn Availability Group Listener – This TCP Port is Already in Use
Creating an AlwaysOn availability group listener in SSMS failed with error 19486: this TCP port is already in use. Here is what the ERRORLOG showed.
SQL SERVER – How to Create Linked Server to SQL Azure Database?
If you take the normal approach to create a linked server to SQL Azure Database, then you would end up in below error message.
SQL SERVER – Unable to Get Listener Properties Using PowerShell – An Error Occurred Opening Resource
A client could not change listener properties with PowerShell and got “An error occurred opening resource”. Here is the T-SQL query I shared and what fixed it.
SQL SERVER – How to Install SQL Server Management Studio (SSMS) From Command Line?
Want to install SQL Server Management Studio silently from the command line, say with SCCM? Here is the one line batch command I shared with a reader.