Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
mart0369
Starting Member
11 Posts |
 Posted - 2008-09-29 : 11:21:07
|
| Problem solved. It was a setting on the server that was causing the problem.I'm getting error:6104 when I try to kill one of my own processes. I log out and get another user to kill the process, which works fine. The minute that I log back onto the server, the process appears again?What am I looking for in order to kill this?I would not normally care, but it is stopping me from doing a database restore.Cheers, |
|
|
jerry.goldring@gmail.com
Starting Member
2 Posts |
Posted - 2008-09-30 : 10:01:01
|
| Any chance of sharing which setting that was on you server? It might help someone else...Thx. |
 |
|
|
mart0369
Starting Member
11 Posts |
Posted - 2008-09-30 : 11:00:55
|
| When the DB admins setup my profile, they set the 'default' database on connection, to the database that I use. Therefore, it created an active pid to that database. So when I tried to 'restore' the database, I was getting the error that it was in use. In the end the 'default database on connection' option was not set to anything, thus problem solved. |
|
|
|
jerry.goldring@gmail.com
Starting Member
2 Posts |
Posted - 2008-10-07 : 12:25:54
|
| That was a subtle as can be. Thanks for the tip.Jerry |
|
|
|
|
|
|
Process will not die