Day 28 of 31 Days of Disaster Recovery: Recovering SQL if the Tempdb Drive Dies
Welcome to day 28 of my series 31 Days of Disaster Recovery. Today I want to talk about recovering SQL...
2013-02-22 (first published: 2013-02-14)
2,902 reads
Welcome to day 28 of my series 31 Days of Disaster Recovery. Today I want to talk about recovering SQL...
2013-02-22 (first published: 2013-02-14)
2,902 reads
This past weekend was SQL Saturday #198 in Vancouver, B.C. It started off with a leisurely drive up to Vancouver...
2013-02-19
1,259 reads
Today is day 27 of my series 31 Days of Disaster Recovery, and I want to talk about restoring a...
2013-02-12
1,112 reads
My series 31 Days of Disaster recovery has been on hiatus due mostly to illness. I’ve been battling a chest...
2013-02-10
1,305 reads
Welcome back for day 26 of my series 31 Days of Disaster Recovery. Today I want to share a tale...
2013-02-10
1,132 reads
The SQLSoldier World Tour kicks off this next Friday when I head up to Vancouver, in British Columbia, Canada. I...
2013-02-10
1,105 reads
Welcome to day 24 of my 31 Days of Disaster Recovery series. Previously, I’ve talked about several different forms of...
2013-01-31
1,863 reads
It’s day 23 of my 31 Days of Disaster Recovery series, and today’s blog post is inspired from an email...
2013-01-29
1,592 reads
The end of the day is quickly approaching as I finish this blog post. This is day 22 in my...
2013-01-27
1,448 reads
Welcome back for day 21 of my 31 Days of Disaster Recovery series. Today I want to talk about trying...
2013-01-26
1,527 reads
By Steve Jones
I was experimenting with CHOOSE() recently after I was asked a question. In a...
By DesertDBA
I did not expect 27 responses to my T-SQL Tuesday #204 invitation, but it...
Should you adopt an off-the-shelf AI tool, partner with a specialist, build in-house, or...
Wa:082374977784 Jl. Palmerah Barat No.38 A, RT.2/RW.3, Grogol Utara, Kec. Kebayoran Lama, Kota Jakarta...
Wa:082374977784 Jl. Jenderal Sudirman Lt Dasar, RT.1/RW.3, Gelora, Kecamatan Tanah Abang, Kota Jakarta Pusat,...
Has anyone ever seen this before? I have sysadmin permission on a server. I...
I run this query:
SELECT s.name AS schemaname , o.name AS objectname FROM sys.objects o INNER JOIN sys.schemas s ON s.schema_id = o.schema_id WHERE o.name = 'Beer'I get two rows back for the objects, named dbo.beer and etl.beer. Both the tables have identical schemas and are not partitioned. There are 25 rows in dbo.beer and 0 rows in etl.beer. I run this code:
ALTER TABLE dbo.beer switch TO etl.beerWhat happens? See possible answers