2024-06-12
479 reads
2024-06-12
479 reads
In the previous posts in this series (part 1, part 2, part 3), I described how I have optimized a long-running set of routines by processing databases, tables, and even subsets of tables in parallel. This leads to many separate jobs that all kick off at roughly the same time
2024-06-12
2024-06-10
553 reads
In part 2 of this series, I showed an example implementation of distributing a long-running workload in parallel, in order to finish faster. In reality, though, this involves more than just restoring databases. And I have significant skew to deal with: one database that is many times larger than all the rest and has a higher growth rate.
2024-06-07
Your challenge for this week was to find out who keeps mangling the contents of the AboutMe column in the Stack Overflow database.
2024-06-03
2024-05-08
714 reads
In my previous post, I showed how to borrow a snake draft concept from fantasy football, or a packing technique from the shipping industry, to distribute different portions of a workload to run in parallel.
2024-05-06
I recently had a restore job where I needed to split the work up into multiple parallel processes (which I’ll refer to here as “threads”). I wanted to balance the work so that the duration was something significantly less than the sum of the restore times
2024-05-01
In this article, I will discuss the history and thinking behind several types of logic that are typically associated with writing relational database code.
2024-04-26
Sometimes when you do GROUP BY, the order of the columns does matter. For example, these two SELECT queries produce different results:
2024-04-24
Once upon a time I had a series about some cool stuff in Snowflake:...
By Steve Jones
“Most overnight successes – in fact any significant successes – take at least 5...
Comments posted to this topic are about the item Why Successful SQL Server Backups...
Comments posted to this topic are about the item Adding Bits II
Comments posted to this topic are about the item An Unlimited Token Budget
I have a table, dbo.bittest, where I am testing an application response. This has this structure:
CREATE TABLE [dbo].[BitTest] ( [insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()), [a] [bit] NULL ) ON [PRIMARY] GOMy application runs this code:
INSERT dbo.BitTest
(
insertdate,
a
)
VALUES
(DEFAULT, true)
GO
See possible answers