Kenneth Igiri

Kenneth Igiri is an Enterprise Architect with almost two decades of experience in Information Technology with nine of those years focused on SQL Server and Oracle databases. His interests include Database Performance, HADR, Cloud Computing, Data Architecture and Enterprise Architecture. Asides from his day job, Kenneth teaches at Youth Church, writes faith-based fiction and works as a Strategy Coach. You can connect with Kenneth via his blog https://kennethigiri.com, LinkedIn or YouTube (@kenigiri).
  • Interests: Strategy, Small Business, Creative Writing
  • Skills: Database Management, Data Management, Leadership, Management, Design Thinking

SQLServerCentral Article

Dealing with Transaction Log Growth

Introduction Relational databases are designed to track changes introduced to a database by data modification language (DML) commands. The fundamental reason for this construct is to ensure that changes are durable and that they can be rolled back reliably. The typical DML command used in SQL are INSERT, UPDATE and DELETE. When INSERT introduces new […]

(5)

You rated this post out of 5. Change rating

2022-06-13 (first published: )

6,792 reads

SQLServerCentral Article

Database Snapshot Use Case: Service Migration

In this article, we show how we used Database Snapshots as a rollbackup plan for a database migration from one data centre to another. Database Snapshots proved to be the best route since we sould not afford the time a backup/restore approach would take.

(1)

You rated this post out of 5. Change rating

2020-08-28 (first published: )

2,546 reads

SQLServerCentral Article

The IDENTITY Column Property

There are a number of ways to generate key values in SQL Server tables including the IDENTITY column property, the NEWID() function and more recently, SEQUENCES. The IDENTITY column property is the earliest of these methods. It was introduced very early in the history of SQL Server and it is arguably the simplest approach. Though old, IDENTITY is still maintained in modern versions of SQL Server and is still relevant for simple use cases.

(7)

You rated this post out of 5. Change rating

2020-05-21

8,356 reads

Blogs

Finding the Last Last Name in SQL: #SQLNewBlogger

By

I wrote a piece on the new SUBSTRING in SQL Server 2025 and got...

SQL Server 2025 GAs Today

By

If you aren’t watching the Ignite keynotes today, then you might have missed the...

Run SQL Server 2025 and SQL Server Management Studio on macOS Tahoe

By

Short version You want to get this running as fast as possible. Do these...

Read the latest Blogs

Forums

Email change does not work

By rjkoala1

I changed my email address in Edit Profile page, but it has no effect...

The case for "Understanding our business" training

By David.Poole

Comments posted to this topic are about the item The case for "Understanding our...

Specifying the Collation

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Specifying the Collation

Visit the forum

Question of the Day

Specifying the Collation

I am dealing with issues on my SQL Server 2022 instance related to collation. I have an instance collation of Latin1_General_CS_AS_KS_WS, but a database collation of Latin1_General_CI_AS. I want to force a few queries to run with a specified collation by using code like this:

DECLARE @c VARCHAR(20) = 'Latin1_General_CI_AS'

SELECT  p.PersonType,
        p.Title,
        p.LastName,
        c.CustomerID,
        c.AccountNumber
 FROM Person.Person AS p
 INNER JOIN Sales.Customer AS c
 ON c.PersonID = p.BusinessEntityID
 COLLATE @c
Will this solve my problem?

See possible answers