Here are some quick dmv queries you can run to point at a possible memory shortage issue, keeping in mind that your deadlock issue and memory are unrelated:

SELECT @@SERVERNAME AS...

Hi, this query may get you some of what you are looking for (fill in your db name):

--Redo Queue KB

--Total number of kilobytes of hardened log that currently remain to...

Hi, are you trying to connect to the Report Server instance from your workstation using SSMS, or, are you RDP'ed to the server itself (where the reporting services are running...

Hi, are you running a query similar to this one and still getting the recipients error message?

USE msdb

GO

EXEC sp_send_dbmail @profile_name='DBServerAlerts',

@recipients='some.user@acme.com',

@subject='Test message',

@body='Congrats, Database Mail received by you Successfully.'

Sorry, I...

I have never explored that option before so afraid to comment on. Another thing to note, Microsoft recommends that you use the PHYSICAL_ONLY option for frequent use on production...

Hi, all the SAN migrations I have been a part of usually consisted of (post migration) checking the Sql Server services and access to the instance, databases, and maybe a...

Hi, this is an excellent article to look at regarding why checkdb takes so long. You will notice the size of the database is his #1 item.

https://blogs.msdn.microsoft.com/sqlserverstorageengine/2007/01/24/checkdb-part-7-how-long-will-checkdb-take-to-run/

Hi Mick, according to this article [http://www.sqlskills.com/blogs/glenn/how-to-perform-a-rolling-edition-upgrade-while-using-database-mirroring/] which is one version back from yours (2012), you can pretty much do as you describe; upgrading the secondary instance first without having...

Or, have not done this in a while, in ssms, go the properties of the database on the Primary server, then go to Transaction Log Shipping, and uncheck the "Enable...

Researched this a little and this: [http://borishristov.com/blog/modifying-not-owned-sql-agent-jobs-without-being-a-sysadmin/] looks like the only available option.

The only thing you could do is try and speed up the mirroring process overall. Most of that is dictated by the network speed between the primary and secondary....

Hi Mike, Sql Server allows this, but, as a good practice due to the I/O and disk loads, it is better to schedule your system backups at a different time...

Correct,

The time required for synchronization depends essentially on how far the mirror database was behind the principal database at the start of the session (measured by the number of...

High Safety Mode -

After synchronization finishes, every transaction committed on the principal database is also committed on the mirror server, guaranteeing protection of the data. This is achieved by...

Right, thinking you would perform these steps: 1) Break (remove) log shipping 2) Perform an upgrade to the Primary instance which will upgrade the database 3) Perform the same...