If you haven’t migrated your workloads to a managed database platform yet, you’re probably still relying on SQL Server Agent for various maintenance and other scheduled tasks. Most of the time, these processes just work. But when it’s time to troubleshoot, it can be cumbersome to get to the root of some problems.
Learn about disaster recovery and high availability options in SQL Server with details on the tradeoffs you make when choosing from Availability Groups, Log Shipping, Database Mirroring, and Replication.
A guest editorial today from Kendra has a few tips for working from home.
This week’s query exercise asked you to find two kinds of locations in the Stack Overflow database.
As a member of the PostgreSQL open-source community, I have been following the recent license change by Redis Labes on March 20, 2024. Redis introduced a dual license model, specifically adding the Redis Source Available License (RSAL), which prevents other vendors from providing Redis as a service without a paid subscription from Redis Labs. The […]
Learn how it works and how to use the DENSE_RANK() function in your code.
Ever wonder all the reasons that we use databases instead of file systems? While we don’t think of it too much anymore, the first reason that databases came into existence was to remove redundancies.
Using a CURSOR is not normally the best way to process through a set of records. Yet when a seasoned programmer moves to writing TSQL for the first time they frequently look for ways to process a sets of records one row at a time. They do this because they are not used to thinking about processing records as a set. In order to process through a TSQL record set a row at a time you can use a cursor. A cursor is a record set that is defined with the DECLARE CURSOR statement. Cursors can be defined as either read-only or updatable. In this article I will introduce you to using cursors to do record level processing one row at a time.
By Zikato
In SQL Server, using the KILL command to terminate a session results in an...
In today’s data-driven world, having the right tools to manage and process large datasets...
By Steve Jones
flichtish – adj. nervously aware how much of your self-image is based on untested...
I have few snapshot transactions , now my admin has informed me that put...
Comments posted to this topic are about the item Kubernetes is Cool, But ...
Comments posted to this topic are about the item Multiple Query Trace Flags
I want to enable two trace flags, 4199 and 4137, for a single query. How should I do this:
-- A
SELECT
a.AddressID
, a.AddressLine1
, a.AddressLine2
, a.City
, a.StateProvinceID
, a.PostalCode
, p.FirstName
, p.LastName
FROM
Person.Address a
INNER JOIN person.Person AS p
ON p.rowguid = a.rowguid
WHERE
City = 'SEATTLE'
AND PostalCode = 98104
OPTION (QUERYTRACEON 4199, 4137);
-- B
SELECT
a.AddressID
, a.AddressLine1
, a.AddressLine2
, a.City
, a.StateProvinceID
, a.PostalCode
, p.FirstName
, p.LastName
FROM
Person.Address a
INNER JOIN person.Person AS p
ON p.rowguid = a.rowguid
WHERE
City = 'SEATTLE'
AND PostalCode = 98104
OPTION (QUERYTRACEON 4199, QUERYTRACEON 4137);
-- C
SELECT
a.AddressID
, a.AddressLine1
, a.AddressLine2
, a.City
, a.StateProvinceID
, a.PostalCode
, p.FirstName
, p.LastName
FROM
Person.Address a
INNER JOIN person.Person AS p
ON p.rowguid = a.rowguid
WHERE
City = 'SEATTLE'
AND PostalCode = 98104
OPTION (QUERYTRACEON 4199), (QUERYTRACEON 4137);
See possible answers