PFS corruption after upgrading from SQL Server 2014
I’m seeing reports from a few people of DBCC CHECKDB reporting PFS corruption after an upgrade from SQL Server 2014 to SQL Server 2016 or
I’m seeing reports from a few people of DBCC CHECKDB reporting PFS corruption after an upgrade from SQL Server 2014 to SQL Server 2016 or
[Edit 3/12/2019: it looks like this bug, or a similar one, is also in SQL Server 2016. I’ll post an update once I have it.]
This is a quick post to let you know about a bug that a few people are hitting when running DBCC CHECKDB. The symptoms are
This is a quick blog post to let you know about a bug in SQL Server 2012 SP1 that can cause data loss when performing index maintenance.
For the longest time the guidance around tempdb is that if you shrink it on a live system then it could cause tempdb corruption. A
Over the last few weeks I’ve been investigating a series of customer corruption issues (on one customer’s system) where it appears that the page checksum
After going back and forth with someone with a corrupt master database, I’ve just discovered a bug. And unfortunately it goes back to SQL Server
[Edit 2014: there’s an additional bug in SQL Server 2012/2014 – see this post for details.] More details are in KB article 919142, which was
Back in September I blogged about an old 2005 bug that prevented DBCC CHECKFILEGROUP checking the partitions of an object on the specified filegroup unless
A couple of years ago I blogged about 3rd-party file system filter drivers and how if they're not coded correctly to cope with NTFS alternate
This is an interesting performance bug concerning a broken query optimizer rule in 2008. Thanks to Dan Shargel (Twitter) for sending me info on this
2005 SP3 CU6 contains a fix for a corruption bug that can happen after rebuilding an XML index that contains XML elements greater than 8000
Another quickie today. If you're using Activity Monitor in SQL Server 2008, or Performance Data Collection with the Server Activity system data collection set, then you may
Here's an interesting bug that was just recently fixed, and someone actually hit it today, so it's time to blog it. Bottom line is that
Finally! All those customers out there who are frustrated by not being able to turn on the 'lock pages in memory' option to protect the
Not much to do here in Tokyo while waiting for the Bangkok flight except read and blog, and I've already done enough reading for one
See http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=66ab3dbb-bf3e-4f46-9559-ccc6a4f9dc19 for the download, release notes, etc
Both 2005 SP3 CU2 and 2005 SP2 CU12 contain fixes for two bugs that cause corruption in LOB data. The first bug may happen when
While trawling through the latest 2008 Books Online this morning to answer a question, I noticed a new section that I hadn't seen before, which
Cumulative Update 1 for SQL 2008 RTM contains fixes for two nasty FILESTREAM bugs (among a lot of other bug fixes). The first one concerns
With training and consulting from SQLskills, you’ll be able to solve big problems, elevate your team’s capacity, and take control of your data career.