Not Just an Upgrade
Choosing to upgrade isn't as simple as many of us would like. Steve has a few thoughts today on the decision to move to a new version of a database server.
2026-03-09
159 reads
Choosing to upgrade isn't as simple as many of us would like. Steve has a few thoughts today on the decision to move to a new version of a database server.
2026-03-09
159 reads
As a SQL Server DBA, the migration of SQL Server from an existing version to the latest version is a usual activity. In today’s cloud-oriented world, many organizations still prefer an on-prem environment; my organization is one of them. There are multiple reasons to keep your data on-prem, like having more privacy and control of the environment. Currently, our major project is to migrate our existing Microsoft SQL Server 2019 to SQL Server 2022. Recently, we completed the POC. Today, let’s discuss the steps of the SQL Server 2022 installation and migration of our databases.
2025-09-24
Steve has a few thoughts after the end of mainstream support for SQL Server 2019.
2025-03-26
1,775 reads
2024-09-09
464 reads
2024-08-26
450 reads
2024-08-12
618 reads
2024-07-10 (first published: 2024-07-08)
222 reads
2024-02-26
419 reads
Is there a reason to upgrade your SQL Server in place instead of building a new instance? Andy Warren has a few thoughts today on why this might be the right choice.
2023-12-20
6,344 reads
2023-10-13
446 reads
By James Serra
(This is the third post in a three-part series on how AI is changing...
Continuing with my takeaways from SQLCon and FabCon Europe in Barcelona, let’s talk about...
By Steve Jones
Next year the PASS Data Community Summit is in DENVER! and London, but Denver...
Comments posted to this topic are about the item Pay for Performance, which is...
Comments posted to this topic are about the item Helping an English Student with...
Comments posted to this topic are about the item Adding Bits I
I have a table, dbo.bittest, where I am testing an application response. This has this structure:
CREATE TABLE [dbo].[BitTest] ( [insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()), [a] [bit] NULL ) ON [PRIMARY] GOMy application runs this code:
INSERT dbo.BitTest
(
insertdate,
a
)
VALUES
(DEFAULT, 'true')
GO
See possible answers