Public database servers

I could not find any vendors/architectures have public database servers.

So there is no good way to go beyond SQLFiddle (of which I wrote before in SQL Fiddle | A tool for easy online testing and sharing of database problems and their solutions and David Rodriguez: a few nice posts on SQL (via: Google+)), that does not provide database access, but allows you to fire SQL statements onto these architectures:

• MySQL 5.6
• Oracle 11g R2
• PostgreSQL 9.6
• PostgreSQL 9.3
• SQLite (WebSQL)
• SQLite (SQL.js)
• MS SQL Server 2017

I get the thing (it is very hard to secure an “over the internet” connection to a database server; do NOT do this: [WayBack] connectivity – Connect to SQL Server over Internet – Database Administrators Stack Exchange), so the alternative is to run locally.

If you run locally, there are plenty of example/demo database, like:

• [WayBack] MySQL :: Employees Sample Database
• [WayBack] SQLite Sample Database And Its Diagram (in PDF format)
• for SQL server
  • [WayBack] How to Download the Stack Overflow Database via BitTorrent – Brent Ozar Unlimited® via [WayBack] Where are the Stack Exchange data dumps? – Meta Stack Exchange
  • The good old [WayBack] Release AdventureWorks sample databases · Microsoft/sql-server-samples · GitHub via [WayBack] Microsoft SQL Server Product Samples: Database – CodePlex Archive
    • Note that in the release, the first link to [WayBack] AdventureWorks-oltp-install-script.zip is correct, but the second one gives you a 404.
    • I find it easiest is to install from script; see [WayBack] sql-server-samples/README.md at master · Microsoft/sql-server-samples · GitHub: Install from a script
      

      1. download AdventureWorks-oltp-install-script.zip and extract the zip file to the C:\Samples\AdventureWorks folder.
      2. Open C:\Samples\AdventureWorks\instawdb.sql in SQL Server Management Studio and follow the instructions at the top of the file.

      In step 2, do not forget to set the query window to SQLCMD syntax. Or just run the script using the [WayBack] sqlcmd Utility | Microsoft Docs (which reminds me I should update SQL Sever: batch files to find instances and sqlcmd.exe/osql.exe)

–jeroen