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.

SHARE:
TOPICS: Big Data
1

 |  Image 3 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
  • Download the installer

    The first step to getting DataStax 1.2 running on your PC is to download the Windows installer for it. The installer provides a positively Windows-like experience: there are no manual steps required, no scripts to run, or anything of that sort. Just run the installer and everything you need will be on your local machine.

    To get the installer, head over to http://www.datastax.com/download/community and grab the appropriate installer.  The Windows 7 64-bit installer (which also works on Windows 8) is highlighted here.

  • For your own protection

    If you're running the installer on Windows 8, a screen-width message bar will pop up, making it look as if Windows is preventing the installation.  The solution is easy, though counterintuitive: clik the More Info link, highlighted here.

  • Run anyway

    The More Info screen is actually where the needed manual override option is placed.  Click the "Run anyway" button.

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

Talkback

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".
    ldo17