The Madison Solution and the Kilimanjaro Release ExplainedCommented on: 6 years ago
(October 8, 2008)
The "appliance-like" term is significant. IBM also offers support services to make DB2 behave "appliance-like". Perhaps this will lead to vendors, e.g. Netezza, marketing their wares as "Real" Data...
SQL Server Backup Best PracticesCommented on: 6 years ago
(September 30, 2008)
Excellent points. I would add that if it isn't possible to complete daily Full backups of your databases due to their size, take Fulls on the weekend and Differentials on all other days.
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