• Steve Jones - SSC Editor - Thursday, December 27, 2018 9:07 AM

    We've published things a few times, but not anything in awhile. Our system is fairly simple, but it's probably worth documenting. We do have the stats live at monitor.red-gate.com, where the actual data is replicated from our internal systems to a publicly visible demo version of SQL Monitor.

    Not sure what CosmosDB (formerly DocumentDB) would do to help us. If we removed data, we'd likely archive to another SQL Server database, and we could use distributed views to do that, but the amount of data is really small (GBs), so not sure what we'd get from CosmosDB.

    That being said, I'd like to set up some project with that and experiment.

    Building it all out on SQL Server does present an opportunity to showcase SQL Monitor. But here is why I raised the question about Azure CosmosDB (or more specifically, DocumentDB):
    It seems that the bulk of SQL Server Central content is forum posts, editorials, summary stats, and source code. This can be modeled relationally, if you leverage blob data types. However, it's more naturally structured as documents, mostly html text with meta-data tags. Also, CosmosDB is very scalable in terms of user request throughput (~ $500 / month for 10,000 request units per second), and you can dial the RU/s up or down as needed.

    "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho