Les Smith

I am a database developer working with SQL Server and Oracle8i. My focus is on data warehousing, reporting and analysis. The tools I use are Java, Stored Procedures, Visual Basic and commercial applications such as Informatica. I am currently working at an Application Service Provider company in Silicon Valley.

SQLServerCentral Article

Data Warehouse Version Management

In most tables it is enough to have a stored procedure that performs Update Else Insert logic for data managment. However, in some cases we do not want to destroy the old data with an update statement. Instead we want to maintain history up to a certain number of versions. This article presents a method for doing so.

You rated this post out of 5. Change rating

2001-08-27

3,310 reads

Blogs

SWAG Saves the Day

By

PASS Summit East is in one week. I was on the road last week...

Upgrading SQL Server Containers on the Laptop

By

I don’t have SQL Server installed on my laptop. In an effort to keep...

How to Find Expensive Queries in Amazon Redshift

By

Slow-running queries can degrade your Redshift cluster’s performance and lead to increased costs. Identifying...

Read the latest Blogs

Forums

Having Issue deploying a report to an on prem server from PowerBI desktop

By daniel.manke

Using PowerBI Version1.25.9508.3237(January 2026). Installed Microsoft Power BI Desktop (Optimized for Power BI Report...

SQL 2019 instance with AG, across 2 Windows 2016 OS servers - OSin-place upgrade

By millardus

Hi all Can I get some perspective from the community please on performing in-place...

How Long is a Long I/O?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item How Long is a Long...

Visit the forum

Question of the Day

How Long is a Long I/O?

In SQL Server 2025, a long I/O is recorded in the error log with message 833. How long much an I/O request be outstanding before this message is written to the log?

See possible answers