Data Modeling Information
Data modeling can be challenging for many reasons. Steve talks about the choices you make in how you store data should be a part of that.
SQL Server 2012 Always On Groups and FCIs Part 4
This is Part 4 of a series on Always On and FCI integration in SQL Server. In this article we will learn how to add the iSCSI disk storage to our SQL Server nodes and build the cluster.
Firebase and Supabase: Key differences you need to know
Firebase is a NoSQL database, while Supabase is a relational database. The type of software you’re constructing determines which database is best for your project.
PASS Data Community Summit registrations are open!
In 2023, connect, share & learn with like-minded peers, speakers, and industry leaders during the full week of data celebrations. Summit happens in person, from November 14th to 17th in Seattle. Check out the blog post to learn more.
Coming Out of the Cloud
Google announced a local version of their cloud databases that companies can install for developers.
Create an Empty Database Using SQL Server Integration Services
Learn how to create a copy of an existing database without any data using Integration Services.
SQL Prompt Safety Net Features for SSMS: SQL History
Mistakes occasionally happen. Occasionally, you make some ill-judged 'refinements' to working code and now just wish you could rewind your tab back in time an hour and forget the whole sorry episode. Now and again, SSMS just conspires against you and crashes unexpectedly, and you lose all your currently open query tabs, some of which you hadn't saved. SQL History offers a useful safety net in the event of any of these unfortunate events.
Use DDL Triggers to Automatically Keep SQL Server Views in Sync
As much as we tell people to use SCHEMABINDING and avoid SELECT *, there is still a wide range of reasons people do not. A well-documented problem with SELECT * in views, specifically, is that the system caches the metadata about the view from the time the view was created, not when the view is queried. If the underlying table later changes, the view doesn't reflect the updated schema without refreshing, altering, or recreating the view. Wouldn't it be great if you could stop worrying about that scenario and have the system automatically keep the metadata in sync?
Moore's Law: Navigating the Pace of Technological Change
Technology has always been a driving force in shaping our world, propelling us forward into new realms of innovation and progress. One of the most famous concepts in technology is Moore's Law, which suggests that the number of transistors on a microchip doubles approximately every two years, leading to exponential increases in computing power. In […]
Data Oriented Cloud Security Mechanisms
This article looks at security mechanisms in the cloud that can help protect your data, with specific examples in AWS.
Blogs
Keeping Redshift System Table History Past 7 Days with S3 Tables
Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...
Updating the Data API Builder
By Steve Jones
I was updating my session for the Data API Builder (DAB) recently, mostly to...
T-SQL Tuesday #202 Invitation: That One SQL Server Outage You’ll Never Forget
I am excited to host T-SQL Tuesday for the first time. I want to...
Forums
Practical Ways to Approach SQL Server Problems and Case Studies
Working with SQL Server can involve more than just writing queries. Understanding database design,...
Measuring Productivity
Comments posted to this topic are about the item Measuring Productivity
Importing Excel files into SQL Server using DuckDB and Python
Comments posted to this topic are about the item Importing Excel files into SQL...
Question of the Day
Tracking All the Queries
I have 3 instances of a brand new long running query that are executing on a SQL Server 2025 instance. Query store is enabled. One of the queries is killed by the administrator, one is cancelled by the user. The other runs to completion. How many rows are in Query Store for this query?
See possible answers