Timeline for Move a database (from decomisioned server) to an existing server with heavy ongoing loads
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 3, 2017 at 18:38 | vote | accept | BeginnerDBA | ||
| Jul 5, 2016 at 16:19 | answer | added | Kenneth Fisher | timeline score: 0 | |
| Jul 5, 2016 at 16:17 | comment | added | datagod | Find out the current average I/O, CPU, and memory usage on the existing server while under a heavy load. Do the same for the proposed target server. Now find out what your proposed target server can accommodate. Simple math will tell you if the new server has enough spare capacity. I suggest, however, that you trust your instincts on this one. Moving a heavy load onto an already loaded server is a disaster waiting to happen. | |
| Jul 5, 2016 at 16:00 | comment | added | BeginnerDBA | @Molenpad, I just edited the question . This may not be that technical of a question related to any issue, but its more of how to make that judgement of what parameters or values can conclude what we need to migrate on those loaded servers? | |
| Jul 5, 2016 at 15:58 | history | edited | BeginnerDBA | CC BY-SA 3.0 |
added 232 characters in body
|
| Jul 5, 2016 at 15:35 | comment | added | Molenpad | I'm not sure there is a question here to answer. You can only be provided with the options you have already outlined yourself, namely a) Keep things as they are and don't decommission the existing server or b) Verify that the alternative server can take the load of a new database and migrate it in, and be prepared to upgrade server components if not. | |
| Jul 5, 2016 at 14:55 | history | asked | BeginnerDBA | CC BY-SA 3.0 |