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,313 reads

Blogs

Audit – Security Compliance Frameworks (Part 1)

By

This blog series on Audit/Compliance/Security, this is first blog where we would discuss about...

Restore SQL Server Database to an OrbStack Container

By

In the previous post, we've built a SQL Server 2025 sandbox in an OrbStack...

Day of Data Baton Rouge Slides and Code

By

Thanks to everyone for attending my talk today at Day of data Baton Rouge...

Read the latest Blogs

Forums

Can You Really Downgrade from Enterprise to Standard and Save Thousands? Here's What Happened

By Pablo Echeverria

Comments posted to this topic are about the item Can You Really Downgrade from...

What is CPU Usage?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item What is CPU Usage?

Limiting Checkpoints

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Limiting Checkpoints

Visit the forum

Question of the Day

Limiting Checkpoints

If I use the -k parameter with a number after it, what does this change in SQL Server?

See possible answers