2,410
We have a company where the Extender tables are over 50 GB in size. I can't seem to find a Best Practice for GP on table size and partitioning.
We would like to (if it won't break anything) partition the Extender tables off onto their own files to better manage the drive space.
Will doing so cause any problems?
GP 2010 SP2, SQL Server 2008 R2 (instance on a farm)
*This post is locked for comments
Ok, that's what I was afraid of. Data is being imported daily with SmartConnect / eConnect to the GL and Extender tables.
Yes it could affect existing data/reports/Smartlists but I cannot say for sure as that is not something we really test.
Ok, that won't be an option then.
Yes, there are 14 strings in the window. A few of the fields could be switched to numbers, but most are alpha-numeric values.
Would changing the field types affect current data/reports/smartlists?
The only way is to manually remove information from the tables which is not support and can cause problems. Is everything in Extender being entered as a String? If so you may want to switch to another type such as integ or lists ETC.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,214
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (