Yes, you can use Central Management server or Registered Servers. See my post here: http://www.mssqltips.com/sqlservertip/2855/sql-server-multi-database-query-with-registered-servers/[/url]

One of my favorite ones is: https://connect.microsoft.com/SQLServer/feedback/details/778203/books-on-line-has-bad-email-address-for-send-feedback

Pretty much the moral is: feedback does not work by design and it won't be fixed 🙂

It actually works for me, so it looks...

Try -Q instead of -q

You can use Windows authentication - you need to add -E parameter (no need to use username and password).

Check also if [NT AUTHORITY\SYSTEM] has sysadmin access on SQL Server (if WMI service runs as SYSTEM account).

Try to create a test alert and see if it works:

EXEC msdb.dbo.sp_add_alert @name=N'Test Alert - Create DB',

@message_id=0,

@severity=0,

@enabled=1,

@delay_between_responses=15,

@include_event_description_in=1,

@notification_message=N'WMI Testing',

@category_name=N'[Uncategorized]',

@wmi_namespace=N'\\.\root\Microsoft\SqlServer\ServerEvents\MSSQLSERVER',

@wmi_query=N'select * from create_database'

GO

After...

Do you use Default or Named instance?

Make sure that SQL Server Agent service has been restarted

The general recommendations are right, but in real life every database will be different. If this is vendor's application that requires a database you can ask software vendor what should...

Shrinking the log file is not the same as shrinking data file. If you shrink data file - yes, it will lead to fragmentation. Shrinking the log file will improve...

You can actually export reports to Excel and copy text from there. That's what I do when I need it.

Check the installation log files in %programfiles%\Microsoft SQL Server\100\Setup Bootstrap\Log\ folder.

Looks like performance dashboard for SQL Server 2005: http://www.microsoft.com/download/en/details.aspx?id=22602.

I don't think you can script Maintenance plan in SQL 2005, but if you need to change job's owner you can use this stored procedure:

EXEC msdb.dbo.sp_update_job @job_name = 'job_name', @owner_login_name...

The full error message is "An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full."

Are there any other...