This continues my series on auditing SQL Server. The fist parts covered discovery and documentation, server level hardware audits and SQL Server engine level audits. This section examines database configuration audits.
2024-09-18
2024-02-21
408 reads
This trigger will work even if you don't have the primary key on any table. Mechanism to configure the primary key in config table has been provided. This can be very helpful to solve the system audit requirements without much efforts.
Disclaimer : Audit Log trigger has performance overhead. It’s meant for table which is not frequently updated, deleted or inserted. Please take precaution when creating the trigger on the table having too many columns.
2019-10-15 (first published: 2019-10-10)
3,094 reads
2018-01-26 (first published: 2018-01-18)
12,319 reads
By SQLPals
Reality (And Limits) of Instant File Initialization for Transaction Logs in SQL Server 2022 ...
By Steve Jones
Last week I spent a few days in Cambridge, UK for the Redgate Company...
By alevyinroc
This is long overdue but life and distractions happened. It’s been a little over...
Comments posted to this topic are about the item Adding and Dropping Columns II
Comments posted to this topic are about the item Leveraging DuckDB for OLAP Workloads:...
Comments posted to this topic are about the item More Documentation is Needed
I have this table in my SQL Server 2022 database:
CREATE TABLE [dbo].[CityList] ( [CityNameID] [int] NOT NULL IDENTITY(1, 1), [CityName] [varchar] (30) , [Country2] [char] (3), [stateprovince2] [char] (2), [Country] [char] (3), [stateprovince] [char] ) ON [PRIMARY] GOI decide to drop the stateprovince2 and country2 columns. What code should I use? See possible answers