By Michael K. Campbell, 02/09/2012
In previous posts we touched upon an overview of what causes corruption and looked at ways to simulate corruption. In this post we’ll talk about more about corruption – in terms ...
By Michael K. Campbell, 02/02/2012
In part two of this article series on high availability, Michael K. Campbell outlines the benefits and negative implications of log shipping as a means for achieving high ...
By Michael K. Campbell, 01/30/2012
In my last post I provided an overview of what SQL Server database corruption is – and how it’s almost always caused by problems at the IO subsystem (or disk) level. However, ...
By Michael K. Campbell, 01/27/2012
When it all comes down to it there are really only two main things that DBAs need to worry about: making data available to the proper people, and making sure it’s inaccessible to ...
By Michael K. Campbell, 01/26/2012
In part 1 of this multi-part series, Michael K. Campbell provides an overview of high availability, and outlines clustering as a solution for achieving high availability with SQL ...
By Michael K. Campbell, 01/05/2012
In this how-to article, Michael K. Campbell provides developers with a solution to eliminate duplicate content and improve SEO and Google page rankings for ISS and ASP.NET sites.
By Michael K. Campbell, 01/02/2012
Until now, my previous two posts have largely just been a review of best practices for making backups redundant – with only a single mention about RESTORE VERIFYONLY’s LOADHISTORY ...
By Michael K. Campbell, 12/23/2011
Following up on my previous post, when it comes to the need to create off-box backups, there are really only two (well, three) main reasons you’d want to do Off-Box Backups: ...
By Michael K. Campbell, 12/22/2011
In this editorial, Michael K. Campbell discusses his thoughts on why he thinks Microsoft Internet Explorer (IE) is losing the browser war against Google Chrome and Mozilla Firefox.
By Michael K. Campbell, 12/14/2011
Although the ADO.NET Entity Framework makes application developers' jobs easier, the code it generates can lead to poorly performing applications. Here is what you need to know ...
By Michael K. Campbell, 12/13/2011
SQL Server’s RESTORE statement is insanely powerful. Not only because of the obvious fact that it can be handy in a disaster (when you have regular backups in place), but because ...
By Michael K. Campbell, 12/01/2011
Michael K. Campbell provides a list of free tools that he discovered in 2011 to help boost productivity and save time for web, Visual Studio, and .NET developers.
By Michael K. Campbell, 11/29/2011
While I like to pride myself on being professional enough to admit when I’m wrong, it turns out that I’m a bit more shallow than I’d like to be. For example, I commonly tell my ...
By Michael K. Campbell, 11/23/2011
Michael K. Campbell also shares his thoughts on the end-user experience (UX) for developers and the upcoming SOPA legislation.
By Michael K. Campbell, 11/17/2011
COPY_ONLY backups were a great addition to SQL Server 2005 (and up). Without them, it was all to easy for DBAs, devs, and SysAdmins to create a ‘backup’ for dev/testing purposes ...
By Michael K. Campbell, 11/03/2011
Microsoft is planning to release its .NET Framework 4.5 as an in-place update. In Michael K. Campbell's commentary, see why he thinks there will be trouble for both system admins ...
By Michael K. Campbell, 10/31/2011
For most reluctant-DBAs there’s a certain degree of mysticism or ‘unknown’ about the SQL Server backups that they get ‘roped’ into managing. Moreover, for the uninitiated, there ...
By Michael K. Campbell, 10/27/2011
Michael K. Campbell describes his experience with Microsoft's SQL Azure in hopes of achieving 100 percent application availability with his distributed solution.
By Michael K. Campbell, 10/25/2011
In my free webcast on Essential Techniques for SQL Server Memory Management, I made a number of references to additional resources that I would make available for anyone bumping ...
By Michael K. Campbell, 10/21/2011
SQL Source Control takes all the pain and potential problems out of implementing version control in SQL Server.