Three Mile Island And Your Databases
Grant takes a few lessons for database DR from a nuclear accident in the US.
2022-08-06
141 reads
Grant takes a few lessons for database DR from a nuclear accident in the US.
2022-08-06
141 reads
When a disaster occurs and your staff is working on it, what cadence of updates should your customers expect?
2022-08-01
216 reads
2022-07-08
118 reads
A major outage from Atlassian because of a bad script has Steve thinking about the challenges of recovering from mistakes. When we are making changes to portions of our data and we need to plan for mistakes to occur and ensure we can restore the data.
2022-04-22
227 reads
Continuous backup in Cosmos DB doesn't quite work as Steve would expect. He has a few comments on why it is important you know how your backup and restore system works.
2022-02-21
495 reads
After an outage, how do you respond to the issue in the future? A good review of the incident should be a learning opportunity.
2021-09-29
161 reads
Sometimes just running a backup isn't enough, especially in this era of ransomware. Steve has a few thoughts on backup strategies and recovery skills.
2021-08-09
458 reads
Being prepared for a disaster might mean having a way to collect data when something occurs.
2021-05-12
286 reads
When downtime strikes, we may have to make decisions about which systems to focus our efforts upon. Steve talks about the impact of a disaster on your choices.
2021-01-28
121 reads
Losing your instance might result in the need to get information from what you have. Steve Jones looks at a way to get the proper version and patch, and database list, from what limited resources you might have.
2020-10-27
2,744 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...
Has anyone ever seen this before? I have sysadmin permission on a server. I...
Comments posted to this topic are about the item Switching Schema II
Comments posted to this topic are about the item A Practical Approach to Automating...
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