Technical Article

Fun with PowerShell Asynchronous

Imagine a candle that is lit and takes 1 hour to burn out. Now imagine one hundred candles. How many hours will it last? That depends. If they are lit simultaneously, it will take 1 hour. That is the basic idea of running in the background or asynchronously. Of course, the 100 candles can execute independently of one another, unlike if you try to run 100 processes on a computer with 2 cores. PowerShell has some ways to manage that, as PowerShell job – which we will see in this article – runspaces – needs to add programmable using .net.

Blogs

The trade-offs associated with low-code solutions

By

Low-code solutions often accelerate development and make tasks accessible to people who can’t or...

Monday Monitor Tips: Looking Back in Time

By

Often we find out about a problem reported by a customer after the incident...

Can You Tell Why a Plan Didn’t Go Parallel?

By

Let’s face it, most of the time, you probably don’t want your SQL Server...

Read the latest Blogs

Forums

Is there a way to determine an Azure Data Factory Trigger's "next run time"?

By Orlando Colamatteo

Many job schedulers (e.g., SQL Agent, Airflow, Azure Logic Apps) can report when a...

The Table Backup

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Table Backup

Dynamic T-SQL Script Parameterization Using Python

By omu

Comments posted to this topic are about the item Dynamic T-SQL Script Parameterization Using...

Visit the forum

Question of the Day

The Table Backup

I run this code in SQL Server 2022. What happens?

BACKUP TABLE beercount TO DISK = 'beercount.bak'
 

See possible answers