Performance

External Article

Why is My Database Application so Slow?

  • Article

When your application is running slowly, the reflex action is to blame the database queries. It is certainly true that some of the more extravagant delays can be fairly blamed on a missing index or unnecessary locking, but there are other potential villains in the drama, including the network and the application itself. Dan Turner points out that you could save a lot of time and money by working out for sure where the problems lie before diving into the detail.

2017-11-02

7,358 reads

External Article

Investigating the Cause of SQL Server High CPU Load Conditions When They Happen

  • Article

Any DBA who is trying to find the cause of an intermittent problem with a server or database dreams of being able to use a query or procedure take a snap of the relevant variables at the point when the problem occurred. Laerte takes an example of a slow-running query hogging resources to show that you can run queries when a WMI alert is fired, and save the results for later inspection, whenever it happens.

2017-09-20

4,188 reads

Blogs

How to: Regain SysAdmin Access to a SQL Server Instance Without the SA Password

By

Hello, reader! Today, I’m going to walk you through a scenario that many DBAs...

Secure Your SQL Estate: Best Practices for Azure SQL Security

By

The Castle and the Keys Imagine your Azure SQL environment as a sprawling digital...

The Book of Redgate: Meetings

By

I think we might have forgotten this a bit, but on one of the...

Read the latest Blogs

Forums

Visual Studio SSIS Package Showing Up Blank

By DAhmed

Hi all, this is my first time posting on this forum, thank you all...

MySQL 5.6 not writing any logs

By Forum Researcher

We are using MySQL version 5.6 in our Windows Server 2012 R2 environment. We...

How to resolve issue of custom Audit log table containing incorrect data?

By Kevin8

We have created a parent table, child table & Audit log table in SQL...

Visit the forum

Question of the Day

Change Tracking Default Retention

I run this command on my SQL Server 2022 database:

ALTER DATABASE AdventureWorks2017 SET CHANGE_TRACKING = ON;
What is the default data retention period?

See possible answers