Browse by Tags

Blog Post: SharePoint Adventures : Claims, Named Pipes and Kerberos

SQL Server Support Content

I ran into a new Kerberos Scenario that I hadn’t hit before when I was working on the cases related to this blog post . It’s rare that I actually see a case related to the Named Pipes protocol. When I do, it is usually a customer trying to get it ...read more

on 17 May 2013
Blog Post: How It Works: Maximizing Max Degree Of Parallelism (MAXDOP)

SQL Server Support Content

I was working on an index build issue for an 80 CPU system and kept seeing that only 64 CPUs were getting used. I had carefully studied sys . dm_os_spinlock_stats and sys . dm_os_wait_stats along with performance counters, memory usage pattern, and I ...read more

on 27 Sep 2013
Blog Post: SQL Server–Storage Spaces/VHDx and 4K Sector Size

SQL Server Support Content

This blog outlines a new twist to my previous blog outlining issues with 4K sector sizes. SQL Server - New Drives Use 4K Sector Size: http://blogs.msdn.com/b/psssql/archive/2011/01/13/sql-server-new-drives-use-4k-sector-size.aspx In the previous post ...read more

on 15 May 2013
Blog Post: Every time I ‘ATTACH DATABASE’ SQL logs error 1314 for SetFileIoOverlappedRange

SQL Server Support Content

Turns out this is an issue in the SQL Server code and the error is a bit noisy during attach database. When opening the database files, SQL Server calls SetFileIoOverlappedRange (when enabled properly) in order to help improve I/O performance. This ...read more

on 16 Oct 2013
Blog Post: FileNotFoundException with Microsoft.AnalysisServices.Xmla

SQL Server Support Content

I ran across two cases that were hitting the following Exception within SharePoint trying to run the PowerPivot Management Portal. This was located in the SharePoint ULS Log: EXCEPTION: System.IO.FileNotFoundException: Could not load file or assembly ...read more

on 5 Dec 2012
Blog Post: AlwaysOn ERROR: Log backup for database "MyDB" on secondary replica created backup files successfully but could not ensure that a backup point has been committed on the primary.

SQL Server Support Content

This error surprised me when it showed up in the error log so I decided to dig into it a bit more. “Log backup for database "MyDB" on secondary replica created backup files successfully but could not ensure that a backup point has been committed ...read more

on 5 Dec 2012
Blog Post: Don’t change value of that parameter

SQL Server Support Content

Parameter sniffing is a well known among SQL User community. But I have seen variations of this frequently that need a bit creative handling and solution may not that straight forward. One of the variation is that a user changes the value ...read more

on 3 Feb 2013
Blog Post: How Can Reference Counting Be A Leading Memory Scribbler Cause?

SQL Server Support Content

The concept of the memory scribbler comes up quite a bit in support. The term can often be over used but I ran into a specific example that commonly fools people, including support engineers. The random nature and even the resulting ...read more

on 12 Nov 2012
Blog Post: SQL Server: Correlating Timestamps From Various Data Points

SQL Server Support Content

I was looking at data from a customer, in a different time zone (UTC+1) from mine, this week involving SQL Server AlwaysOn (HADRON) and found that lining up the timestamps in the various logs was challenging. Some times are local to the SQL ...read more

on 11 Sep 2012
Blog Post: INF: AlwaysON – The secondary database doesn't come automatically when the primary instance of SQL Server goes down

SQL Server Support Content

In this blog we would discuss about behavior of AlwaysON where the secondary database doesn't come automatically when the primary instance goes down. The secondary database goes into Resolving state. On the failover cluster manager the resource appears ...read more

on 15 Mar 2012
Blog Post: AlwaysON - HADRON Learning Series: HADR_SYNC_COMMIT vs WRITELOG wait

SQL Server Support Content

The distinction between these two wait types is subtle but very helpful in tuning your Always On environment. The committing of a transaction means the log block must be written locally as well as remotely for synchronous replicas. When in ...read more

on 26 Apr 2013
Blog Post: SQLCLR and sp_OA* procedures are not compatible

SQL Server Support Content

We ran into an issue today that is a bug you may need to be aware of because of its behavior. When a SQLCLR procedure calls back into the SQL Server (in proc provider) and executes sp_OA*, during the callback activity, it triggers a bug (currently ...read more

on 20 Dec 2012

Products

Resources

Solutions

Updates

Trials

Related Sites

Training

Certifications

Other resources

Support options

More support

Not an IT pro?

SQL Server KBs and Blogs

Browse by Tags

Blog Post: SharePoint Adventures : Claims, Named Pipes and Kerberos

Blog Post: How It Works: Maximizing Max Degree Of Parallelism (MAXDOP)

Blog Post: SQL Server–Storage Spaces/VHDx and 4K Sector Size

Blog Post: Every time I ‘ATTACH DATABASE’ SQL logs error 1314 for SetFileIoOverlappedRange

Blog Post: FileNotFoundException with Microsoft.AnalysisServices.Xmla

Blog Post: AlwaysOn ERROR: Log backup for database "MyDB" on secondary replica created backup files successfully but could not ensure that a backup point has been committed on the primary.

Blog Post: Don’t change value of that parameter

Blog Post: How Can Reference Counting Be A Leading Memory Scribbler Cause?

Blog Post: SQL Server: Correlating Timestamps From Various Data Points

Blog Post: INF: AlwaysON – The secondary database doesn't come automatically when the primary instance of SQL Server goes down

Blog Post: AlwaysON - HADRON Learning Series: HADR_SYNC_COMMIT vs WRITELOG wait

Blog Post: SQLCLR and sp_OA* procedures are not compatible