[#Blogged] Developer Edition "DE org"

Development and deployment on Force.com typically take place in an environment or org, which provides a number of features and accommodations for applications within that environment. An environment lets you instantly start developing, testing and deploying your app in the cloud. For an explication of the types of environments, optically discern An Exordium to Environments.
Follwing are the salesforce licenses : 
Salesforce Customer Portal
2 Salesforce CRM licenses
2 Salesforce Mobile licenses
3 Salesforce Platform licenses
5 Salesforce Partner licenses
10 Salesforce Customer Portal Manager licenses  

Other Limits for Developer Edition:
5.0 MB of Data Storage
20.0 MB of File Storage ( attachments)
5000 API requests per 24 hours
Any number of applications
A 500 MB bandwidth and 10 minute service request time limits (per rolling 24 hours) 

Developer Edition (often referred to as a "DE org") is a fully-featured development environment with limits on data and users. Developer Edition is used for:

Trailhead - Salesforce's free and fun online learning tool requires Developer Edition.
Development and Testing - If you don't have a sandbox (a copy of your Salesforce production organization), you can use Developer Edition to isolate development and testing.

ISVs - Independent Software Vendors use DE orgs to create managed packages, which may then be released as apps on the AppExchange.

Developer Previews - Sometimes we release new functionality to Developer Edition before other editions, so you can practice with it.

Fun - You can have more than one Developer Edition, so use one whenever you want to mess around and try something new.

How to signup for free developer edition in Salesforce?

1. Open "http://developer.force.com/".

2. Click "Sign Up" button.
3. Fill in the details. Click "Sign me up". 
4. Verify the account in email.
5. Use "https://login.salesforce.com" for login.

[#Blogged] Different Types Of Sandboxes

Sandboxes :

A sandbox is a replica of an engenderment environment utilized for a variety of purposes, commonly including testing and development. Here's how it works: When you engender or refresh (essentially effaces and reconstitutes a sandbox utilizing the same name) a sandbox, a facsimile of the engenderment environment at that point in time is made.

Different types of Sandboxes 

FullSandbox - Plenarily testing changes against authentic data afore promoting to engenderment.  This may include utilizer acceptance testing.  All changes must go through this sandbox.  If multiple admins/developers are working on overlapping areas, this is the place where changes get merged.  Force.com IDE can be habituated to compare changes by separate developers of the same apex code.
Full sandboxes have the same storage limit as your production organization.Once you refresh the Full Copy Sandbox then to refresh it one more time you have to wait for 29 Days.

 Partial Data Sandbox - This is an incipient sandbox type and I am not quite sure what the intention was.  Probably just a more frugal alternative to a full sandbox.  If you have a full sandbox, then partial data sandbox sounds like a good place for utilizer training for incipient features, incipient employees, etc.  Having authentic data can authentically avail with training.  Additionally, possibly a place to work on integration changes since it can hold quite remotely of authentic data.
Partial Data sandboxes have a 5 GB storage limit.
Once you refresh the Partial Data Sandbox then to refresh it one more time you have to wait for 5 Days.

Developer - A place to work through solutions to incipient requisites.  The main conception is to keep arbitrary experimentation out of the full sandbox.  It there are multiple admins/developers, each one should get their own so that they don't trample on each others work (until they deploy to the full sandbox).

Developer sandboxes have a 200 MB storage limit.

Once you refresh the Developer Sandbox then to refresh it one more time you have to wait for 1 Day.

Developer Pro - The main distinction between this and Developer is the amount of data that can be stored.  It additionally prehends some product data from engenderment.  If those two things are paramount, utilize this one.  Otherwise, it's interchangeble with Developer.

Developer Pro sandboxes have a 1 GB storage limit.

Once you refresh the Developer Pro Sandbox then to refresh it one more time you have to wait for 1 Day.

[#Blogged] Login Failed in Apex Data-loader

If you are getting a failed to send request error you may need to check the server host Data Loader set. 

Resolution -Whenever you receive the error Failed to send a request to http://localhost/services/Soap/check the following:  1. Go to Settings | Settings and change the server name to https://www.salesforce.com 2. If logging into the sandbox, then the URL is https://test.salesforce.com

Check if your network is using a proxy - Getting the error message, "Failed to send a request to https://www.salesforce.com/services/Soap/u/31.0" typically indicates that you're going through a proxy server resulting in your login attempt from the Data Loader not making it from your local machine to Salesforce servers. If your network is utilizing a VPN, you'll need to include or set your proxy information in the Data Loader settings. We recommend contacting your IT department to get the following pieces of information:

- Proxy host

- Proxy port

- Proxy username

- Proxy password settings

Check network connectivity or local machine issues - Review the affected user record's login history. If the Data Loader's login attempt has been recorded, you'll want to check the login attempt status. You'll be looking for login attempts that failed due to:

- Incorrect password

- Login restrictions

- Missing a required security token(For Developer Edition, give password+security token as password. Username is as usual username.)

If you've confirmed that these are correct and the login attempt is still not recorded this is indicative of a firewall, router, switch, or other network related device or connectivity issue that's preventing the Data Loader's login attempt from properly reaching the Salesforce servers.

You may troubleshoot potential network issues by running the network tests outlined in the article, How do I run a ping and traceroute to Salesforce? and reviewing the results as outlined in the article, How to Interpret the Traceroute? to determine whether it may be appropriate to engage your IT or network administration team to investigate or for further assistance.

If you continue to see an issue and have ruled out the above causes you may also try completely uninstalling the Data Loader and Installing Data Loader once again or trying to login via the Data Loader on another machine to potentially identify and/or rule out the behavior being an installation or local machine issue.

[#Blogged] Steps to Download Apex Data Loader

The Salesforce Data Loader / Apex Data Loader is a client application for the bulk import or export of data. Use it to insert, update, delete, or extract salesforce.com records.

Frequently, you will use the Force.com platform to create applications that operate on data that you already have in some form - in comma-separated variable files, spreadsheets or other relational databases.

The Data Loader is an easy to use graphical tool that helps you to get your data into Salesforce objects. The Data Loader can also be used to extract data from database objects into any of the destinations mentioned above. You can even use the Data Loader to perform bulk deletions by exporting the ID fields for the data you wish to delete and using that source to specify deletions through the Data Loader.

Steps to Download Apex Data Loader :

1. Go to Setup - Administration Setup - Data Management - Data Loader in your Org.

2.  Click "Download the Data Loader" link to download the data loader.