Packaged-Application Database Nightmares - A Horror Story
The business decides on a packaged application and buys it. After installation, you look at the schema and realize that is is a nightmare. How do you manage this nightmare?
The business decides on a packaged application and buys it. After installation, you look at the schema and realize that is is a nightmare. How do you manage this nightmare?
There's a sale on the price of SQL Server for Linux and Steve wonders if people will move.
In this post, Tim Smith will look at some of the considerations for both data rules and logic to prevent invalid data early in the ETRL process.
Steve likes that idea of auto deleting data, especially with legislation increasing.
With HIPAA and GDPR requiring your careful scrubbing of data for lower environments, random word generation promises to be a huge helper. Read here how to do it.
Microsoft currently offers two built-in methods of running production SQL Server databases in Azure. The first relies on the ability of Infrastructure-as-a-Service (IaaS) Azure virtual machines to host a variety of on-premises workloads, including SQL Server instances. The second one leverages Platform-as-a-Service (PaaS)-based Azure SQL Database. With the introduction of the Azure SQL Managed Instance service, you have a third option, which combines the benefits of its two predecessors.
Based on a real fact, this article demonstrates how a bad use of sp_executesql can lead to unpleasant surprises
We don't mean to introduce security issues, but sometimes we do because we give in to pressure.
One of the most important tools for query tuning is ability to view execution plans. They are even portable; you can send an execution plan to get advice from someone who doesn't have access to the underlying data. Have you even considered that sensitive information might travel along with the plans? Hugo Kornelis explains how execution plans affect data protection.
By Steve Jones
A customer was trying to compare two tables and capture a state as a...
By Zikato
When I'm looking at a query, I bet it's bad if I see... a...
By Steve Jones
This month is a milestone for T-SQL Tuesday. It’s number 200, which doesn’t sound...
Wa:0821-4447-7715 Jl. A. R. Hakim No.2, Mangkukusuman, Kec. Tegal Tim., Kota Tegal, Jawa Tengah...
Wa:0821-4447-7715 Jl. Jend. Sudirman No.49-51, Terban, Kec. Gondokusuman, Kota Yogyakarta, Daerah Istimewa Yogyakarta 55223
Comments posted to this topic are about the item A Quick Second Opinion
On my SQL Server 2025, I want to search the error log from my T-SQL code for potential issues and then inform an administrator. What is the current way to easily query the error log?
See possible answers