Try sys.dm_exec_sessions dynamic management view.

Other related views and relationships displayed here: http://msdn.microsoft.com/en-us/library/ms181509.aspx

This is supported as per VMware article http://www.vmware.com/solutions/business-critical-apps/sql/%5B/url%5D

Hi,

You would do it for nonclustered indexes only. The steps are:

1) Create new filegroup:

ALTER DATABASE DB1 ADD FILEGROUP FG_Indexes

2) Add new data file (*.ndf) to the database and...

Hi,

The USERSTORE_SXC section in you log has the largest amount of memory: "SinglePage Allocator = 3909992 KB" (~3.7Gb).

It looks like large batch execution issue described in MS article: http://support.microsoft.com/kb/2001221

If the files are old then they will not have information related to your issue. The .mdmp file is more for the Microsoft support and not really readable, but .txt...

You can open SQLDump00NN.txt file in the same folder.

Is this the new SQL Server instance or you used it before? Were you able to connected to the SQL Server before?

Try also to change network protocols order for the SQL Client. Set TCP to be top protocol.

This MS article has information related to this error: http://support.microsoft.com/kb/319892/%5B/url%5D

There are also references to the security patch, but if you have SP 4 , so you should be fine.

Check...

This article from Microsoft has a little bit more information: http://support.microsoft.com/kb/897284/en-us

This is easy to fix. Just update index option:

ALTER INDEX [PK_tblIntDiscoveredItems] ON [dbo].[tblIntDiscoveredItems] SET (

ALLOW_PAGE_LOCKS = ON

) ;

You can check maintenance plans error logs in SQL Server "LOG" folder. You can double check the location by opening the maintenance plan and by clicking "Reporting and Logging" icon...

You wouldn't be able to use SQL Server Agent to run jobs. SQL Server Agent will not start without this parameter enabled. You can create sqlcmd backup scripts and run...

Something else that is required for the SQL Agent is SQL Server Broker enabled for the msdb database. You can check if it is enabled:

SELECT is_broker_enabled FROM sys.databases WHERE...

Did you check value for 'Agent XPs' ? You need to set this option to 1 as well:

sp_configure 'show advanced options', 1;

GO

RECONFIGURE;

GO

sp_configure 'Agent XPs', 1;

GO

RECONFIGURE

GO

Hi, I am not sure if this will help, but check 'Agent XPs' configuration option : sp_configure 'show advanced options', 1;

If option is 0 then you will not be able...