Most people blog to share something they've done, and hopefully with the idea that someone else will learn and benefit from it. Steve Jones is happy to share code, but not everyone seems to be in agreement. In any case, you ought to respect the author's wishes.
In SQL, you can express the logic of what you want to accomplish without spelling out the details of how the database should do it. Nowhere is this more powerful than in constraints. SQL is declarative, and Joe Celko demonstrates, in his introduction to Declarative SQL, how you can write portable code that performs well and executes some complex logic, merely by creating unique constraints.
In the final Database Weekly of 2015, Steve Jones looks at a CIO's column on workplace change.
An alternative read-only routing technique for non-Microsoft clients.
SQL Injection isn't special code. It consists of regular, valid T-SQL that is unexpected by the application. Steve Jones notes that using the principle of least privilege can help to limit the damage from SQL Injection if the application fails to properly check input.
Azure SQL Database provides a number of benefits that leverage resiliency and redundancy built into the underlying cloud infrastructure. You can take advantage of these features in order to perform backup, restore, and failover tasks, which help you recover from human errors, service outages, or even regional disasters. In this article, Marcin Policht provides an overview of the primary capabilities incorporated into Azure SQL Database, in particular focusing on point-in-time restore
This Friday Steve Jones has a poll about which SQL Servers might impress you. Is there a company or installation that you think would really showcase the power and scalability of SQL Server?
A secret project is underway up in Redmond, according to sources not so high up in the development team. A port is partially working for various reasons. Read this exclusive scoop!
Oracle 12.1.0.2 can throw an ORA-01438 when importing an interval partitioned table. In this post, David Fitzjarrell suggests a work-around until Oracle patches the bug.
We all make mistakes, but it's important that we revise our code to correct them over time.
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