How It Works: SQL Server (BCP, Database I/O, Backup/Restore, …) Reports Operating System Error (665, 1450 or 33) when writing to the file – BIG DATA

Suresh and I have blogged about these issues before but this post will put another spin on the information, as it applies to BIG DATA. Previous Blog References http://blogs.msdn.com/b/psssql/archive/2008/07/10/sql-server-reports-operating-system-error-1450-or-1452-or-665-retries.aspx http://blogs.msdn.com/b/psssql/archive/2009/03/04/sparse-file-errors-1450-or-665-due-to-file-fragmentation-fixes-and-workarounds.aspx http://blogs.msdn.com/b/psssql/archive/2009/01/20/how-it-works-sql-server-sparse-files-dbcc-and-snapshot-databases-revisited.aspx I ran into a 665 issue with a customer attempting to BCP data out of a database.  The scenario was that it worked if…

2

Where Did My Availability Group (AG) Go?

I ran into an issue where the AG was no longer present on a specific node of my cluster but I had NOT dropped the AG from another node in the cluster.  (http://blogs.msdn.com/b/psssql/archive/2012/06/13/how-it-works-drop-availability-group-behaviors.aspx)   Note: Use the XEvent files captured in the LOG directory to confirm that a DDL command was not issued. There are…


How It Works: DROP AVAILABILITY GROUP Behaviors

I just learned something new about the DROP AVAILABILITY GROUP command behavior that I didn’t realize.  The comment on TechNet, alludes to how DROP works but we definitely need to update our documentation. Remove an Availability Group (SQL Server) – http://technet.microsoft.com/en-us/library/ff878113(v=sql.110).aspx "When the availability group is online, deleting it from a secondary-replica causes the primary…

2

AlwaysON – HADRON Learning Series: Worker Pool Usage for HADRON Enabled Databases

I am on several e-mail aliases related to Always On databases (reference Availability Group, AG, HADRON) and the question of worker thread usage is a hot topic this week.  I developed some training around this during the beta so I decided to pull out the relevant details and share them with you all.   Hopefully this…

7

How It Works: HealthCheckTimeout Interval Activities

As I wrote my recent blog posts and did more research I found that is would be helpful to highlight the HealthCheckTimeout behavior in more detail. Always On FCI (Failover Cluster Instance) vs Non-FCI Installations Documentation The first thing that I need to point out is the subtle wording difference in Books Online and other…

1

How It Works: Failover Cluster/Availability Group XEL Logging Frequency

I had a great question from my post on sp_server_diagnostics (http://blogs.msdn.com/b/psssql/archive/2012/03/08/sql-server-2012-true-black-box-recorder.aspx).  As ‘luck’ would have it, Bob Ward, was working on some training and had a similar question.  As I investigated I uncovered a few details that can help us all. Connection Scope As soon as the Failover Cluster Instance (FCI) or Availability Group is…

2

AlwaysON – HADRON Learning Series: Automated Failover Behaviors (Denali – Logging History Information, FCI and Default Health Capture, sp_server_diagnostics)

Quite an encompassing title I will agree but the features all work together to build a really nice product.  I had this tucked away during beta and thought it would be helpful to post. SQL Server AlwaysON and "Denali" has undergone a significant upgrade to the way the cluster resource (for an Availability Group or…


How It Works: Return codes from SQLIOSim

I have been asked how to automate SQLIOSim on several occasions.  SQLIOSim is a utility to test SQL Server I/O integrity (not performance) patterns against a system without needing to install SQL Server on the system.  It ships with SQL Server 2008 and SQL Server 2008 R2 and is located in the BINN directory. There…

1

AlwaysON – HADRON Learning Series: Maximum Failovers Within Specified Period

I can’t take the credit for all this content as much of the investigation was done by Curt Mathews (SQL Server Escalation Engineer). We are finding that folks want to test the failover abilities of AlwaysON but after a single failover it no longer seems to work.   This is because of the default, cluster policy…

2

AlwaysON – HADRON Learning Series: – How does AlwaysON Process a Synchronous Commit Request

The behavior of a synchronous commit in AlwaysON is to commit the transaction on the local replica as well as the secondary replica before the transaction is considered complete.    If you  have used database mirroring you may be familiar with the term ‘High Availability’ to describe a similar behavior. A common misperception is that the…

5