Cannot start in Single User Mode

  • For a disaster recovery test we are being required to restore our master database to an alternate server.

    Several servers have worked fine.

    I have used SQL Server Configuration Manager and changed the startup parameters to Single Mode.

    When I use SQLCMD to restore the database I am plagued by an error stating there is basically another use logged in.

    I have started SQL Server from the command prompt as well (-m and -c options to watch for logins (I changed SQL Server security to log successful logins) and I see nothing.

    Any suggestions. I have googled the heck out of this and not coming up with anything else to try.

  • starting SQL Server 2008 there is an option available when using the -m parameter which sets the app name that is allowed to connect in single user mode.

    This limits connections to a single connection and that connection must identify itself as the SQLCMD client program.

    sqlservr -m"SQLCMD"

    This limits connect through the Query Editor in Management Studio,

    sqlservr -m"Microsoft SQL Server Management Studio - Query"

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • Perry Whittle (7/29/2013)


    starting SQL Server 2008 there is an option available when using the -m parameter which sets the app name that is allowed to connect in single user mode.

    This limits connections to a single connection and that connection must identify itself as the SQLCMD client program.

    sqlservr -m"SQLCMD"

    This limits connect through the Query Editor in Management Studio,

    sqlservr -m"Microsoft SQL Server Management Studio - Query"

    Repeated the steps above allowing only SSMS to connect and still faced with "Only 1 administrator can connect at this time"

    This is being dictated by our current DR plan which I don't entirely agree with. Need some thoughts. I'm just not a fan of relying on a Master database restore for a cold standby server. Too many factors that can make difficult.

    Even if I use Mirroring I am faced with keeping the Master database 'synced'.

    What is everyone doing when using Mirroring to keep Master sycned?

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply