If the design of a relational database is wrong, no amount of clever DML SQL will make it work well. Dr. Codd’s Information Principle is that you have, inside the entity tables, the columns that model the attributes of that entity. The columns contain scalar values. Tables that model relationships can have attributes, but they must have references to entities in the schema. You split those attributes at your peril. Joe Celko explains the basics.
There is a new utility to import data from SQL Server on premises or Azure SQL to Azure SQL Data Warehouse (ASDW)
Today Steve Jones talks about the short cuts that developers might take, many of which aren't necessarily helpful.
Slow, unreliable tests prevent teams doing great work, and make continuous delivery impossible. So what can you do to improve your automated tests?
Azure SQL Data Warehouse is Microsoft’s new enterprise-class, elastic petabyte-scale, data warehouse service that can scale according to organizational demands in just few minutes. In this installment, Arshad Ali covers the different ways to load data into SQL Data Warehouse.
This week Steve Jones wants to know what type of really interesting projects you are working on. Is there something you really enjoy and look forward to building?
We all make mistakes, what you do next is what is important.
Aaron Bertrand shows a quick demo that illustrates why you should be very careful about oversizing varchar / nvarchar columns.
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers