AlwaysOn encompasses the SQL Server solutions for mission-critical high availability and disaster recovery. Two solutions were included under the AlwaysOn umbrella in SQL Server 2012: Availability Groups and Failover Cluster Instances. Each solution has different characteristics, making them appropriate for different scenarios, and both can be combined in the same deployment.
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.
With companies like Microsoft and Google building data centers in small towns, Steve Jones has some comments about how this might affect IT jobs.
Looking for a way to put images on SSRS reports and allow the business users to change the images every so often? This article explains how to implement this in such a way that you don't have to modify a report when the image is changed.
Lots of developers have embraced Agile development, and Steve Jones thinks it's a good way to build software. However, it's not necessarily as easy as you might think.
Tom Stringer (@SQLife) was working on some HADR testing for a customer to simulate many availability groups and introduce significant load into the system to measure overhead and such. In his quest to do that he was seeing behavior that he couldn’t really explain and so worked with him to uncover what was happening under the covers.
Our next webinar on July 23rd has Steve Jones presenting on some disaster stories with ideas on how you might prevent, or mitigate the effects, of those problem situations.
Understanding thousands of lines of code of an existing database is very time-consuming and tedious, prone to inadvertent oversight of key logic points. We are looking at advanced ways to provide greater insight into your code base while reducing the numerous demands placed on the developer. Please help us by completing this short survey to help us define the requirements.
A table does not so much 'have' a clustered index as a table 'is' a clustered index.
It is very difficult to pinpoint what ails a server, just by looking at a single snapshot of the data, or to spot retrospectively what caused the problem by examining aggregated data for the server, collected over many months. The answer? Baselines.
By Steve Jones
We had an interesting discussion about deployments in databases and how you go forward...
By ChrisJenkins
You could be tolerating limited reporting because there isn’t an off the shelf solution...
A while back I wrote a quick post on setting up key mappings in...
Comments posted to this topic are about the item Lots of FKs
Comments posted to this topic are about the item Real-time On-prem SQL Server Data...
Comments posted to this topic are about the item Can You Let Go of...
In SQL Server 2025, what are the most outgoing and incoming FK references a table can have?
See possible answers