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 |
denis_the_thief
Aged Yak Warrior
596 Posts |
Posted - 2013-02-24 : 14:10:43
|
I need to upgrade a Database to a new version of the vendor's software (i.e. a whole bunch of update scripts containing table changes, Stored Procs etc...).I obviously don't want anyone using it during the upgrade.What is the recommended practice here? Single User mode - Restricted User mode? Detach it from the Server and perform the upgrade on my personal computer and then put it back? Or any other idea would be appreciated. |
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2013-02-24 : 14:15:25
|
A few ideas:1) Take a full backup before you start anything for a rollback point2)Is there some way you can limit how the applications connect? Single user mode may be restrictive during an upgrade as multiple DBAs may need to work on the db3)Detaching it and working from another server is ok , will depend on point 2Jack Vamvas--------------------http://www.sqlserver-dba.com |
|
|
denis_the_thief
Aged Yak Warrior
596 Posts |
Posted - 2013-02-24 : 14:24:23
|
Thanks, there may be a way to limit connections from the application but I am not sure.Then maybe Restricted user would work? I would not have to worry about other connections and it would allow other DBAs to work on it. |
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2013-02-25 : 01:35:54
|
Resetricted_user mode is a good idea, as long as the users through the apps are not set at db_owner, dbcreator or sysadmin.Jack Vamvas--------------------http://www.sqlserver-dba.com |
|
|
|
|
|