You may turn on the audit for login in SQL Server.

Check the log file and remove the inactive logins.

Did you turn on Database Mail?

Do your stand alone server and cluster in the same domain (whether or not you need a different mail server)?

Are you sure that you did not highlight other code?

I copied your code and ran it on my test SQL 2005 without any issue.

It is a space issue.

My understanding is that Data Protector is an HP tool for backup/recovery.

Find the path of logs for this tool and check its space.

Best luck.

What errors did you get?

Here are some possible reasons, quoted from other sources.

Microsoft SQL Server 2000 64-bit is for Itanium CPU's only. It does not work on an x64 cpu...

Here are my input.

When you add node from the active node, SQL Server will automatically installed on the newly added node.

You do not have to restart existing node. But you...

Check the key word, master server. Using master server, you can control your jobs on multiple servers.

How about something as below?

CREATE PROC myProc WITH ENCRYPTION AS

SELECT * FROM sysusers

The disavantage is that no one can view it at all. You have to keep your source...

How about something as below?

EXEC master..sp_MSForeachdb '

USE [?]

IF DB_ID(''?'') > 4 --dont do system dbs

BEGIN

EXEC sp_msforeachdb ''GRANT EXEC on myProc TO PUBLIC''

END

'

Did you try to update your statistics, which is used in estmated execution plans?

You may try to build your string, then execute it.

DECLARE @var NVARCHAR(2000)

SET @var = 'SELECT * FROM Server_inventory WHERE INSTNC_NM = ''MSSQL1'''

EXEC sp_executesql @var

As far as I know, it is a mission impossible.

Drop the data saved in the master.dbo.sys.sysdatabases and remove related data and log files.

Could we grant VIEW and UPDATE a DTS package without granting EXECUTION to a user?

Many thanks in advance.

Have you ever try to set ISOLATION LEVEL? Its syntax is below.

SET TRANSACTION ISOLATION LEVEL

{ READ COMMITTED

...