Process Tracking
It is not always possible to run a process on a set schedule. This article by Steve Jones looks at a technique for ensuring that your processes can run on whenever you need them to without any loss of data.
2001-04-18
4,754 reads
Articles
Tame Those Strings! Part 3 - Using REPLACE
The third part of Steve Jones's series on programming and manipulating strings in T-SQL dealing with REPLACE.
2001-04-18
17,118 reads
Tame Those Strings! Part 4 - Numeric Conversions
The fourth part of Steve Jones's series on programming and manipulating strings in T-SQL dealing with numeric conversions.
2001-04-18
9,512 reads
Blogs
AI Step 1
By Vinay Thakur
As this is an Artificial Intelligence (AI) World, things are changing. We can see that...
Beginner’s Guide: Building a Dockerized Todo App with React, Chakra UI, and Rust for Backend
In a containerized app, React and Chakra UI provide a robust and accessible user...
A New Word: Nachlophobia
By Steve Jones
nachlophobia – n. the fear that your deepest connections with people are ultimately pretty...
Forums
More Funny SELECTs
Comments posted to this topic are about the item More Funny SELECTs
Reducing the Cycle Time
Comments posted to this topic are about the item Reducing the Cycle Time
SQL Server migration using replication
I've set up replication in my SQL 2019 environment in attempt to migrate SQL...
Question of the Day
More Funny SELECTs
What does this code return?
SELECT
( SELECT COUNT (*), MAX(soh.OrderDate) AS latestorder
FROM Sales.SalesOrderHeader AS soh
WHERE
soh.OrderDate > '01/01/2011'
AND soh.OrderDate < '01/01/2012') AS OrdersIn2000
, ( SELECT COUNT (*), MAX(soh.OrderDate) AS latestorder
FROM Sales.SalesOrderHeader AS soh
WHERE
soh.OrderDate > '01/01/2012'
AND soh.OrderDate < '01/01/2013') AS OrdersIn2001
, ( SELECT COUNT (*), MAX(soh.OrderDate) AS latestorder
FROM Sales.SalesOrderHeader AS soh
WHERE
soh.OrderDate > '01/01/2013'
AND soh.OrderDate < '01/01/2014') AS OrdersIn2002;
GO See possible answers