What You Need To Know About DR Testing
Practice makes perfect. That’s true of everything, including disaster recovery. If you aren’t already testing your DR plan, you should be - here’s what you need to know to get started.
2017-07-10
678 reads
Disaster Recovery (DR)
2017-01-26
1,227 reads
Why PolyBase matters - Part 2
Part 2, a more in depth look at An alternative approach to disaster recovery and backup strategies using PolyBase.
2015-08-11
2,056 reads
Disaster Recovery and Big Data
Big data applications are not usually considered mission-critical: while they support sales and marketing decisions, they do not significantly affect core operations such as customer accounts, orders, inventory, and shipping. Why, then, are major IT organizations moving quickly to incorporating big data in their disaster recovery plans?
2015-04-29
9,397 reads
Practically Cloudy: SQL Server Disaster Recovery to Microsoft Azure - Backups
In the first in a series on the practicalities of using the Microsoft Azure Platform for the SQL Server professional, Buck Woody shows that, whatever your version of SQL Server, there is a way of storing offsite backups in the cloud.
2014-08-11
9,549 reads
Disaster Recovery Tip #8: Maintain up-to-date contact information
A corollary to Murphy's Law states that disaster is most likely to strike when your senior people are out of the office.
2013-08-01
4,236 reads
Disaster Recovery Tip #6 - Monitor Your Systems
Today's complex systems are too large to be able to rely on any DBA's memory for knowledge of each component, and its configuration options and settings.
2013-07-25
4,301 reads
Disaster Recovery Tip #4 - Learn about partial restores!
Sometimes recovery simply entails rerunning a failed process.
2013-07-19
3,818 reads
Disaster Recovery in the Enterprise – Paying the Price to Avoid Extra Costs
Data Protection and Disaster Recovery (DR) are IT tasks that seldom get the same level of attention as development… until disaster strikes. Only if planning is adequate can an organisation be resilient in the face of unexpected problems. There are several steps that are needed to achieve an adequate DR process and the ability to restore business operations after a disaster.
2013-04-18
3,227 reads
Planning for Disaster
There is a certain paradox in being advised to expect the unexpected, but the DBA must plan and prepare in advance to protect their organisation's data assets in the event of an unexpected crisis, and return them to normal operating conditions. To minimise downtime in such circumstances should be the aim of every effective DBA. To plan for recovery, It pays to have the mindset of a pessimist.
2012-12-14
1,871 reads
Blogs
Retro Data 2025 – Slidedeck
You can find the slides of my session on the €100 DWH in Azure...
The Book of Redgate: We Value Teams
By Steve Jones
This value is something that I still hear today: our best work is done...
Troubleshooting TempDB Log Full Errors When SSMS Won’t Connect
By gbargsley
Have you ever received the dreaded error from SQL Server that the TempDB log...
Forums
Is there a way for SP to know who called it?
Hi everyone I am writing an SP where there is logic inside the SP...
Planning for tomorrow, today - database migrations
Comments posted to this topic are about the item Planning for tomorrow, today -...
Bottlenecks on SQL Server performance
We have a BI-application that connects to input tables on a SQL Server 2022...
Question of the Day
The Tightly Linked View
I try to run this code on SQL Server 2022. All the objects exist in the database.
CREATE OR ALTER VIEW OrderShipping
AS
SELECT cl.CityNameID,
cl.CityName,
o.OrderID,
o.Customer,
o.OrderDate,
o.CustomerID,
o.cityId
FROM dbo.CityList AS cl
INNER JOIN dbo.[Order] AS o ON o.cityId = cl.CityNameID
GO
CREATE OR ALTER FUNCTION GetShipCityForOrder
(
@OrderID INT
)
RETURNS VARCHAR(50)
WITH SCHEMABINDING
AS
BEGIN
DECLARE @city VARCHAR(50);
SELECT @city = os.CityName
FROM dbo.OrderShipping AS os
WHERE os.OrderID = @OrderID;
RETURN @city;
END;
go
What is the result? See possible answers