Articles

SQLServerCentral Article

Undocumented T-SQL Tricks With Logs

An interesting feature added to SQL Server 7.0 and 2000 is the ability to purge
an error log through a stored procedure or DBCC command. In this article, Brian Knight shows some of the undocumented stored procedures to detect, read and purge an SQL Server error log in T-SQL.

1 (1)

You rated this post out of 5. Change rating

2001-06-27

14,841 reads

External Article

SQL Server 2000: New XML Features Streamline Webcast

With XML support in SQL Server 2000, you can query SQL over HTTP with a URL, bring the data down to the browser, and manipulate it on the client machine. By adding Internet Explorer 5.0 to the mix and using XSL to convert the XML to HTML, you can lighten the load on your database server. Going still one step further, by using Vector Markup Language you can even create drawings on the fly using the data from your SQL queries.

2001-06-26

4,110 reads

Blogs

The Evolution of Data: From Databases to Spark to Lakebases

By

The circle cylinder of life Maybe you’ve noticed all the twenty somethings tight rolling...

Why Microsoft Fabric Signals the Next Wave of Data Strategy

By

In today’s data-driven economy, organizations are no longer asking if they should invest in...

PostgreSQL Timeline: History and Evolution

By

PostgreSQL, often referred to as Postgres, is a powerful, open-source object-relational database system that...

Read the latest Blogs

Forums

How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory

By Chandan Shukla

Comments posted to this topic are about the item How a Legacy Logic Choked...

How to fix transactional replication latency

By coolchaitu

Good Morning All, We are facing replication latency issue. I checked for blocking, long...

Life's Little Frustrations

By Grant Fritchey

Comments posted to this topic are about the item Life's Little Frustrations

Visit the forum

Question of the Day

The Updated Columns List

I have this table in SQL Server 2022:

CREATE TABLE CustomerLarge
  (CustomerID               INT NOT NULL IDENTITY(1, 1) CONSTRAINT CustomerLargePK PRIMARY KEY CLUSTERED
 , CustomerName             VARCHAR(20)
 , CustomerContactFirstName VARCHAR(40)
 , CustomerContactLastName  VARCHAR(40)
 , Address                  VARCHAR(20)
 , Address2                 VARCHAR(20)
 , City                     VARCHAR(20)
 , CountryCode              CHAR(3)
 , Postal                   VARCHAR(20)
)
GO
If I check the columns_updated() function return in a trigger, what is the data returned?

See possible answers