Surface Book
Steve Jones is looking for a new laptop. Perhaps. Read on to see what he wants in a machine.
Steve Jones is looking for a new laptop. Perhaps. Read on to see what he wants in a machine.
Phil factor argues that if you are within the SQL and relational mindset, there is no good technical reason to have to change, since SQLite takes care of all the small stuff and the new breed of NewSQL takes care of the jelly-masses of unstructured data.
Sometimes the stress of interdepartmental friction within organisations can get on top of you, especially between the business and IT when the going gets tough. Simple-Talk's answer is a board game to put it all into perspective. Instead of getting carried away, play the board game instead and reach catharsis.
PowerShell is like any computer language: you must understand the paradigms, the constructs, and the way it is designed to work to get the most value from it. It is no good just translating 'sausage-string' procedural algorithms. To demonstrate how Powersahell should be used as its' creators intended, Laerte Junior shows the difference between PowerShell problem-solving with, and without, PowerShell paradigms.
Failures happen with manual and automated releases, they are a fact of life. Make sure you know how and when to rollback failed deployments
Kendra Little takes a look at the upcoming SQL Server 2016 'Number of Rows Read' feature in action.
Inevitably there comes a time where some backend data cleanup needs to be done. Ben Snaidero shares some best practices to follow when deleting data.
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