Wait Type PREEMPTIVE_COM_COCREATEINSTANCE

Wait statistics, in the context of SQL Server, refer to the amount of time that a query spends waiting to access data in the database. When a client application requests data from the database, the request is placed in a queue and the client application must wait for its turn to access the data. The time that the query spends waiting is called a "wait" and is tracked by SQL Server. This information can be used to identify potential performance bottlenecks and optimize the performance of the database. Wait statistics are commonly used by database administrators to diagnose and troubleshoot performance issues in SQL Server.

What Is PREEMPTIVE_COM_COCREATEINSTANCE?

This wait type shows up when SQL Server needs to step outside its normal routine and talk to something called a COM object. Think of COM (Component Object Model) as a helper that lives outside SQL Server�like a third-party assistant it calls on for special tasks. The �COCREATEINSTANCE� part means SQL Server is asking to create one of these helpers from scratch.

In everyday terms, it�s like SQL Server outsourcing a job to an external service and waiting for it to pick up the phone and get started. This happens in �preemptive� mode, meaning SQL Server pauses its usual work to wait for this outside help to kick in.

Why Does It Happen?

You�ll see this wait type when SQL Server is doing things that need external components�like running certain extended stored procedures, calling CLR (Common Language Runtime) code, or interacting with linked servers that rely on COM. For example, if you�re pulling data from an old-school application or a custom plugin, SQL Server might need to create a COM object to make it happen.

It�s not a bad thing by itself, but if this wait type is piling up, it could mean those external calls are slow or there�s too much back-and-forth, dragging down performance.

How Can You Monitor It?

To figure out if PREEMPTIVE_COM_COCREATEINSTANCE is a speed bump worth worrying about, you can track it using the Historic Waits feature in Database Health Monitor. This tool gives you a clear view of wait times over hours or days, so you can see if this wait is spiking during specific tasks�like a big data import�or if it�s a constant drag. It�s like having a performance detective on your side, pointing out when and where things slow down.

By watching it, you can decide if you need to rethink how often SQL Server leans on those external helpers or if the issue lies with the COM object itself being sluggish.

Wrapping It Up

PREEMPTIVE_COM_COCREATEINSTANCE is just SQL Server�s way of saying it�s waiting on an outside assistant to get going. It�s a normal part of some operations, but if it�s hogging too much time, it�s worth a closer look. Tools like Database Health Monitor make it simple to keep tabs on this wait type and others, helping you keep your database running smoothly.

Want to stay on top of your SQL Server performance? Check out Database Health Monitor�a free tool from Stedman Solutions that tracks wait types and helps you pinpoint bottlenecks with ease. Download it today and see what�s really going on under the hood!

Watch on YouTube

Find out more about our SQL Server Managed Services

Applies to

Related Waits