2016-12-19
941 reads
2016-12-19
941 reads
Too often in the past, High Availability and Disaster Recovery have been marketed as expensive choices for businesses with deep pockets. The truth is that, with careful planning, there are sensible and economic solutions for small businesses that can maintain business continuity when disaster strikes.
2015-01-02
9,346 reads
This article summarizes the factors to consider and provide an overview of various options for HA and DR in cloud based SQL Server deployments.
2014-09-11
7,592 reads
2013-11-12
1,834 reads
2012-05-04
2,794 reads
This white paper discusses how to reduce planned and unplanned downtime, maximize application availability, and provide data protection using SQL Server 2012 AlwaysOn high availability and disaster recovery solutions.
2012-04-27
3,566 reads
2012-03-29
2,256 reads
2011-06-24
2,480 reads
2011-02-22
2,314 reads
Wesley has heard High Availablity touted as all sorts of technological cure-all for busy SysAdmins and DBAs, and now he's taking a stand against it. There are a range of things that High Availability is regularly confused with (either deliberately or innocently), and Wesley's clearing it all up
2011-02-01
4,724 reads
By Steve Jones
Here are the resources for my talk at Day of Data Boston. Slides –...
By Steve Jones
I’ve covered the values in a number of previous posts on the Book of...
By Arun Sirpal
When the evidence names the database, it says so. When it doesn’t, it stops....
Comments posted to this topic are about the item Split Large Queries in Athena...
Comments posted to this topic are about the item Finding Trailing Spaces
I have some data in a SQL Server 2025 database. It looks like this for the dbo.Customer table:
CustomerID CustomerName PreferredName 1 Steve Steve 2 Andy Andy 3 Brian Brian 4 Allan Allan 5 Devin Devin 6 Steve Steve 7 Sally SallyI want to detect which names have a single trailing space. The CustomerName is a varchar() and the PreferredName is a CHAR(). Does this query detect the problem rows?
SELECT
CustomerID,
CustomerName,
PreferredName
FROM Customer
WHERE CustomerName <> RTRIM(CustomerName)
OR PreferredName <> RTRIM(PreferredName); See possible answers