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 |
|
steelkilt
Constraint Violating Yak Guru
255 Posts |
 Posted - 2002-10-21 : 15:15:13
|
| Hi.It has been determined that the machine running our SQL Server 7.0 needs both an OS reinstall and a SQL Server 7.0 reinstall. The machine in question is a Compaq ML 320 running WIN 2K Server. Following a virus attack months ago, the machine is behaving oddly and I've inherited the mess.This machine has two disk partitions, C: and E:MSSql70db directory is on E:We back up regularly using Veritas Backup Exec v 8.x which has the SQL Agent included (i.e. quick backup of all SQL dbs via checkbox).We also backup to disk E: regularly, full backup once a night, transactions every 3 hrs for our key db.My main question is how to ensure that the admins who are handling the reinstall will do it right, i.e. how to get things set up so I can simply reinstall my DBs from tape and/or hard disk and all will be good to go.I'm concerned about targeting the new server (same name) from the tape drive and having the tape drive tell me it can't find the machine due to unique backup IDs and such. Also, I'm concerned about any needed DSN re-assignment, i.e. how to make sure my end users can still hit the DBs from their Excel/Access front-ends.I won't even begin to talk about WIN 2K permissions schemes and how to preserve them.Any tips would be greatly appreciated, especially if you can point me to a resource that covers this in excruciating detail.Thanks. |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-10-21 : 15:26:37
|
| While this one's title is for SQL 2000, it should hold very close for SQL 7.0 too:http://www.sqlteam.com/item.asp?ItemID=10061AjarnMark also has two articles on migrating SQL 7.0 to SQL 2000, but the process is also very much what you'll encounter:http://www.sqlteam.com/item.asp?ItemID=9066http://www.sqlteam.com/item.asp?ItemID=9465I would recommend detaching the databases and then re-attaching them afterwards. That way you don't have to worry about the backups at all except in an emergency. You can copy the data files off to a separate drive, possibly on the network, and then reattach them quite easily. You can also scan the data files separately for viruses, but I'd recommend against any action that might "correct" or "disinfect" the files if indeed a virus is found, as it could corrupt the data. |
 |
|
|
steelkilt
Constraint Violating Yak Guru
255 Posts |
Posted - 2002-10-21 : 17:10:32
|
| thanks Rob. I assume detaching and reattaching the system dbs -- master, msdb, model -- on the fresh install of SQL 7.0 is OK as long as I'm sticking with V. 7.0?? or should I heed the warning in this case not to attempt to migrate those directly? If I don't migrate the system DBs directly, what do I stand to lose if (worst case) I end up starting with a fresh master, model, msdb on the cleaned server? We have very few jobs running, no DTS stuff, only one VERY IMPORTANT database.thx |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-10-21 : 17:17:53
|
| System databases should NOT be detached/reattached. You can script out any jobs using Enterprise Manager, or just recreate them by hand (if they're relatively simple). You'll lose logins, but they can be recreated.Also take at look at Jasper's article:http://www.sqlteam.com/item.asp?ItemID=10060And search SQL Team for "transfer logins" or something similar, there are a few articles on how to do it. |
|
|
|
|
|
|
|
|
How to reinstall/restore SQL 7.0 w/o probs?