Did you specified the db_executor role name under the where clause:

where D.name='SPECIFY ROLENAME HERE'

MJ

Have you gone thru http://support.microsoft.com/kb/911816

MJ

See if the default roles meets ur requirement:http://technet.microsoft.com/en-us/library/ms188283.aspx

Or you can explicitly deny access on sp_add_job stored procedure for that particular user.

MJ

From http://www.fmsinc.com/freE/NewTips/SQL/SQLtip9.asp

While only local devices are shown in Enterprise Manager’s Backup/Restore dialogs, there is a way to create or restore a SQL Server database backup on a network file share....

Try running profiler and see what are the queries that are consuming most of the CPU and tune them one at a time.

Also, make sure AUTO SHRINK and AUTO CLOSE...

If you have a stored procedure that uses a temp table the common assumption is that its deleted after the SP executes because you don't have drop it explicity in...

Try this:

DECLARE @sTableName SYSNAME

DECLARE @sSQL NVARCHAR(max)

DECLARE @iRowCount INT

DECLARE @t_TableNames_Temp TABLE

(table_name SYSNAME)

Drop Table TableGrowth

Create Table TableGrowth

(

DBName varchar(32),

SchemaName varchar(32),

TableName varchar(50),

TableID int,

MinRowSize int,

MaxRowSize int,

ReservedKB int,

DataKB ...

Try using the below mentioned script in a stored procedure and loop it through all databases on the server. Create and schedule a sql agent job which runs this stored...

What does that job do? Please post the job script if possible.

MJ

Does it display the same once you execute dbcc updateusage(0) with count_rows?

MJ

Use this:

SELECT C.name 'Schema',

B.name AS Object,

...

Its happening because the owner of the database is this login "xyz". To revoke permissions from it change the database owner to something else for eg. Exec sp_shangedbowner 'sa' and...

This is an expected message if the server runs under local admin or any domain account.

If you run SQL as Network Service or Local System, then the service will have...

Try putting up database in single user mode(if possible) and then run the code. If it runs fine then you need to find what else was bothering when it was...

Try to make use of the logic that 'tempdb' database gets created evrytime when sql server service is restarted so log this in a central table and report on how...