Jennifer Smith 2 min

How to Spot Common Salesforce Org Growing Pains


Salesforce org growth leads to many challenges. Check out highlights from our recent on-demand webinar to learn how to successfully avoid common data growing pains. bit.ly/4ckqIMy



0:00

I want to talk about what happens to a lot of orgs when they think about data

0:05

management life

0:06

cycles because we often start out with a strategy whether that's spoken or oft

0:11

entimes unfortunately

0:12

unspoken it's not really been consciously thought about when we start off with

0:16

a new org and maybe

0:17

small data sets and that kind of works for a while when the data is new or the

0:21

data is still in

0:22

development but over time orgs tend to balloon and volume and those strategies

0:27

have to change or

0:28

they at least have to be consciously set so I would love to talk about the

0:33

challenges that you've

0:34

encountered as your data storage grew. Lori can you tell us about your data

0:39

storage growing over time

0:41

and how that kind of created some hurdles for you? Sure and I think there we

0:46

had we had two

0:48

challenges specifically related to that we migrated away from a so we have a

0:52

legacy sales force

0:53

environment and as you can imagine there was data in there but we reduced the

0:57

amount of user

0:58

significantly and so the availability of data that we had in there kind of

1:02

shrunk and so we had

1:04

to figure out how we handled that data as we keep it around for historical

1:08

purposes and how we get

1:09

within our data consumption limits in that environment so we had that one and

1:13

that was actually really

1:15

high attachments and files were something we really had to be concerned about

1:19

in that world so we had

1:20

to deal with kind of that world just from a legacy perspective and then as we

1:23

went into our new org

1:25

you know as you mentioned over time things just started creeping up on the on

1:29

the data side of the

1:30

house and so we really started to outgrow our ability to do like the annual

1:35

task of deleting

1:36

data based on certain policies that we'd set right so we were out growing that

1:40

you know pretty

1:41

quickly over the last three years and we had to look at a different kind of

1:45

continuous solution.

1:46

Right so the manual deleting of data which you were doing to you know keep your

1:52

storage down was

1:53

becoming kind of untenable right yeah and tenable and frankly wasn't working

1:58

because our data was

1:58

out growing faster than we could you know delete some of the objects that we

2:06

were okay with.

X

This is a test comment.

X

This is a longer test comment to see how this looks if the person decides to ramble a bit. So they're rambling and rambling and then they even lorem ipsum.


author