Skip to content
Tutorials Center
My learning

Topics

Lesson 2 of 36 ยท Getting Started

Editions and Installation

Compare Stata BE, SE and MP, understand licenses and system requirements, install and update Stata, and add community packages with ssc install.

Before your first command you need a working copy of Stata. This lesson explains the three editions, how licensing works, how to install and update, and how to add the community-written commands that make Stata far more powerful than the base install. Because the installer is a normal desktop program, we describe the steps instead of running them.

The three editions

Stata is sold in three editions that run the same commands. They differ in how much data they can hold and how fast they are.

Edition Name Typical use Limits (approximate)
Stata/BE Basic Edition Students, small projects About 2 billion observations, 2,048 variables
Stata/SE Standard Edition Most researchers Same observations, up to 32,767 variables
Stata/MP Multiprocessor Big data, long models Up to 20 billion observations (largest versions), 65,532 variables, uses several CPU cores

The exact limits change between releases, so check help limits in your own copy. What matters for beginners: a do-file written in one edition runs in the others as long as the dataset fits. Code does not change; only capacity and speed do.

flowchart TD
    A["Dataset small?<br/>fewer than 2,048 variables"] -->|"yes"| B["Stata/BE is enough"]
    A -->|"no, many variables"| C["Stata/SE"]
    C --> D["Huge data or slow models?"]
    D -->|"yes"| E["Stata/MP (multi-core)"]
    D -->|"no"| C

Choosing an edition: variables decide BE vs SE, data size and speed decide MP.

Licenses

Stata is not free. Common ways to get it:

  • Perpetual license: pay once for a version and use it forever. Updates within that version are free; a new major version is a new purchase.
  • Annual license: a yearly subscription that always includes the newest version.
  • Student and academic pricing: large discounts, often with short-term (6 or 12 month) licenses for students.
  • Site or campus licenses: many universities and institutes buy one license that covers all staff and students. Ask your IT department before paying.
  • Stata Now / web options: StataCorp has offered cloud-style access in some releases; check the vendor site for what is currently on sale.

During installation you enter a serial number, an authorization code and a license key printed on your invoice. Keep them safe: you need them again if you reinstall.

System requirements

Stata runs on Windows, macOS and Linux. Requirements are modest: a recent 64-bit operating system, a few GB of disk space and enough RAM to hold your data. Because Stata loads the entire dataset into memory, RAM is the real limit. A dataset that is 2 GB on disk needs a bit more than 2 GB free RAM. Plan for about the file size plus working room for new variables.

Installing

  1. Download the installer for your operating system from your Stata account page or your university portal.
  2. Run it and accept the license agreement.
  3. When asked, enter the serial number, code and key.
  4. Choose an install folder and finish.
  5. Launch Stata. You should see the main window with a Command box at the bottom and a Results area.

On Linux there is also a command-line version, started with stata (text mode) or xstata (windowed). On Windows you may see the StataNow or numbered launchers such as StataMP-64; they differ only by edition.

Updating the software

Stata checks for updates against StataCorp's server. Inside Stata you can type:

STATA
update query      // check which version you have and whether updates exist
update all        // download official updates

You can also use the menu Help > Check for Updates. Updates fix bugs and add small features to your current release, without changing results from earlier code. After an update Stata asks to restart.

To see which version you run, type:

STATA
about
version

about prints the license and release number; version prints the language version your session emulates. That second one matters later when you write do-files that should keep working in future releases.

Installing community packages

Many useful commands are written by other researchers and shared on the Statistical Software Components (SSC) archive hosted by Boston College. Install them with ssc:

STATA
ssc install estout         // tables for regression results (esttab)
ssc install outreg2        // another regression table exporter
ssc install reghdfe        // regression with many fixed effects
ssc describe estout        // read about a package before installing
ssc new                    // what was added recently
adoupdate, update          // update installed community packages

These packages are stored as ado-files (programs written in Stata's own language) in a folder called PLUS. Stata finds them automatically the next time you type the command name. To see where Stata looks:

STATA
sysdir                     // list the system directories
adopath                    // the search order for ado-files
which estout               // where does this command live?

Some packages come from GitHub or an author's website instead. Use net install name, from(URL) for those, and only install code from sources you trust, because ado-files run with your user rights.

Reading and exploring the ado idea

An ado-file is just a text file of commands whose first line starts with program. That is why Stata can be extended with commands that behave exactly like built-in ones. The stand-in below lists which names are "built in" and which come from an add-on, using a tiny lookup table.

Python Stand-in: where does a command live?

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The last line shows a real Stata habit: an unknown command gives error code r(199) ("unrecognized command"). You then know to install the package or fix a typo.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the main difference between Stata/BE, SE and MP?

    The command language is identical; editions differ in size limits and multi-core speed.
  2. 2. Which command installs a community package from SSC?

    ssc install package downloads from the SSC archive.
  3. 3. Why is RAM important in Stata?

    The full dataset is loaded in memory, so free RAM limits what you can analyze.
  4. 4. What does the command update all do?

    update all fetches official updates for your Stata release; adoupdate is for community packages.

Summary

  • BE, SE and MP run the same code; they differ in capacity and speed.
  • Licenses are perpetual, annual, student or institutional; keep your serial number and keys.
  • Memory (RAM) is the practical limit because Stata holds the dataset in memory.
  • update all updates the official software; ssc install and adoupdate handle community packages.
  • Ado-files extend Stata; which and adopath show where commands come from.

Next: Your First Session