the multiple log files will be addressed as one sequential topology, but importantly If the log contains multiple physical log files, the logical log will move through all the physical...

you can't, sql uses transaction logs in a sequential manner, you will have to wait till normal log activity has left no active vlfs in the secondary log files.

Attempt to...

you mentioned OS upgrades and new sql server versions in an...

balasach82 (3/7/2013)

---

Georege, gazareth, correct. any below options are futile. I was under the impression, that scriptingo out logins which also has password, would work. But that is not the case....

if you use sp_help_revlogin it copies out the password in an encrypted format. Just run the script as its produced on your destination server and the login will be created...

upgrade dev, test till you are happy

upgrade test, test until you are happy

upgrade prod. If its a virtual, take a snapshot before the upgrade as a quick backout.

You cannot be...

I've not heard of anyone else changing server names and switching test and prod environments as part of an upgrade cycle. Keep prod as prod and test as test, then...

Markus (3/6/2013)

---

We use dns aliases for this purpose. Although, we DO have some app folks that ping that name and find out the real name and use it. ...

the developers are asking a lot of you there, the code should be flexible enough to cope with changes in server names for DR and migration from test to prod...

why the frequent server renames, can they not be avoided?

be aware the SSIS transfer logins task changes the password for sql logins to an arbitrary value (for security reasons but also makes it useless 🙂 )

these groups are used to manage security outside of SQL, so I cannot see a reason they cannot be renamed like any other windows group, but I have never tried...

The SID for the groups is actually used and this is not changed by the server rename so you don't have to rename the groups.

will you be using the original instance again?

Definitely offline SQL so you have a clean shutdown and to avoid any possibility of file corruption. If you are shutting down sql...

I wouldn't go the detach\attach route, rather use the alter database modify file command (see BOL).

stop connections to databases

backup the databases (for safety)

offline databases

run alter database with new physical name...