Re: Best Practices for MultiTerrabyte TDW
"Dr. Frank Tate" <frank.tate-9LkaxTQlAnxWk0Htik3J/[email protected]>
| Newsgroups | gmane.comp.sysutils.tivoli.general |
|---|---|
| Message-ID | <CAOprv-=7idd3wBpUHerqy5GCtgAck4AYTLf8BpB=SNAAr7Md6Q__25940.5292956673$1359064015$gmane$org@mail.gmail.com> |
Ya know what? The entire datadase is flat, with absolutely NO relationships, so you *could* use the DB2 that you're licensed to use for the "live" TDW, then just copy whatever tables you want into Oracle. In this type of situation I've found that what the DBA and/or reporting group of the customer wants to do is something new/sexy/cool/experimental that the WPA and especially SPA have absolutely no chance of dealing with. So separating the live DB from the one they want to mess with can make a lot of sense. Just set up the documented maintenance scripts for db2 to run via.cron and it won't really need any other work. Just a thought. Frank - from my phone On Jan 24, 2013 11:54 AM, "Gregory Mendes" <[email protected]> wrote: > Hello All, > > I have a TDW (Oracle) that will be over 25 TBs. I have the white paper or > best practices for TDW but it doesn't address handling these types of large > databases. > > I know about the TDW Load Projection spreadsheet but my customer refuses > to use it. So, they have calculated in their head what they think the size > should be. > > So, do you guys/gals have any suggestion or tips to give? > > Regards, > > Gregory R. Mendes > 770-317-8593 > > > _______________________________________________ > TME10 mailing list > [email protected] > Unsubscribe:[email protected] > > _______________________________________________ TME10 mailing list [email protected] Unsubscribe:[email protected]