I suggest you take a look at Books Online -> multiserver administration. 

Or look at the sql error log if it hasn't been recycled yet since the last restart.

try two more things:

1. make sure the destination D: drive has enough free space for the backup.

2. Use "with format" in the backup statement.

It requires a sql service restart to reflect the change made by the stored procedures.

You can try these extended stored procedures:

declare @mssqlservice nvarchar(100),

    @sqlserveragent nvarchar(100)

 select @mssqlservice = 'mssqlserver',

        @sqlserveragent = 'sqlserveragent'

exec master..xp_servicecontrol  N'QUERYSTATE', @mssqlservice

exec master..xp_servicecontrol  N'QUERYSTATE', @sqlserveragent

I don't think you can always do this....

You need to join sysusers, syspermissions, sysprotects and sysobjects tables in order to see complete info. Replace the name column in sysusers with your user name.

You can only have create permissions if you're...

YOu can create a user table to hold the status of DBCC process. If you run this in QA, start with a getdate() and end with the same function.

create...

Do you mean the table name also shows up in the diagram name?

My gutt tells me you've got a uncommitted transaction going on when the log becomes full. Therefore there is no way to truncate it. You will have to either expand...

You can use @rowcount = 10000 in a loop and having each update push forward until it reaches the limit. Then print out a line "update 10000 rows successful". Then...

It sounds like a blocking issue. It could also be resource contention. Set up a job that runs frequently that monitors blocking. alert you when blocking happens.

If you're using SQL 7.0 , then you'll need a dummy install to get the server name straightened out. For SQL 2k, following Steve's steps.

Seems you intend not to...

If you don't want to break log shipping, you'll have to keep the secondary dbs in either recovery or standby mode. Neither mode allows transactions. Therefore you can't shrink the...

depending on your query type...If a query only looks at REC_TYPE and STATE, then the second index appears obsolete. But it has one more key "SOURCE" so in case a query looks...

You don't need to mess around with the replication. You can directly truncate the published table without problem. Think of this as the same as a delete.