January 9, 2006 at 2:58 pm
January 9, 2006 at 3:39 pm
Stop using.
Go to Current Activity window, processes view, sort by database name, see who is using this very database, log off everyone except for yourself (call 'em first). Yourself, close everything, then open only Query Analyzer, make sure you are not in your database and run the detach statement.
Yelena
Regards,Yelena Varsha
January 9, 2006 at 3:52 pm
SPID | Status | Login | HostName | BlkBy | DBName | Command |
----- | ------------------------------ | ----- | ------------------------------ | ----- | ------ | ---------------- |
1 | sleeping | sa | . | . | master | SIGNAL HANDLER |
2 | BACKGROUND | sa | . | . | PMM2 | LOCK MONITOR |
3 | BACKGROUND | sa | . | . | PMM2 | LAZY WRITER |
4 | sleeping | sa | . | . | PMM2 | LOG WRITER |
5 | sleeping | sa | . | . | PMM2 | CHECKPOINT SLEEP |
6 | BACKGROUND | sa | . | . | PMM2 | AWAITING COMMAND |
7 | sleeping | sa | FRHG-ESI-TEST | . | master | AWAITING COMMAND |
8 | sleeping | sa | FRHGPURCH31 | . | msdb | AWAITING COMMAND |
10 | RUNNABLE | sa | FRHGPURCH31 | . | PMM2 | SELECT INTO |
I ran sp_who2 with the samw idea, I only get my self back, I am in a test environment, no has access? spid 8 and 10 are myself
January 10, 2006 at 9:53 am
Hi,
There is something on the server open with sa connection. Could it be Enterprise Manager open through terminal services? I would reboot the server, check that there is no jobs scheduled for data import/export for example and then use just 1 tool to detach. Do use Current Activity window, it will show you what application is trying to connect.
Regards,Yelena Varsha
January 10, 2006 at 10:36 am
Put db in single user mode and then try the dettach.
January 10, 2006 at 10:40 am
Worked great THANKS!!!!!
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply