An In-depth look at memory – SQL Server 2012/2014

I finally had some time on my hands, so thought to try and get around to blogging about the memory architecture of SQL server 2012/2014. The memory architecture for the SQL Server relational database engine was practically overhauled with SQL Server 2012, and most of it has remained the same in SQL 2014. Please note…

7

An interesting issue with Peer to Peer Replication

I recently ran into an interesting issue when setting up Peer 2 Peer Replication across 3 instances. The primary instance was SM-UTSQL, where we configured a Peer-to-Peer publication named "PUBLISH1" on the database "DDS-TRANS". Next, we proceeded to configure Peer-to-Peer topology (right-click on publication, click on "Configure Peer-To-Peer topology"), and added the other 2 instances…

2

Something to watch out for when using IS_MEMBER() in TSQL

I recently worked on an interesting issue with my good friend Igor (@sqlsantos), where we were facing performance issues with a piece of code that used the IS_MEMBER () function. Basically, the IS_MEMBER function is used to find out whether the current user (windows/sql login used for the current session) is a member of the…

8

When using SSL, SQL Failover Cluster Instance fails to start with error 17182

I recently worked on an interesting issue with a SQL Server Failover Cluster Instance (FCI). We were trying to use an SSL certificate on the instance, and we followed these steps: Made sure the certificate was requested according to the requirements defined here. Loaded the certificate into the Personal store of the computer account across…

8

SQL 2012 Availability Group does not come up on one instance

I recently came across this interesting issue with SQL 2012 Always on Availability Groups, wherein after the network and IP were changed, the AG would not come up on one of the instances.   We checked the errorlogs on the server, found the following successful stacks for the failovers that had been attempted for the…

2

SQL Server patch fails with "Could not find any resources appropriate for the specified culture or the neutral culture"

I recently worked on a number of issues where SQL Server Service Pack/patch installation would fail, and we would see this error in the relevant Detail.txt (located in C:Program FilesMicrosoft SQL Server100Setup BootstrapLog<Date time of the installation attempt> for SQL 2008/2008 R2):   2013-04-07 20:14:07 Slp: Package sql_bids_Cpu64: – The path of cached MSI package…

0

How To: Troubleshooting SQL Server I/O bottlenecks

One of the most common reason for server performance issues with respect to SQL Server is the presence of an I/O bottleneck on the system. When I say I/O bottleneck, it can mean issues like slow disks, other processes hogging I/O, out-dated drivers, etc. In this blog, I will seek to outline the approach for…

27

An interesting issue with SQL Server Script upgrade mode

Here’s another common issue that I’ve seen quite a few people run into of late. When you run a patch against SQL Server, the patch installs successfully, but on restart, SQL goes into “script upgrade mode” and you’re unable to connect to it. Upon looking at the errorlog, you see something like this:   2012-08-23…

3

Why the service account format matters for upgrades

  I’ve seen this issue a few times in the past few months, so decided to blog about this. When upgrading from SQL 2005 to SQL 2008/SQL 2008 R2 (or even from SQL 2008 to SQL 2008 R2), you might face an error with the in-place upgrade. Open the setup logs folder (located in C:Program…

0

An in-depth look at SQL Server Memory–Part 3

In part 1 and part 2 of the series, we talked about the memory architecture and the Procedure Cache respectively. In this third and final instalment of the SQL Server Memory series, I will look to focus on troubleshooting SQL Server Memory pressure issues.   Before we start on the troubleshooting part though, we need…

30