IMO, we should distinguish between a regular and an abrupt growth. Consequently, more detailed questions make sense only in the latter case. The former case should be handled automatically.
-
-
-
Yes, I agree. But for me, no partitioning (when option is there) means it was not designed for regular growth.
- Još 3 druga odgovora
Novi razgovor -
-
-
My current primary db I support is 130TB. Sometimes you just add the space so you can keep the locomotive on the tracks. 24 hour awr:pic.twitter.com/ZfHvlEAfoh
-
If we do an AWR Load Profile Horror Picture Show like
@dani_schnider did a SQL Horror Picture Show, you can be at the top
3% transactions are rolled back. On average 1 call out of two has a parse call. Oh, and 25 logons per second
Those 68MB/s redo, probably full of...
Kraj razgovora
Novi razgovor -
-
-
I'll hire a new DBA
-
An autonomous one?
- Još 1 odgovor
Novi razgovor -
-
-
Had a similar discussion recently. Other party was amazed I wouldn't just randomly add space. I think it's important to understand why something is growing, in case it shouldn't be...
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Good to know, I will just ask another dba then
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
And physical placement - IOT - physical ordering (especially if you partition) - column order - should this be in a TS with fixed extent size... - inline (x)LOBs?
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Don’t try that with
@oraclebase today. It was all in the original email. ;)Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
principal consultant & database evangelist at 


