The Mistake
SQL Server 2008 has been delayed and Steve Jones thinks the entire process of building this version has been poorly handled.
2008-01-29
433 reads
SQL Server 2008 has been delayed and Steve Jones thinks the entire process of building this version has been poorly handled.
2008-01-29
433 reads
Ken Henderson passed away this past week. I found out about it from the MVP forums as well as from...
2008-01-29
1,450 reads
If we will get a new version of SQL Server every 3 years, how can we make the process smoother.
2008-01-29
47 reads
If we will get a new version of SQL Server every 3 years, how can we make the process smoother.
2008-01-29
55 reads
If we will get a new version of SQL Server every 3 years, how can we make the process smoother.
2008-01-29
57 reads
Common sense guidelines, removing local administrators and too much money in IT. Steve Jones comments on a few headlines from the week.
2008-01-28
79 reads
Ever worked on a software project where you didn't get all the requirements? One where the functions and features change in midstream? Steve Jones comments on some possibilities on why this happens.
2008-01-28
91 reads
SQL Server 2008 has been delayed and Steve Jones thinks the entire process of building this version has been poorly handled.editor
2008-01-28
39 reads
SQL Server 2008 has been delayed and Steve Jones thinks the entire process of building this version has been poorly handled.
2008-01-28
56 reads
SQL Server 2008 has been delayed and Steve Jones thinks the entire process of building this version has been poorly handled.
2008-01-28
52 reads
By Brian Kelley
If your organization is spending money, then meaningful results are a must. Pen testing...
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...
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