I hit the following issue this morning when I tried viewing the properties of a SQL Server database using SSMS: Microsoft SQL Server Management Studio Cannot show requested dialog. ADDITIONAL INFORMATION: Cannot show requested dialog. (SqlMgmt) Property Owner is not available for Database ‘[databasename]’. This property may not exist for this object, or may not
For anyone running Windows 2008 (or above), you can simply add the “Command Line” column to the Task Manager view. From there, the instance name will follow the “-s” startup option, for example: C:\…\Binn\sqlservr.exe” –sPREPROD If you’re on Windows 2000/2003 then it’s not quite as straight forward. You can either get the Process ID from
The following post provides step by step instructions for moving each of the SQL Server 2000 system databases, one by one, from one location to another, on the same server. These system databases being: master model msdb tempdb In this case, I need to move all of these system databases from E:\MSSQL\MSSQL\Data to D:\MSSQL\Data For the model and
Apparently, being able to use Oracle’s SQL Developer to connect to SQL Server databases has been around for a while (via third party drivers), but I only started using it today for the first time, with SQL Developer 4 EA2 after my colleague mentioned it to me this afternoon 🙂 First of all, thanks to
Having had to run through this process again recently, I thought I’d tidy up my notes on all of this, and put together a proper how-to post 🙂 When SQL Server 2005 was released, the added functionality of Database Mail came with it, giving us the ability to use SMTP to send email from SQL Server
This procedure has been disabled from SQL Server 2005 onwards, when the ‘Surface Area Configuration’ tool was introduced as part of security enhancements within SQL Server. SQL Server blocked access to procedure ‘sys.xp_cmdshell’ of component ‘xp_cmdshell’ because this component is turned off as part of the security configuration for this server. A system administrator can
This can happen following things like hardware failure, power outages, database files being locked by the Operating System (Anti-Virus, backup software etc.) or actual corruption of the database. Attempting the repair procedure below is really a last resort. If you have good and recent backups, then if at all possible I would perform point-in-time recovery of