Operational but able to restore additional transaction logs

I have databases which have been left in the operational, but able to restore
additional transaction logs mode. I had done this last week thinking I could
easily setup log shipping that day. Tonight's backup will be the first full
backup corresponding with transaction log backups. The full backup will need
to run against this database which currently shows (loading) as its state.
Should this be removed or fixed somehow - at this point, I cannot delete, or
restore, or anything else including go to the properties to reset the state
because the database is not in the databases collection for this server...
so, what do I do now?
Regards,
Jamie
Wow, I figured that one out. I checked the sysdatabases as I had tried to
detach the database that was indicated as loading. Detaching removes it
from the sysdatabases. I only needed to refresh the Enterprise Manager.
Regards,
Jamie
"thejamie" wrote:

> I have databases which have been left in the operational, but able to restore
> additional transaction logs mode. I had done this last week thinking I could
> easily setup log shipping that day. Tonight's backup will be the first full
> backup corresponding with transaction log backups. The full backup will need
> to run against this database which currently shows (loading) as its state.
> Should this be removed or fixed somehow - at this point, I cannot delete, or
> restore, or anything else including go to the properties to reset the state
> because the database is not in the databases collection for this server...
> so, what do I do now?
> --
> Regards,
> Jamie