Making Complex Table Changes
The complexity of tables makes modifying them over time a challenge, especially as data sizes grow.
The complexity of tables makes modifying them over time a challenge, especially as data sizes grow.
This week Steve Jones looks at a new idea, rating the security of products publicly to try and shame vendors into more secure coding.
Too many failovers can cause problems, as can those that happen to often. Steve Jones says you need to consider whether you always need to failover in a sitaution.
This article compares SELECT INTO and INSERT INTO under different scenarios, and the best approach preferred.
So often, the unexpected delays in delivering database code are more likely to happen after the developers initiate the release process. The necessary checks and tests can turn up surprises: The handover process can expose deficiencies. With good teamwork, planning and forethought, though, the process can be made almost painless.
As database developers, we may need to rethink the way we store and handle personal names
In this latest T-SQL Tuesday, Rob Farley takes a look at a couple of unexpected aspects of query plans you might observe when using Temporal Tables in SQL Server 2016.
Daniel Calbimonte walks through the steps to creating a SQL Server Reporting Services (SSRS) Report from an Analysis Services Tabular Database.
By DataOnWheels
Thanks to everyone who joined the blog party this month. I noticed three themes...
By Vinay Thakur
This week has training on AI – Cyber security experts – Omar Santos and...
Following on from my previous post on building The Burrito Bot, I want to...
Comments posted to this topic are about the item What's new in R 4.6
Comments posted to this topic are about the item Interesting Changes in R, which...
Comments posted to this topic are about the item PostgreSQL String Functions Part 1
When thinking about the identity property and sequence objects, which of these can generate values before an insert statement is executed?
See possible answers