"Greg D. Moore (Strider)" <mooregr_deleteth1s@greenms.com> wrote in message
news:HSksc.79976$hY.3322@twister.nyroc.rr.com...
>
> "Erland Sommarskog" <sommar@algonet.se> wrote in message
> news:Xns94F35FAA3EE57Yazorman@127.0.0.1...
> > Greg D. Moore (Strider) (mooregr_deleteth1s@greenms.com) writes:
> > > I'll have to try it again tomorrow if I get a chance, but as I recall,
> > > it's during a restore of a DB to our SQL 7.0 server.
> >
> > And EM is SQL2000 or SQL7?
> >
> > > And yes, I did a sp_who2 active and found the blocking SPID. A DBCC
> > > INPUTBUFFER on the spid showed the restore.
> >
> > I was more interested in what the blocked spid was up to.
>
> Ah good point. I THINK it was doing a select against the sysdatabases
> table, but I'll have to check later today.

Ok, finally remembered to do it.

The SPID doing the restore:
RPC "master"."dbo"."restore_foo" -- no real surprise here. this is the
stored proc doing the work.

The blocked SPID from SQL EM (2000) against the DB (SQL 7.0)

select name, DATABASEPROPERTY(name, N'IsDetached'), (case when
DATABASEPROPERTY(name, N'IsShutdown') is null then -1 else
DATABASEPROPERTY(name, N'IsShutdown') end), DATABASEPROPERTY(name,
N'IsSuspect'), DATABASEPROPERTY(name, N'IsOffline'), D




>
>
> >
> >
> > --
> > Erland Sommarskog, SQL Server MVP, sommar@algonet.se
> >
> > Books Online for SQL Server SP3 at
> > http://www.microsoft.com/sql/techinf...2000/books.asp
>
>