by Robert Desisto | May 10, 2013 | Comments Off
An org in the salesforce.com vernacular is a logical instance of data and metadata for a set of users. Selecting single org, multi org or a combination remains a key decision that will improve the effectiveness of salesforce.com projects for which business application managers are responsible. In a research note I recently published, How to Manage Salesforce.com Orgs for Optimal Benefit, I provide a framework business application managers can use to determine the most optimial salesforce.com Org strategy for their organization
When looking at my customer inquiries in the past year, Salesforce.com org structures are in the top 3 questions I recieve for clients about to embark on a salesforce.com project. Salesforce.com project managers must determine how many salesforce.com orgs they should use in their projects. An org unit is bound by both capacity limits (number of users and storage) and execution computing resources (query sizes and API limits). The specific limitations will be determined by the specific salesforce.com offering and edition. Therefore, making an incorrect decsion will have impact on the success on a salesforce.com project.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.