Update: this post is a bit dated, since I am no longer working on the project described, but I am still thinking about turning this into a sample project that may help others that could benefit from putting together their own CMS.
I have been running a public-facing content-managed website for a number of years. It’s purpose has turned out to be more theoretical than practical, due to the fact that most of its planned uses never materialized, even after development was complete (ouch!).
The present problem to be solved is that the existing website is far more complex than is really necessary. It consumes server resources out of proportion to its importance, and requires a level of programmer expertise that is just plain unreasonable under the circumstances. There were good reasons for this when the site was created, but times have changed and what is needed now is a simple, content-managed database query website.
Indexed Views – SQLServerCentral. This post describes an interesting feature that I have never been able to use. Unfortunately, indexed views come with a fairly long list of restrictions and I always seem to run afoul of at least one of them.
Before I migrated to SQL Server 2012, I was using Visual Studio 2010 Premium, which included Database Projects. It was a great feature that, once I figured out how to use it, enabled me to keep track of all my schema changes automatically, and to deploy them to production in …Continue reading →
For the last few weeks, on and off, I have been experimenting with setting up SharePoint 2013 Enterprise in order to explore its Business Intelligence features. Maybe you can just read about it and understand, but I need to try things.