DataStax 1.2 on Windows: A guided tour

DataStax 1.2 on Windows: A guided tour

Summary: Getting the DataStax Community distribution of Cassandra up and running on your local PC is a snap. In this gallery, you'll see that for yourself.

TOPICS: Big Data

 |  Image 7 of 19

  • Thumbnail 1
  • Thumbnail 2
  • Thumbnail 3
  • Thumbnail 4
  • Thumbnail 5
  • Thumbnail 6
  • Thumbnail 7
  • Thumbnail 8
  • Thumbnail 9
  • Thumbnail 10
  • Thumbnail 11
  • Thumbnail 12
  • Thumbnail 13
  • Thumbnail 14
  • Thumbnail 15
  • Thumbnail 16
  • Thumbnail 17
  • Thumbnail 18
  • Thumbnail 19
  • Automatic or manual?

    Are you going to be using Cassandra frequently?  If so, have the services run automatically.  But if not, then uncheck the two options shown here.  This way, everything will be installed, but it won't run unless you explicitly start it up.  Once you've made your decision, click the "Next" button.

  • See installer run

    The installer should now run without further necessary interaction.

  • Start the services

    If you elected to have the services run manually, then you will need to launch Windows' Services applet and scroll down through the alphabetical list to the three DataStax services.  One-by-one, click each service and start it.  You can start the service through its context menu or by clicking on the "play" VCR-style button on the toolbar.  Once all three services are running (they should display "Running" in the "Status" column), you're ready to start working.

Topic: Big Data

Andrew Brust

About Andrew Brust

Andrew J. Brust has worked in the software industry for 25 years as a developer, consultant, entrepreneur and CTO, specializing in application development, databases and business intelligence technology.

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Related Stories


1 comment
Log in or register to join the discussion
  • How Do You Keep It All Up-To-Date?

    Having to run a separate GUI installer for every single package sounds like a scalability nightmare. Including your DBMS, Web server, load balancer, memory cache, scripting languages, scripting language add-ons, Web server add-ons, library dependencies ... that could easily mount up to hundreds of separate installers, which means hundreds of separate updates needing to be managed. On a Linux system, keeping it all-to-date involves little more than typing "apt-get update && apt-get upgrade".