Single user mode during upgrade to SQL 2008?

Question

Single user mode during upgrade to SQL 2008?

SQL Galaxy

One Orange Chip

Points: 29472
More actions
September 8, 2012 at 12:19 am

#261699

IN place method for the database upgrade SQL 2000 to 2008,
Can I go for below one of the steps?
first database brings to single user in SQL 2000 database, then start upgrade installation on sql server 2008. once completed installation then apply SP3, finally database brings to multi_user mode

Viewing 6 posts - 1 through 5 (of 5 total)

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

Orlando Colamatteo SSC Guru Points: 182276 More actions · Answer 1

I am not sure what that would do to the installer. If the installer tried to open multiple connections it would fail, and it may in fact change the mode itself during the upgrade process. Not sure about 2000 but 2005 and the newer will deny connections during critical portions of an upgrade stating they are in 'administrative mode' or something like that.

Is your goal simply to guarantee users cannot connect to the database instance during the upgrade? If so then if you only have network clients to worry about then consider disabling all protocols except Shared Memory to essentially take the database instance off the network before doing the upgrades.

There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato

Revenant SSC-Forever Points: 42467 More actions · Answer 2

I would uninstall and do a clean install. I have seen too many problems with upgrades, especially if a between-version is skipped.

Jeff Moden SSC Guru Points: 1003853 More actions · Answer 3

ananda.murugesan (9/8/2012)
IN place method for the database upgrade SQL 2000 to 2008,
Can I go for below one of the steps?
first database brings to single user in SQL 2000 database, then start upgrade installation on sql server 2008. once completed installation then apply SP3, finally database brings to multi_user mode

No... Don't use the single user connection mode for this because if you lose connection for even a second, a web service will grab the connection and you'll be out of luck.

The proper way to do this is to make sure that all of the web services pointing to the server have been cleanly shut down.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

SQL Galaxy One Orange Chip Points: 29472 More actions · Answer 4

Thanks for your replay...

Mr. Jeff comments is good method stoping IIS services instead of using single user mode in database side.

I have done migration activity last weekend and application aslo working fine with SQL SERVER 2008, but i am did wrong method by used single user mode at databse side during IN PLACE upgrade action.

I should take care next time if any server migration action.

Perry Whittle SSC Guru Points: 233821 More actions · Answer 5

you could turn on your firewall and block incoming traffic to the port sql server is listening on

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

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