Gail Shaw's SQL Server Howlers
For the latest in our series of SQL Server Howlers, we asked Gail Shaw which common SQL Server mistakes and misunderstandings lead to tearful DBAs and plaintive cries for help on the forums.
2012-09-10
3,694 reads
For the latest in our series of SQL Server Howlers, we asked Gail Shaw which common SQL Server mistakes and misunderstandings lead to tearful DBAs and plaintive cries for help on the forums.
2012-09-10
3,694 reads
To kick off a series of DBA worst case scenarios, we asked Phil Factor to confess. He came up with a classic: The mistaken belief that a backup WITH CHECKSUM guaranteed a good backup that could be restored, and the ensuing disaster.
2012-02-02
5,280 reads
By Steve Jones
I was listening to the radio the other day and the hosts were discussing...
By Steve Jones
We’re a week late, once again my fault. I was still coming out of...
By Steve Jones
I ran across this article recently (https://www.gatesnotes.com/meet-bill/source-code/reader/microsoft-original-source-code) and it has a great opening piece...
Comments posted to this topic are about the item Learning From Breakage
Comments posted to this topic are about the item Python in Action to Auto-Generate...
Comments posted to this topic are about the item Adding and Dropping Columns I
I have this table in my SQL Server 2022 database:
CREATE TABLE [dbo].[CityList] ( [CityNameID] [int] NOT NULL IDENTITY(1, 1), [CityName] [varchar] (30) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ) ON [PRIMARY] GOI decide to add two new columns for the StateProvince and Country. What code should I use? See possible answers