External Article

Getting Started with HDInsight - Part 2 - Introduction to Azure HDInsight PowerShell

PowerShell is a very popular and powerful feature in the Microsoft stack. It is extensively used for development, deployment and administration across various ecosystems like SQL Server, SharePoint, Azure Cloud and others. PowerShell cmdlets are available for HDInsight as well and in this tip we will take a look at fundamental aspects of Microsoft Azure PowerShell for HDInsight.

External Article

SQL Server Data Aggregation for Data with Different Sampling Rates

In the emerging "Internet of Things", there are multitudes of devices collecting data at differing sampling rates. Integrating this data so the data has a common granularity in time is important to not only allow for accurate analysis and mining, but it will also aid in reducing the amount of data to be stored and processed.
In this tip, we will demonstrate how to use the T-SQL AVG function and GROUP BY clause to transform data collected from two devices sampling at 100Hz and 40Hz to one row per second.

Blogs

Overcoming Imposter Syndrome: A Plan

By

My most recent bout with imposter syndrome was with ISACA’s Digital Trust Ecosystem Framework...

Advice I Like: Celebrate Success

By

“On the way to a grand goal, celebrate the smallest victories as if each...

Programmatically Retrieving MLV Lineage and Refresh Times

By

Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...

Read the latest Blogs

Forums

Increase Deadlock Detection

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Increase Deadlock Detection

A Tool is Better than a Script

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Tool is Better than...

Understanding Deadlock Victim Selection in SQL Server

By john.martin

Comments posted to this topic are about the item Understanding Deadlock Victim Selection in...

Visit the forum

Question of the Day

Increase Deadlock Detection

How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?

See possible answers