In Redgate Change Control v3.0, you can now commit your database changes to your local Git repository and collaborate with your team by pushing and pulling changes from the remote Git repository. If you’re using branches, you can also create and switch Git branches from within Redgate Change Control.
One of the finest songs of the sixties had the following lines … "Sitting one day by myself, And I'm thinking, "What could be wrong?" When this funny little Hedgehog comes running up to me, And it starts up to sing me this song. Oh, you know all the words, and you sung all the […]
Use native SQL Server backups with Amazon RDS databases to easily import and export data between local server and the AWS cloud.
Today Steve asks about the people that might be critical in your organization.
This tip looks at using artificial intelligence models with SQL Server to predict outcomes.
The challenges of large scale administration can be complex, but the more we share, the more we help others learn and better manage systems.
In this article we look at different examples of creating SQL Server stored procedures.
The latest version of SQL Change Automation now integrates with SQL Clone to let you use a snapshot of your database’s schema as a baseline. This simplifies migration development in complex databases, avoiding problems like invalid objects or circular dependencies, and you can verify migration scripts on a copy of the currently released database.
Read a One-Slide Summary of the Differences Between TDE and Always Encrypted from Brent Ozar.
By Vinay Thakur
Continued thinking about my Journey blog where we have to look back at the...
By SQLPals
PowerShell Remoting for SQL DBAs: WinRM + SSH Guide (Updated 2026) ...
By Steve Jones
We’re coming back to New York, which is exciting for me. I love NYC....
Comments posted to this topic are about the item Identities and Sequences II
Comments posted to this topic are about the item Using PostgreSQL as a NoSQL...
Comments posted to this topic are about the item Is Your Time "Free"?
In thinking about the differences between the identity property and a sequence object, which of these two guarantees that there are consecutive numbers (according to the increment) inserted in a single table?
See possible answers