here's one I whipped up that works on 2000 and 2005.

set nocount on

if object_id('tempdb..#DBSpace') is not null

drop table #DBSpace

go

create table #DBSpace

(

ServerName sysname

,InstanceName sysname

,dbname sysname

,DB_OR_LOG_NAME sysname

,AllocatedMb integer

,UsedMb integer

,AutoGrowMaxSize integer

)

exec master.dbo.sp_MSForEachDb @command1...

sp_spacesused executes two transactions.

You won't be able to just pump it into a table with

INSERT table

exec sp_spaceused

You'll need to script out master..sp_spaceused and figure it out from there.

There...

There might be the root of the problem.

I might suggest firstly looking into snapshot isolation instead of nolock

If that turns up nothing you can still reduce blocking in any...

Different drivers handle the clob/blob differently between versions.

Does it matter if you use the lock hints or not?

Have you identified all your tables with LOB data types and...

try running

xp_cmdshell 'DEL M:\Microsoft SQL Server\MSSQL.6\MSSQL\Backup\Categories_10-21-2008.bak'

and you'll get your answer.

(hint: no spaces in dos file paths)

~BOT

When you specify a lock hint like nolock, you're overriding your connection's default isolation level.

In this case specifically nolock = read uncommited.

~BOT

Interesting problem.

I have a suggested approach:

Write an after trigger that adds the event's rowcounts to a counter table.

This will only get you counts AFTER the trigger is in place, but...

This is making some sense now.

Is this the SQL Agent trying to start a job and having the login fail?

the only realy thing here is disk availability.

Having master on some form of RAID is invaluable as you likely know. After that rely on your good backups and documentation...

look on the bright side, restoring master is a pain in the stones anyway.

It's not terribly difficult to reattach database files (assuming they're not toast) and recreate users. just...

You are partly correct.

Here is what happens on a full database backup

1. lock database blocking all transactions

2. place a mark in the tran log

3. release the database lock

4. back up...

orphan users are only SQL Auth users.

I don't really have an idea of how to help you, but you should check that the SQL Server service accounts are the same...

model and msdb don't matter... master doesn't really either

Ideally tempdb is on a different drive from the user databases because of the IO throughput.

there are lots of read/writes on tempdb;...

has the password expired on the service account?

you use the grant statement to grant access to an object by a securable

deny will do the opposite.

http://msdn.microsoft.com/en-us/library/ms187965(SQL.90).aspx

I query this information with sp_helprotect, but its also found in sysprotects in...