SQL ConstantCare® Population Report: Fall 2025
In this quarter’s update of our SQL ConstantCare® population report, showing how quickly (or slowly) folks adopt new versions of SQL Server, the data is very similar to last quarter
2025-11-17
In this quarter’s update of our SQL ConstantCare® population report, showing how quickly (or slowly) folks adopt new versions of SQL Server, the data is very similar to last quarter
2025-11-17
2024-11-06
199 reads
In this tip, I will demonstrate how to migrate an existing database schema from SQL Server to PostgreSQL.
2024-03-13
There are a number of ways to run SQL Server for free (or low cost) for development. Read a bit about how to do this.
2024-02-23
6,983 reads
This article shows how to use Python to access data in SQL Server and produce a K-Means analysis with a chart.
2024-01-08
3,177 reads
One of the most effective ways to fully utilize your data is to create an Azure Hyperscale database. The principles of Azure Hyperscale databases have been discussed in this article, including their cost-effectiveness, worldwide accessibility, automatic scaling, and reliable performance.
2023-12-22
2,179 reads
2023-11-10
245 reads
This article will show the basic outline for how Python scripts can access and work with data in SQL Server.
2023-11-06
19,654 reads
Batch execution mode is a new optimization feature in SQL Server. In this Article, we'll explore how Batch execution mode works and how you can use it to get faster query results on Rowstore data.
2023-10-30
4,592 reads
Profiler is a GUI based tool that runs a SQL Server trace to capture the metrics listed above as well additional data. This data can then be used to determine where your SQL Server performance issues are related to your TSQL code. Running a trace without using Profiler is known as a Server Side Trace. You can create and start the trace using TSQL commands instead of having to use the GUI.
2023-09-29
By Steve Jones
I come to Heathrow often. Today is likely somewhere close to 60 trips to...
By Brian Kelley
If your organization is spending money, then meaningful results are a must. Pen testing...
I’m starting a webinar series about SQL Server indexing with the fine folks of...
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers