2023-09-25
521 reads
2023-09-25
521 reads
Do you actively choose which compatibility level makes sense for your SQL Server databases? Or do you just take the defaults? Steve has a few thoughts today on actively managing your system.
2023-06-14
1,911 reads
The database compatibility level ought to provide some protection from database upgrade changes, but do you believe that?
2020-09-21
409 reads
2015-10-19
1,370 reads
Changes the database compatibility level of all databases to the given level.
2013-01-31 (first published: 2013-01-07)
969 reads
Recently, in an attempt to thwart leechers (1990s kids will know), I added some...
Once upon a time I had a series about some cool stuff in Snowflake:...
By Steve Jones
“Most overnight successes – in fact any significant successes – take at least 5...
Comments posted to this topic are about the item Why Successful SQL Server Backups...
Comments posted to this topic are about the item Adding Bits II
Comments posted to this topic are about the item An Unlimited Token Budget
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