Temporary Tables

External Article

Self-maintaining, Contiguous Effective Dates in Temporal Tables

  • Article

'Temporal' tables contain facts that are valid for a period of time. When they are used for financial information they have to be very well constrained to prevent errors getting in and causing incorrect reporting. This makes them more difficult to maintain. Is it possible to have both the stringent constraints and simple CRUD operations? Well, yes. Dwain Camps patiently explains the whole process.

2015-03-26

9,819 reads

External Article

Temporary Tables in SQL Server

  • Article

Temporary tables are used by every DB developer, but they're not likely to be too adventurous with their use, or exploit all their advantages. They can improve your code's performance and maintainability, but can be the source of grief to both developer and DBA if things go wrong and a process grinds away inexorably slowly. We asked Phil Factor for advice, thinking that it would be a simple explanation.

2011-09-22

6,511 reads

Blogs

SQL Server Journey Part 2: Modern Era (2017 – 2026) – AI/Cloud First

By

Following up on my Part 1 baseline, the journey from 2017 onward changed how...

Google Moves Up Post-Quantum Cryptography Timeline

By

In cryptography, the RSA and ECC algorithms which we use primarily for asymmetric cryptography...

The Book of Redgate: No Politics

By

In today’s world, this might mean something different, but in 2010, we had this...

Read the latest Blogs

Forums

Dancing Robot Goes Rogue

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Dancing Robot Goes Rogue

advice as i migrate my winscp based ssis pkg to our prod server

By stan

Hi , i installed winscp on my pc, added it to GAC thru vs...

Identities and Sequences II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Identities and Sequences II

Visit the forum

Question of the Day

Identities and Sequences II

In thinking about the differences between the identity property and a sequence object, which of these two guarantees that there are consecutive numbers (according to the increment) inserted in a single table?

See possible answers