Migrate a SQL Server Database to a PostgreSQL Database
Learn about various options to migrate an entire SQL Server database to a PostgreSQL database.
Learn about various options to migrate an entire SQL Server database to a PostgreSQL database.
Steve is thinking about technology today, inspired by a developer/architect that asks some philosophical and moral questions of software.
In my previous article (What is Microsoft Fabric All About) I explained what Microsoft Fabric is, how it came about and whether it brings anything new to the data insights domain.
Learn how to get a Failover Cluster Instance set up and configured with Windows and SQL Server. This is part of a series showing how to combine a Failover Cluster Instance of SQL Server with an Always On availability group.
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.
Level 1 of the stairway looks at exactly what the technologies "Always On", "Failover Cluster Instance" (FCI) and "Windows Server Failover Cluster" are. We'll look at each in detail and summarize where in the High Availability stack they sit.
In this new level of the stairway, we examine the storage knowledge you need for an Always On configuration.
In this next level of the Stairway to Always On, we will look at the components required to implement a Windows Server Failover Cluster.
In level 6 of this stairway, we will look deeper into Availability Groups and how to set them up along with a Listener.
In Level 7 of this stairway, we look at combining Availability Groups with FCIs for both HA and DR protection.
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Comments posted to this topic are about the item Spending Time in the Office
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers