blocks|key|197065|text|“用户当前已连接到该窗口”可能是SQL+Server+Management+Studio窗口本身。请尝试选择主数据库，然后再次运行ALTER查询。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|197066|entityMap^0|1T|5|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

The “user is currently connected to it” might be SQL Server Management Studio window itself. Try selecting the master database and running the <code>ALTER</code> query again.

blocks|key|2829140|text|该错误消息通常意味着有其他进程连接到数据库。尝试运行此命令以查看哪些已连接：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2829141|exec+sp_who|code-block|syntax|javascript|2829142|这将返回进程，然后您应该能够运行：|2829143|kill+[XXX]|2829144|其中xxx是您试图杀死的进程的spid。|offset|length|style|CODE|2829145|然后你就可以运行上面的语句了。|2829146|祝好运。|2829147|entityMap^0|0|0|0|0|F|4|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|10|8|@$M|11|N|12|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|14|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

That error message generally means there are other processes connected to the DB. Try running this to see which are connected:

<pre><code>exec sp_who
</code></pre>

That will return you the process and then you should be able to run:

<pre><code>kill [XXX]
</code></pre>

Where [xxx] is the <code>spid</code> of the process you're trying to kill.

Then you can run your above statement. 

Good luck.

blocks|key|197125|text|您可以添加选项以立即回滚您的更改。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|197126|ALTER+DATABASE+BARDABARD
SET+MULTI_USER
WITH+ROLLBACK+IMMEDIATE
GO|code-block|syntax|javascript|197127|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You can add the option to rollback your change immediately.

<pre><code>ALTER DATABASE BARDABARD
SET MULTI_USER
WITH ROLLBACK IMMEDIATE
GO
</code></pre>

blocks|key|201648|text|SQL+Server+2012：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|201649|右键单击DB+>+Properties+>+Options+>+[Scroll+down]+State+>+RestrictAccess+>+select+Multi_user，然后单击OK。|offset|length|style|CODE|201650|瞧！|201651|entityMap^0|0|4|2C|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

SQL Server 2012:

right-click on the <code>DB &gt; Properties &gt; Options &gt; [Scroll down] State &gt; RestrictAccess &gt; select Multi_user</code> and click OK.

Voila!

blocks|key|197099|text|我也遇到了同样的问题，并通过以下步骤解决了这个问题-+reference：http://giladka8.blogspot.com.au/2011/11/database-is-in-single-user-mode-and.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|197100|use+master
GO

select+
++++d.name,+
++++d.dbid,+
++++spid,+
++++login_time,+
++++nt_domain,+
++++nt_username,+
++++loginame
from+sysprocesses+p+
++++inner+join+sysdatabases+d+
++++++++on+p.dbid+=+d.dbid
where+d.name+=+'dbname'
GO

kill+56+--=>+kill+the+number+in+spid+field
GO

exec+sp_dboption+'dbname',+'single+user',+'FALSE'
GO|code-block|syntax|javascript|197101|entityMap|0|LINK|mutability|MUTABLE|url|http://giladka8.blogspot.com.au/2011/11/database-is-in-single-user-mode-and.html^0|11|28|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

I had the same issue and it fixed by the following steps - reference: <a href="http://giladka8.blogspot.com.au/2011/11/database-is-in-single-user-mode-and.html" rel="nofollow noreferrer">http://giladka8.blogspot.com.au/2011/11/database-is-in-single-user-mode-and.html</a>

<pre><code>use master
GO

select 
 d.name, 
 d.dbid, 
 spid, 
 login_time, 
 nt_domain, 
 nt_username, 
 loginame
from sysprocesses p 
 inner join sysdatabases d 
 on p.dbid = d.dbid
where d.name = 'dbname'
GO

kill 56 --=&gt; kill the number in spid field
GO

exec sp_dboption 'dbname', 'single user', 'FALSE'
GO
</code></pre>

blocks|key|197267|text|这对我来说很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|197268|步骤1.右键单击数据库引擎，单击活动监视器，查看哪个进程正在连接。杀死该特定用户并立即执行查询。|197269|第2步。|197270|USE+[master];
GO
ALTER+DATABASE+[YourDatabaseNameHere]+SET+MULTI_USER+WITH+NO_WAIT;
GO++|code-block|syntax|javascript|197271|并刷新数据库。|197272|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|R|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

This worked fine for me.

Step 1. Right click on database engine, click on activity monitor and see which process is having connection. Kill that particular user and execute the query Immediately.

Step 2.

<pre><code>USE [master];
GO
ALTER DATABASE [YourDatabaseNameHere] SET MULTI_USER WITH NO_WAIT;
GO 
</code></pre>

and refresh the database.

blocks|key|2829424|text|我实际上有一个问题，我的数据库几乎被进程和与它们的竞争条件锁定，当我刷新一个命令执行时，他们再次锁定它……我不得不在SSMS中背靠背地运行以下命令，并使我脱机，从那里我进行了恢复，并恢复为在线状态，这两个查询如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2829425|第一次运行：|2829426|USE+master
GO

DECLARE+@kill+varchar(8000)+=+'';
SELECT+@kill+=+@kill+%2B+'kill+'+%2B+CONVERT(varchar(5),+spid)+%2B+';'
FROM+master..sysprocesses+
WHERE+dbid+=+db_id('<yourDbName>')

EXEC(@kill);|code-block|syntax|javascript|2829427|然后紧接着(在第二个查询窗口中)：|2829428|USE+master+ALTER+DATABASE+<yourDbName>+SET+OFFLINE+WITH+ROLLBACK+IMMEDIATE|2829429|做了我需要的，然后让它重新上线。感谢所有为我写出这些片段的人，让他们结合起来并解决了我的问题。|2829430|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I actually had an issue where my db was pretty much locked by the processes and a race condition with them, by the time I got one command executed refreshed and they had it locked again... I had to run the following commands back to back in SSMS and got me offline and from there I did my restore and came back online just fine, the two queries where:

First ran:

<pre><code>USE master
GO

DECLARE @kill varchar(8000) = '';
SELECT @kill = @kill + 'kill ' + CONVERT(varchar(5), spid) + ';'
FROM master..sysprocesses 
WHERE dbid = db_id('&lt;yourDbName&gt;')

EXEC(@kill);
</code></pre>

Then immediately after (in second query window):

<pre><code>USE master ALTER DATABASE &lt;yourDbName&gt; SET OFFLINE WITH ROLLBACK IMMEDIATE
</code></pre>

Did what I needed and then brought it back online. Thanks to all who wrote these pieces out for me to combine and solve my problem.

blocks|key|2829737|text|我刚刚修复了使用以下步骤，它可能会对你有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2829738|步骤:+1|offset|length|style|BOLD|2829739|​|2829740|📷|atomic|2829741|2829742|2829743|步骤:+2|2829744|2829745|2829746|2829747|2829748|步骤:+3|2829749|2829750|2829751|2829752|2829753|步骤:+4|2829754|2829755|2829756|2829757|2829758|步骤:+5|2829759|然后运行以下查询。|2829760|ALTER+DATABASE+YourDBName
SET+MULTI_USER
WITH+ROLLBACK+IMMEDIATE
GO|code-block|syntax|javascript|2829761|尽情享受吧！|2829762|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/99c9a5e05721371061ba06f114403a16.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/ada811249068c7227c336107d593d7d0.png|2|https://ask.qcloudimg.com/http-save/yehe-900000/240781e9dc4168a100e0973faf23445a.png|3|https://ask.qcloudimg.com/http-save/yehe-900000/5ae543fc569cad5cea67307d065c694b.png^0|0|0|5|0|0|0|1|0|0|0|0|0|5|0|0|0|1|1|0|0|0|0|5|0|0|0|1|2|0|0|0|0|5|0|0|0|1|3|0|0|0|0|5|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1X|8|@$D|1Y|E|1Z|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|20|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|21|8|@]|9|@$D|22|E|23|1|24]]|A|$]]|$1|M|3|I|5|6|7|25|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|26|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|27|8|@$D|28|E|29|F|G]]|9|@]|A|$]]|$1|Q|3|I|5|6|7|2A|8|@]|9|@]|A|$]]|$1|R|3|K|5|L|7|2B|8|@]|9|@$D|2C|E|2D|1|2E]]|A|$]]|$1|S|3|I|5|6|7|2F|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|2G|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|2H|8|@$D|2I|E|2J|F|G]]|9|@]|A|$]]|$1|W|3|I|5|6|7|2K|8|@]|9|@]|A|$]]|$1|X|3|K|5|L|7|2L|8|@]|9|@$D|2M|E|2N|1|2O]]|A|$]]|$1|Y|3|I|5|6|7|2P|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|2Q|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|2R|8|@$D|2S|E|2T|F|G]]|9|@]|A|$]]|$1|12|3|I|5|6|7|2U|8|@]|9|@]|A|$]]|$1|13|3|K|5|L|7|2V|8|@]|9|@$D|2W|E|2X|1|2Y]]|A|$]]|$1|14|3|I|5|6|7|2Z|8|@]|9|@]|A|$]]|$1|15|3|-4|5|6|7|30|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|31|8|@$D|32|E|33|F|G]]|9|@]|A|$]]|$1|18|3|19|5|6|7|34|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|1C|7|35|8|@]|9|@]|A|$1D|1E]]|$1|1F|3|1G|5|6|7|36|8|@]|9|@]|A|$]]|$1|1H|3|-4|5|6|7|37|8|@]|9|@]|A|$]]]|1I|$1J|$5|1K|1L|1M|A|$1N|1O|1P|-4]]|1Q|$5|1K|1L|1M|A|$1N|1R|1P|-4]]|1S|$5|1K|1L|1M|A|$1N|1T|1P|-4]]|1U|$5|1K|1L|1M|A|$1N|1V|1P|-4]]]]

I have just fixed using following steps, It may help you.

Step: 1

<a href="https://i.stack.imgur.com/EPVke.png" rel="noreferrer"><img src="https://i.stack.imgur.com/EPVke.png" alt="right click on single user database"></a>

<hr>

Step: 2

<a href="https://i.stack.imgur.com/wZnbJ.png" rel="noreferrer"><img src="https://i.stack.imgur.com/wZnbJ.png" alt="take offline"></a>

<hr>

Step: 3

<a href="https://i.stack.imgur.com/tAx2K.png" rel="noreferrer"><img src="https://i.stack.imgur.com/tAx2K.png" alt="Drop connection and take offline"></a>

<hr>

Step: 4

<a href="https://i.stack.imgur.com/vZSPM.png" rel="noreferrer"><img src="https://i.stack.imgur.com/vZSPM.png" alt="Take online"></a>

<hr>

Step: 5

Then run following query.

<pre><code>ALTER DATABASE YourDBName
SET MULTI_USER
WITH ROLLBACK IMMEDIATE
GO
</code></pre>

Enjoy...!

blocks|key|3042099|text|最好是直接登录到服务器，而不是使用SQL+Management+Studio|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3042100|确保您登录的帐户是要设置为MULTI_USER的数据库的dbowner。以sa身份登录(使用SQL+server身份验证)(如果可以)。|3042101|如果您的数据库正由IIS使用，请停止网站和使用该数据库的应用程序池-这可能是已连接并阻止您设置为MULTI_USER的进程|offset|length|style|BOLD|3042102|USE+MASTER
GO

--+see+if+any+process+are+using+*your*+database+specifically

SELECT+*+from+master.sys.sysprocesses
WHERE+spid+>+50+--+process+spids+<+50+are+reserved+by+SQL+-+we're+not+interested+in+these
AND+dbid=DB_ID+('YourDbNameHere')

--+if+so,+kill+the+process:

KILL+n+--+where+'n'+is+the+'spid'+of+the+connected+process+as+identified+using+query+above

--+setting+database+to+read+only+isn't+generally+necessary,+but+may+help:

ALTER+DATABASE+YourDbNameHere
SET+READ_ONLY;
GO

--+should+work+now:

ALTER+DATABASE+Appswiz+SET+MULTI_USER+WITH+ROLLBACK+IMMEDIATE|code-block|syntax|javascript|3042103|如果您仍然有问题，请参考此处：|3042104|http://www.sqlservercentral.com/blogs/pearlknows/2014/04/07/help-i-m-stuck-in-single-user-mode-and-can-t-get-out/|3042105|作为最后的替代-如果您尝试过上述所有方法，但遇到困难时，可以尝试停止SQL+server实例，然后重新启动它|3042106|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|X|0|0|0|0|35|0|0|0|7|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|13|8|@$F|14|G|15|H|I]]|9|@]|A|$]]|$1|J|3|K|5|L|7|16|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|17|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|18|8|@]|9|@$F|19|G|1A|1|1B]]|A|$]]|$1|S|3|T|5|6|7|1C|8|@$F|1D|G|1E|H|I]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|R]]]]

It may be best to log onto the server directly instead of using SQL Management Studio

Ensure that the account you login as is dbowner for the database you want to set to MULTI_USER. Login as sa (using SQL server authentication) if you can

If your database is used by IIS, stop the website and the app pool that use it - this may be the process that's connected and blocking you from setting to MULTI_USER

<pre><code>USE MASTER
GO

-- see if any process are using *your* database specifically

SELECT * from master.sys.sysprocesses
WHERE spid &gt; 50 -- process spids &lt; 50 are reserved by SQL - we're not interested in these
AND dbid=DB_ID ('YourDbNameHere')

-- if so, kill the process:

KILL n -- where 'n' is the 'spid' of the connected process as identified using query above

-- setting database to read only isn't generally necessary, but may help:

ALTER DATABASE YourDbNameHere
SET READ_ONLY;
GO

-- should work now:

ALTER DATABASE Appswiz SET MULTI_USER WITH ROLLBACK IMMEDIATE
</code></pre>

Refer here if you still have trouble:

<a href="http://www.sqlservercentral.com/blogs/pearlknows/2014/04/07/help-i-m-stuck-in-single-user-mode-and-can-t-get-out/" rel="noreferrer">http://www.sqlservercentral.com/blogs/pearlknows/2014/04/07/help-i-m-stuck-in-single-user-mode-and-can-t-get-out/</a>

AS A LAST ALTERNATIVE - If you've tried everything above and you're getting desperate you could try stopping the SQL server instance and start it again

blocks|key|200257|text|你不能这样做，因为数据库在单模式下。首先，好吧，但您应该知道:当您打开sql+management+studio时，它不知道数据库上的任何用户，但当您单击数据库时，它会将您视为单个用户，并且您的命令不起作用。只需这样做:关闭management+studio，然后重新打开它。新建查询窗口，不选择任何数据库，编写命令脚本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|200258|USE+[master];
GO
ALTER+DATABASE+[tuncayoto]+SET+MULTI_USER+WITH+NO_WAIT;
GO+|code-block|syntax|javascript|200259|让f5+wolla万事大吉！|200260|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

You couldn't do that becouse database in single mode. Above all right but you should know that: when you opened the sql management studio it doesn't know any user on the database but when you click the database it consider you the single user and your command not working.
Just do that: Close management studio and re open it. new query window without selecting any database write the command script.

<pre><code>USE [master];
GO
ALTER DATABASE [tuncayoto] SET MULTI_USER WITH NO_WAIT;
GO 
</code></pre>

make f5 wolla everything ok !

