Part four of this stairway series examines the process of updating the data in an existing table in a load. MVP Andy Leonard talks about the way in which packages can handle changes in a repeatable fashion.
This level introduces keys, constraints, and relationships.
In this second level of the Stairway, Phil looks at where we go to find information about objects, using triggers as the example.
Learn about the very basics of what Integration Services is and how it's used in SQL Server.
An introduction to SQL Server StreamInsight and Complex Event Processing with a focus on Business Intelligence.
Back to the basics: learn how to Create, Read, Update and Delete operations are pivotal for any database application. Plus, you’ll see how to use Stored Procedures to manipulate data on the database side instead of on the application side.
If you have been working with SQL Server long enough, you have probably been involved with a SQL Server 2000 to 2005 upgrade. It was painful for many shops due to the deprecation of some features like DTS and the removal of old-fashioned comma joins with the plus operator. It was worth the pain as […]
Steve has a few thoughts on what is worse than telling your boss about a data breach.
This article by Adam Aspin reviews the Azure Cosmos DB SQL API from the perspective of the relational database developer. More specifically it will show you how to leverage your Structured Query Language skills to exploit the core possibilities of Cosmos DB as a NoSQL document database.
By Vinay Thakur
Following up on my Part 1 baseline, the journey from 2017 onward changed how...
By Brian Kelley
In cryptography, the RSA and ECC algorithms which we use primarily for asymmetric cryptography...
By Steve Jones
In today’s world, this might mean something different, but in 2010, we had this...
Comments posted to this topic are about the item Dancing Robot Goes Rogue
Hi , i installed winscp on my pc, added it to GAC thru vs...
Comments posted to this topic are about the item 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