By Design
Just because something works, is it prudent to implement a solution knowing there is a chance this design flaw will be stricken from future revs of SQL Server? It depends.
2017-04-10
77 reads
Just because something works, is it prudent to implement a solution knowing there is a chance this design flaw will be stricken from future revs of SQL Server? It depends.
2017-04-10
77 reads
Microsoft's Customer Experience Improvement Program for SQL Server: once easy to avoid, now hard to ignore, but Rodney Landrum sees an upside.
2017-02-06
1,538 reads
Rodney Landrum gets lost in the fourth dimension, while coding the infinite possible combinations of SQL Server dates and times.
2016-02-01
82 reads
2015-09-14
144 reads
In a guest post, Rodney Landrum ponders the gaps in his DBA experience at the edge of Lake Erie.
2015-03-02
120 reads
Conference travel enhances our minds with more than just SQL. It exposes us to new cultures, people and possibilities.
2015-01-05
119 reads
Rodney Landrum on finding the inspiration you need, somehow and from somewhere, to get yourself out of a tight corner.
2014-09-29
129 reads
2014-04-14
159 reads
When DBAs too often find themselves trading sleep for Megabytes, it's time for a different approach to detection and alerting of disk space problems. So argues Rodney Landrum.
2014-01-20
120 reads
An impromptu hacking session, in response to an inexplicably-changed password, reminds Rodney Landrum of some valuable lessons for every DBA.
2013-08-05
117 reads
By HeyMo0sh
In my experience, FinOps success has never been just about tools or dashboards. It...
By HeyMo0sh
As a DevOps person, I know that to make FinOps successful, you need more...
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
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