blocks|key|199948|text|当我不知道用于切换到singleuser模式的特定SPID时，下面的代码对我很有效。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|199949|use+master
GO

select+
++++d.name,+
++++d.dbid,+
++++spid,+
++++login_time,+
++++nt_domain,+
++++nt_username,+
++++loginame
from+sysprocesses+p+
++++inner+join+sysdatabases+d+
++++++++on+p.dbid+=+d.dbid
where+d.name+=+'dbname'
GO

kill+52+--+kill+the+number+in+spid+field
GO

exec+sp_dboption+'dbname',+'single+user',+'FALSE'
GO|code-block|syntax|javascript|199950|entityMap^0|A|A|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

The code below has worked for me when I didn't know the specific SPID that was used to change into <code>singleuser</code> mode.

<pre><code>use master
GO

select 
 d.name, 
 d.dbid, 
 spid, 
 login_time, 
 nt_domain, 
 nt_username, 
 loginame
from sysprocesses p 
 inner join sysdatabases d 
 on p.dbid = d.dbid
where d.name = 'dbname'
GO

kill 52 -- kill the number in spid field
GO

exec sp_dboption 'dbname', 'single user', 'FALSE'
GO
</code></pre>

blocks|key|2829297|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2829298|尝试了所有操作都不起作用|ordered-list-item|2829299|远程登录到该服务器，因为我们将终止所有连接|2829300|多次运行以下代码，直到它返回完成，并且没有“终止进程”测试使用下面的代码|2829301|再次测试它|2829302|2829303|使用master+GO将@sql声明为varchar(20)，将@spid声明为整数|blockquote|2829304|2829305|select+@spid+=+min(+spid+)+from+master..sysprocesses+where+dbid+=+db_id('DB_NAME')+and+spid+!=+@@spid+while+(@spid不为null)+begin+print+'Killing+process‘%2B+cast(@spid+as+varchar)+%2B’...‘set+@sql+=+'kill‘%2B+cast(@spid+as+varchar)+exec+(@sql)|2829306|select+@spid+=+min(+spid+)+from+master..sysprocesses+where+dbid+=+db_id('DB_NAME')+and+spid+!=+@@spid+end|2829307|2829308|然后把它活着带回来|2829309|ALTER+DATABASE+DB_NAME+SET+MULTI_USER；GO|2829310|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|Z|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|10|7|@]|8|@]|9|$]]|$1|D|3|E|4|C|6|11|7|@]|8|@]|9|$]]|$1|F|3|G|4|C|6|12|7|@]|8|@]|9|$]]|$1|H|3|I|4|5|6|13|7|@]|8|@]|9|$]]|$1|J|3|-4|4|5|6|14|7|@]|8|@]|9|$]]|$1|K|3|L|4|M|6|15|7|@]|8|@]|9|$]]|$1|N|3|-4|4|5|6|16|7|@]|8|@]|9|$]]|$1|O|3|P|4|5|6|17|7|@]|8|@]|9|$]]|$1|Q|3|R|4|5|6|18|7|@]|8|@]|9|$]]|$1|S|3|-4|4|5|6|19|7|@]|8|@]|9|$]]|$1|T|3|U|4|5|6|1A|7|@]|8|@]|9|$]]|$1|V|3|W|4|5|6|1B|7|@]|8|@]|9|$]]|$1|X|3|-4|4|5|6|1C|7|@]|8|@]|9|$]]]|Y|$]]

<ol>
<li>Tried everything didn't work</li>
<li>Login to that server remotely as we gonna kill all connections </li>
<li>run the below code more than once till it returns completed and no "killing process" test anymore</li>
<li>reactivate it again using the code below the below code </li>
</ol>

<blockquote>
 use master GO declare @sql as varchar(20), @spid as int
 
 select @spid = min(spid) from master..sysprocesses where dbid =
 db_id('DB_NAME') and spid != @@spid 
 
 while (@spid is not null) begin
 print 'Killing process ' + cast(@spid as varchar) + ' ...'
 set @sql = 'kill ' + cast(@spid as varchar)
 exec (@sql)

<pre><code>select 
 @spid = min(spid) 
from 
 master..sysprocesses 
where 
 dbid = db_id('DB_NAME') 
 and spid != @@spid end
</code></pre>
</blockquote>

then to bring it back alive 

<blockquote>
 ALTER DATABASE DB_NAME SET MULTI_USER; GO
</blockquote>

blocks|key|3041909|text|这对我来说很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3041910|3041911|Take+a+backup|ordered-list-item|3041912|Create+new+database并将备份恢复到该数据库|3041913|，然后选择属性>选项>向下滚动状态>+RestrictAccess+>选择Multi_user并单击OK|3041914|3041915|旧数据库|3041916|希望这对所有人都有用谢谢Ramesh+Kumar|3041917|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|T|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|U|8|@]|9|@]|A|$]]|$1|J|3|-4|5|E|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

This worked fine for me

<ol>
<li>Take a backup</li>
<li>Create new database and restore the backup to it</li>
<li>Then Properties > Options > [Scroll down] State > RestrictAccess > select Multi_user and click OK</li>
<li>Delete the old database</li>
</ol>

Hope this work for all
Thank you
Ramesh Kumar

blocks|key|201831|text|如果上述方法不起作用，请找到spid的登录名并在Security+-+Logins中将其禁用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|201832|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If the above doesn't work, find the loginname of the spid and disable it in Security - Logins

blocks|key|199444|text|我很容易就解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|199445|199446|右键单击数据库名称更改后将其重命名为|ordered-list-item|199447|，右键单击数据库名称-->属性-->选项-->转到滚动数据库的底部(SINGLE_USER+to+MULTI_USER)|199448|Now+|199449|+you+RestrictAccess+SINGLE_USER+as+your+old+name.|199450|199451|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|P|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|R|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|S|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|T|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

I have solved the problem easily

<ol>
<li>Right click on database name rename it</li>
<li>After changing, right click on database name --> properties --> options --> go to bottom of scrolling RestrictAccess (SINGLE_USER to MULTI_USER)</li>
<li>Now again you can rename database as your old name.</li>
</ol>

blocks|key|2829450|text|只需转到数据库属性并将单用户模式更改为多用户|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2829451|​|2829452|📷|atomic|2829453|2829454|注意:如果对您不起作用，请再次执行数据库备份和还原，并再次执行上述方法|2829455|*+Single=SINGLE_USER|2829456|Multiple=MULTI_USER|2829457|Restricted=RESTRICTED_USER|2829458|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/c87f9e68f86406ce57fae63ec0bb3337.jpeg|imageAlt^0|0|9|0|0|0|1|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|16|8|@]|D|@$9|17|A|18|1|19]]|E|$]]|$1|K|3|G|5|6|7|1A|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1B|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1C|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1D|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|1E|8|@]|D|@]|E|$]]|$1|T|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|U|$V|$5|W|X|Y|E|$Z|10|11|-4]]]]

just go to database properties 
and change SINGLE USER mode to MULTI USER

<a href="https://i.stack.imgur.com/Z89VS.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Z89VS.jpg" alt="enter image description here"></a>

NOTE:
if its not work for you then take Db backup and restore again and do above method again

*
Single=SINGLE_USER

Multiple=MULTI_USER

Restricted=RESTRICTED_USER

blocks|key|3042080|text|在使用SQL+Server+2014的3次以上的情况下，我已经将数据库转换为单用户模式，而无需进行任何更改。它一定是在创建数据库时以某种方式发生的。上面的所有方法都不起作用，因为我总是收到数据库处于单用户模式且无法连接的错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3042081|我要做的唯一一件事就是重新启动SQL+Server+Windows服务。这使我能够连接到数据库并进行必要的更改，或者删除数据库并重新开始。|3042082|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

On more than 3 occasions working with SQL Server 2014, I have had a database convert to Single User mode without me changing anything. It must have occurred during database creation somehow. All of the methods above never worked as I always received an error that the database was in single user mode and could not be connected to. 

The only thing I got to work was restarting the SQL Server Windows Service. That allowed me to connect to the database and make the necessary changes or to delete the database and start over.

blocks|key|201849|text|进入单用户模式后，客户端只能与SQL+Server建立一个连接，请记住，“对象资源管理器”会占用一个(单独的)连接，因此，如果您尝试在查询窗口中运行多用户语句，您将收到错误消息，即在单用户模式下无法建立另一个连接。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|201850|对我来说，这不是问题所在，在我的例子中，很少有自动进程持续地(每隔几秒钟)建立连接，所以当我将数据库带入单用户模式并自己断开连接时，其中一个进程建立/占用了连接(在我可以开始恢复操作之前)。一旦我杀死了这些连接，它们就会重新连接，当我运行恢复命令时，我会得到连接已被占用的错误。|201851|为了解决这个问题，我不得不在一个查询窗口中编写kill语句、更改User-Mode语句和Restore操作，当我一次性运行所有这些操作时，瞧！啊，真灵。|offset|length|style|CODE|201852|希望这对其他人有帮助。|201853|entityMap^0|0|0|N|4|W|9|18|7|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@$F|Q|G|R|H|I]|$F|S|G|T|H|I]|$F|U|G|V|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|M|$]]

After going in to the Single-User mode, a client can establish only ONE connection with the SQL Server, remember that "Object Explorer" takes up a (separate) connection, so if you are trying run a Multi-User statement in a query window, you will get error that in Single-User mode you can't establish another connection.

For me this wasn't the issue though, in my case, there were few automated processes that were persistently (in every few seconds) establishing connections, so as soon as I took the DB into Single-User mode and disconnected myself, one of the processes established/occupied the connection (before I could start my Restore operation). As soon as I'd kill those connections - they'd reconnect and when I ran the Restore command, I would get the error that connection is already occupied.

To resolve this I had to write the <code>kill</code> statements, change of <code>User-Mode</code> statements and <code>Restore</code> operations all in one query window and when I ran them all in one go, voila!!! it worked.

Hope this helps others.

blocks|key|201860|text|我和当地的数据库出了点问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|201861|我能够解决这个问题，方法是停止SQL+server，然后启动SQL+server，然后使用SSMS+UI将DB属性更改为Multi_User。|201862|当我试图恢复备份时，数据库进入了“单用户”模式。在尝试恢复之前，我没有创建目标数据库的备份(SQL+2017)。这将会让你每次都有收获。|201863|停止SQL+Server，启动SQL+Server，然后运行上述脚本或使用UI。|201864|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I was having trouble with a local DB. 

I was able to solve this problem by stopping SQL server, and then starting SQL server, and then using the SSMS UI to change the DB properties to Multi_User. 

The DB went into "Single User" Mode when i was attempting to restore a backup. I hadn't created a backup of the target database before attempting to restore (SQL 2017). this will get you every time. 

Stop SQL Server, Start SQL Server, then run the above Scripts or use the UI.

blocks|key|201929|text|我在谷歌上搜索了一段时间，最终得出了下面的解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|201930|SSMS通常在后台使用多个到数据库的连接。|201931|在更改访问模式之前，您需要终止这些连接。(我已经在下面的代码模板中使用EXEC(@)；完成了此操作。)|offset|length|style|BOLD|201932|然后,|201933|运行以下SQL以将数据库设置为MULTI_USER模式。|201934|USE+master
GO
DECLARE+@kill+varchar(max)+=+'';
SELECT+@kill+=+@kill+%2B+'KILL+'+%2B+CONVERT(varchar(10),+spid)+%2B+';+'
FROM+master..sysprocesses+
WHERE+spid+>+50+AND+dbid+=+DB_ID('<Your_DB_Name>')
EXEC(@kill);

GO
SET+DEADLOCK_PRIORITY+HIGH
ALTER+DATABASE+[<Your_DB_Name>]+SET+MULTI_USER+WITH+NO_WAIT
ALTER+DATABASE+[<Your_DB_Name>]+SET+MULTI_USER+WITH+ROLLBACK+IMMEDIATE
GO|code-block|syntax|javascript|201935|要切换回单用户模式，您可以使用：|201936|ALTER+DATABASE+[<Your_DB_Name>]+SET+SINGLE_USER|201937|这应该是可行的。编码快乐！！|201938|谢谢！！|201939|entityMap^0|0|0|Z|G|0|0|3|0|0|S|0|0|0|G|0|0|0|E|0|0|4|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|14|8|@$F|15|G|16|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|17|8|@$F|18|G|19|H|I]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1A|8|@$F|1B|G|1C|H|I]]|9|@]|A|$]]|$1|N|3|O|5|P|7|1D|8|@]|9|@]|A|$Q|R]]|$1|S|3|T|5|6|7|1E|8|@$F|1F|G|1G|H|I]]|9|@]|A|$]]|$1|U|3|V|5|P|7|1H|8|@]|9|@]|A|$Q|R]]|$1|W|3|X|5|6|7|1I|8|@$F|1J|G|1K|H|I]]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1L|8|@$F|1M|G|1N|H|I]]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|11|$]]

I googled for the solution for a while and finally came up with the below solution,

SSMS in general uses several connections to the database behind the scenes.

You will need to kill these connections before changing the access mode.(I have done it with EXEC(@kill); in the code template below.)

Then, 

Run the following SQL to set the database in MULTI_USER mode. 

<pre><code>USE master
GO
DECLARE @kill varchar(max) = '';
SELECT @kill = @kill + 'KILL ' + CONVERT(varchar(10), spid) + '; '
FROM master..sysprocesses 
WHERE spid &gt; 50 AND dbid = DB_ID('&lt;Your_DB_Name&gt;')
EXEC(@kill);

GO
SET DEADLOCK_PRIORITY HIGH
ALTER DATABASE [&lt;Your_DB_Name&gt;] SET MULTI_USER WITH NO_WAIT
ALTER DATABASE [&lt;Your_DB_Name&gt;] SET MULTI_USER WITH ROLLBACK IMMEDIATE
GO
</code></pre>

To switch back to Single User mode, you can use:

<pre><code>ALTER DATABASE [&lt;Your_DB_Name&gt;] SET SINGLE_USER
</code></pre>

This should work. Happy coding!!

Thanks!!

I need help with setting a database that was restored in <code>SINGLE_USER</code> mode to <code>MULTI_USER</code>. Every time I run
<pre><code>ALTER DATABASE BARDABARD
SET MULTI_USER;
GO
</code></pre>
I get this error:
<blockquote>
Changes to the state or options of database 'BARDABARD' cannot be made at this time.
The database is in single-user mode, and a user is currently connected to it.
</blockquote>
It needs to be in non-<code>SINGLE_USER</code> mode to set it to another mode, but I can’t set the database in any another mode while it is <code>SINGLE_USER</code> mode.

Set database from SINGLE USER mode to MULTI USER

身份验证

SQL Server

数据库

服务器

Windows

我需要帮助设置一个在SINGLE_USER模式下恢复到MULTI_USER的数据库。每次我跑步的时候ALTER DATABASE BARDABARDSET MULTI_USER;GO我得到了这个错误：此时无法对数据库'BARDABARD‘的状态或选项进行更改。数据库处于单用户模式，并且当前有用户连接到该数据库。它需要处于非SINGLE_USER模式才能将其设置为另一种模式，但是当数据库处于SING

问将数据库从单用户模式设置为多用户模式
EN

回答 20

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将数据库从单用户模式设置为多用户模式EN

回答 20

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将数据库从单用户模式设置为多用户模式
EN