Timeline for Storage limit in production environment
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 25, 2015 at 6:13 | comment | added | parul | Salesforce article said that there will be no implications of data storage in production environment. Please see the link help.salesforce.com/… | |
| May 14, 2015 at 8:55 | comment | added | Doug B | I believe that having a lot of data can cause the system to be pretty slow - ie. if you have a table with a million rows it might be slower to work with than if it had a thousand rows. You can look to optimise queries, use indexes etc. to speed this up. I don't believe that exceeding the SF storage limit itself causes the system to be slower. I think it's likely that the two things: slowness and exceeding the limit - are both results of the same thing, having lots of data in your tables. | |
| May 14, 2015 at 4:15 | comment | added | parul | We cannot clean up the data, as it is the production environment. Would have to check with salesforce for some solution. Also I still need to know can exceeding the limit beyond a certain point cause system to be pretty slow ? | |
| May 13, 2015 at 15:56 | comment | added | CoryCowgill | Also you may see performance degradation in your reports, list views, queries, etc. because you have added data volumes that have crossed the Force.com Query Selectivity Thresholds. This usually means you need to create custom indexes and update your list views / reports / SOQL to be selective. More details here: help.salesforce.com/help/pdfs/en/… | |
| May 13, 2015 at 15:54 | comment | added | CoryCowgill | They have much stricter rules on the Sandboxes because that is not considered production environment, so they quickly cut you off in Sandboxes including Full Copy Sandboxes. That is why you see a descrpency between the % overages and the cutoff of adding new records. | |
| May 13, 2015 at 15:54 | comment | added | CoryCowgill | Salesforce.com will generally not stop you from adding data in your production environment. They do not want to stop production business from being conducted. However your SFDC AE will get notified that you are above your licensed data storage and come knocking for more $$$. | |
| May 13, 2015 at 13:39 | comment | added | Doug B | I used to see it a lot doing volume testing in sandboxes, we'd get to 110% or 120% and then it would just start consistently returning errors. My understanding (based on hearsay) is that this doesn't happen in Production orgs, and certainly I've seen the Production org significantly exceed the limit without any problem. | |
| May 13, 2015 at 11:42 | comment | added | Girbot | I have seen instances where on exceeding the limit and creating a new record there has been an error but it's not a consistent cut off point. I can recreate it in a developer sandbox I have that has emails copied to it. | |
| May 13, 2015 at 11:30 | history | edited | Doug B | CC BY-SA 3.0 |
added 127 characters in body
|
| May 13, 2015 at 11:24 | history | answered | Doug B | CC BY-SA 3.0 |