| Table Partitioning [message #673731] |
Thu, 06 December 2018 22:40  |
 |
muthukrish104
Messages: 82
Registered: November 2017
|
Member |
|
|
Hi All,
We have a table with a size of 85GB, now we want to make a partition on it.
From where to start, what are the things to be considered.
Kindly guide me.
Regards
krish
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Table Partitioning [message #673737 is a reply to message #673731] |
Fri, 07 December 2018 01:41  |
John Watson
Messages: 8960
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
muthukrish104 wrote on Fri, 07 December 2018 04:40Hi All,
We have a table with a size of 85GB, now we want to make a partition on it.
From where to start, what are the things to be considered.
Kindly guide me.
Regards
krish What you need to consider is the potential for disaster. If you get partitioning right, there may be benefits; get it wrong, and there will be problems. Do not use partitioning because you can - use it to address a defined problem.
And do not say "the problem is that the table is big". In this case, size doesn't matter. It is your SQLs and business processes that you need to look a.
|
|
|
|
|
|
| Re: Table Partitioning [message #673770 is a reply to message #673765] |
Mon, 10 December 2018 01:02 |
John Watson
Messages: 8960
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
As I said, you are approaching this from the wrong direction. You first need to identify a problem. Examples:
A screen refresh is too slow.
A overnight batch job doesn't finish until lunchtime.
A report takes ten minutes, you need it in one.
Then you can consider if (and it is only "if") some partitioning strategy would help.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
