I would suggest that you do NOT reboot SQL Server.

First, take the database to EMERGENCY mode using ALTER DATABASE

ALTER DATABASE dbname SET EMERGENCY;

then, immediately take a COPY_ONLY backup and store...

To my knowledge SQL Audit will capture ad hoc queries, parameterized queries and stored procedures. It just doesn't keep the values that are passed to parameters. This is the same...

The optimizer won't always be able to spot that the indexed view provides all the columns needed for your data. This is especially true if the queries involved are beyond...

In addition to setting the max memory as Gail suggests, I'd want to see what your wait statistics are before and after you add this memory. Further, you want to...

Errors are likely to be in the error log, but there are a number of DMVs that are useful for observing behavior, especially retry rates, etc.

sys.dm_hadr_availability_replica_states

sys.dm_hadr_database_replica_states

sys.dm_tcp_listener_states

You can also gather information...

Rod at work (10/8/2015)

---

Grant Fritchey (10/8/2015)

---

While SQL Server can store XML, it's not great at it. You might want to consider looking at one of the ID/Value databases that's meant...

The problem as you've described it is very unlikely to be solved using queries. The only thing you could look to would be something like SOUNDEX. That will help...

That's right. Encryption of...

In general, look up the INSERT ... SELECT syntax. That's your buddy when dealing with stuff like this. Your current structure, as everyone else has already said, is broken.

I would love to see the execution plan for this query.

I suspect that you're trying to add the columns by referencing the table name when you need to be using...

There will be a way to do this in SQL Server 2016 (and it's already there in Azure SQL Database). Otherwise, no, it's write update statements or look to a...

While SQL Server can store XML, it's not great at it. You might want to consider looking at one of the ID/Value databases that's meant to cope with this type...

I'm not crazy about that configuration. I'd rather see the CPUs available for use instead of a MAXDOP of 1. Just make sure to change the cost threshold for parallelism...

They're both running this query:

(@p0 int,@p1 bigint)DELETE FROM ManifestExportRecord WHERE Id = @p0 AND VersionNumber = @p1

Deadlocks are usually multi-statement issues involving access across multiple resources, not a single...

Not...