Finding SQL Server objects that reference invalid objects
Since many environments haven't committed to using a source control system, identifying mismatched objects can offer a challenge. Tim Smith offers a solution.
Since many environments haven't committed to using a source control system, identifying mismatched objects can offer a challenge. Tim Smith offers a solution.
As a data guy, I always smile when application developers refer to ‘their’ data. If only it were that simple.
How did you fall in into your particular career? Was it because of a product? Andy Warren talks about his career evolution and how often we become trapped by the products we work with.
I inherited a database that was getting large and not performing well. After adding primary keys life got better.
It's Developer Week in Nuremberg July 14-17. There are a couple of great speakers at this event, like Constantin Small and Sascha Dittmann. Register while space is available
NEO4J, the graph database, can be used to provide answers that are very tricky for relational databases, including providing diagrams to show how SQL tables relate to each other, and the shortest chain of relationships between two tables, as David Poole demonstrates
Do we take security too far? Are we creating unnecessary rules for those that need to use the resources we support? Steve Jones talks today about security and how we might want to approach it when handling rights for developers.
In this tip, Sadequl Hussain outlines what's involved in rolling out a SQL Server instance in RDS. In subsequent tips, he will explore what features it offers and what shortcomings it has.
Phil Factor ponders the preponderance of text in current database tools, and asks what happened to our glorious graphical future?
Continuous Delivery is fairly generally understood to be an effective way of tackling the problems of software delivery and deployment by making build, integration and delivery into a routine. Phil Factor explains why he's an enthusiast for databases being full participants in this story, and suggests practical ways of doing so.
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