Fix SQL Server Commvault Backup Failures After an Upgrade

One of my friend sent an email that backups of a SQL Server 2016 instance are failing suddenly when the backups run through the Commvault backup tool. The error is:

Error Code: [30:325]
Description: Error encountered during backup. Error: [System.IO.FileNotFoundException:Could not load file or assembly 'Microsoft.SqlServer.BatchParserClient, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified. Could not load file or assembly 'Microsoft.SqlServer.BatchParserClient, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.]

In below screenshot, backups status fails with error code [30:325] in Commvault console.

Cause

When logged into SQL Server machine and investigated the logs to identify if any recent changes on SQL instance. In C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\summary.txt shows that SQL Server 2008 R2 was upgraded the previous night to SQL Server 2016. Then the backup starts failing. You can also find installed date in add/remove program features in control panel.

Resolution

Read My Complete Article "Here" 

Join webinar on SQL Server 2016 Always on

Click [HERE} to Join webinar.

SQL Server 2016 - AlwaysOn

An availability group supports a failover environment for a discrete set of user databases, known as availability databases, that fail over together. An availability group supports a set of primary databases and one to eight sets of corresponding secondary databases. SQL Server AlwaysOn Availability Groups were first introduced in 2012 and continue to receive enhancements as each new version of the database is released. This webinar will cover enhancements for AlwaysOn FCI and Availability Groups.  

Microsoft SQL Server 2016 Cumulative update 1 (CU1)

Microsoft just announced Microsoft SQL Server 2016 Cumulative update 1 (CU1)

Microsoft reference: [Click Here]

Ganapathi varma Chekuri

Lead SQL DBA, MCP

Linkedin

How to Change an Analysis Services Instance to Tabular Mode

One of my client accidentally set up an SQL Server Analysis Services in multi-dimensional mode instead of Tabular mode. In this post I will show a procedure to change Analysis tabular mode in SQL Server 2016. 

Analysis Services Modes 

Analysis Services can be installed in one of three server modes: Multidimensional and Data Mining (default), Power Pivot for SharePoint, and Tabular. The server mode of an Analysis Services instance is determined during setup when you choose options for installing the server.

You can check the DeploymentMode property in the msmdsrv.ini file that is included in every Analysis Services instance. The value of this property identifies the server mode. Valid values are 0 (Multidimensional), 1 (SharePoint), or 2 (Tabular).

Although changing DeploymentMode property it is not supported by Microsoft, it works.

How to Change an Analysis Services Instance to Tabular Mode

Read My Complete Article "Here" 

Change the Collation Setting for Clustered SQL Server 2014 Instance

One of our SQL Server 2014 clusters was installed and after the install, my client told me that we are supposed to change the SQL Server collation setting. In this post I will show a procedure to change the collation settings of a clustered SQL Server instance. 

To change the default SQL Server collation you have to rebuild the system databases. Before you rebuild the system databases, review the Microsoft MSDN documentation regarding backup of your system databases and logins.

• https://msdn.microsoft.com/en-in/library/ms190190(v=sql.120).aspx
• https://support.microsoft.com/en-in/kb/918992

When you rebuild the master, model, msdb and tempdb system databases are actually dropped and recreated in their original location.

Change SQL Server Collation Setting for a Clustered SQL Server Instance.

Read My Complete Article "Here" 

Configuring Integration Services in a SQL Server 2016 Cluster

In this post I will show a procedure to configure Integration Services in a SQL Server 2016 Cluster.

Clustering Integration Services is not recommended because the Integration Services service is not a clustered or cluster-aware service, and does not support failover from one cluster node to another. Therefore, in a clustered environment, Integration Services should be installed and started as a stand-alone service on each node in the cluster.

Although the Integration Services service is not a clustered service, you can manually configure the service to operate as a cluster resource after you install Integration Services separately on each node of the cluster.

How to configure Integration Services as a cluster resource

Read My Complete Article "Here" 

Microsoft SQL Server 2016 Service Pack 1 (SP1)

Microsoft just announced Microsoft SQL Server 2016 Service Pack 1 (SP1)

Microsoft reference: [Click Here]

Ganapathi varma Chekuri

Lead SQL DBA, MCP

Linkedin