Blog

StackOverflow, ServerFault, and SuperUser are Q&A sites for IT professionals.  I’ve blogged about why I like ServerFault before, but perhaps one of the coolest reasons for database people is that they make their data public.  Every month, StackOverflow dumps out their data to XML.  You can import the data dump into SQL Server, and the whole thing is less than 10gb as of this writing.

But you haven’t done that because you’re lazy.

You just want to open up SQL Server Management Studio 2008 or Toad for SQL Server and connect to the database.  Alright, you got it:

  • SQL Server: brentozar.dyndns.org (as of this writing, it’s 71.57.120.247 – if the name doesn’t work for you, try the IP)
  • Username: StackOverflow_Reader
  • Password: c0mm0ns
  • Databases you can access: ServerFault, StackOverflow, StackOverflowMeta, SuperUser

The data is not a “live” copy – it’s just the monthly Creative Commons data dump, and the schema is the raw output from Sam Saffron’s data dump tool linked above.  The server is a desktop-class machine, nothing fancy, and it’s using my home internet connection.   (Yes, that’s why I’m posting this halfway through the day on Friday – easing into the load.)  You can get a snapshot of my current desk gear and my servers at Flickr.

If you can’t connect to the SQL Server, there’s probably a firewall blocking port 1433 between your workstation and my lab.  Please don’t leave a note to complain – try accessing it from another location, like from your house instead of your work.

To learn more about the schema and how to query it, check out these articles at SQLServerPedia:

↑ Back to top
  1. Hi Brent,

    I’ve been trying to access your SQL server using both domain name and IP address, but can’t connect neither way. What I get as an error message, can be seen below.

    TITLE: Connect to Server
    ——————————

    Cannot connect to 71.57.120.247.

    ——————————
    ADDITIONAL INFORMATION:

    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)
    ——————————

    I’ve also copied/pasted the credentials, so there could not be any misspellings.

    Thanks for any help.

    • That means there’s a firewall between your place and my place that’s blocking port 1433. Sorry about that, but there’s nothing I can do – other users are connecting just fine. Doh!

  2. Pingback: Weekly Link Post 132 « Rhonda Tipton’s WebLog

  3. Interesting experiment on how you can open up a SQL Server and see if anyone can bust it!!!

    Did you do anything particular to the setup of that PC and SQL installation in preparation?

    Also interesting to see that the performance is actually quite good even over a remote TCP/IP connection and billions of users connecting! (Is your blog that popular yet??)

  4. Thanks for sharing your server!

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

css.php