It is not just the speed of SQL Server, it is the inter-dependence that is troubling. It is difficult enough to get funding to pilot a new database or BI project, made worse when it also depends...
The Case to Upgrade to SQL Server 2012Commented on: 3 years ago
(September 22, 2011)
It really does depend on how it ends up being licensed and priced. Most of the features end up only in the Enterprise edition - that gets ridiculously priced, especially when combined with WinServer...
The Microsoft Cloud BI Story, Dateline February 2011Commented on: 4 years ago
(February 12, 2011)
@kromerm - so every 2 years, an "announcement of another CTP feature" - that is progress? 4 months later (Feb2011) - and reporting is still not available. Too Slow.
And a hybrid approach...
Digital Magazine Archives
Browse back issues of SQL Server Pro, from January 2007 through the last issue published in April 2014. Find the back issues here.
My initial goal in writing this series of posts was to outline some of the concerns surrounding Availability Groups (AGs) and SQL Server Agent Jobs – and call out how there is virtually no guidance from Microsoft on this front and then detail some of the pitfalls and options available for tackling this problem domain. I initially expected this series of posts to have between 25 and 30 posts – according to some of the early outlines I created ‘way back when’....More
Throughout this series of posts I’ve taken a somewhat pessimistic view of how SQL Server Agent jobs are managed within most organizations – meaning that most of the code and examples I’ve provided up until this point were based on assumptions about how CHANGE to jobs is managed. That pessimism, to date, has come in two forms:...More
In this series of posts I’ve called out some of the concerns related to SQL Server AlwaysOn Availability Groups and their interaction with SQL Server Agent jobs – both in the form of Batch Jobs (see post #3) and backups....More