Colleen M. Morrow

Colleen Morrow is a database professional living in Cleveland, OH who has been working with database systems since 1996. For more than 12 years, she was a Database Administrator at a large law firm where she developed an appreciation for auditing, automation, and performance tuning. Since that time she has worked with clients in the healthcare, manufacturing, software, and distribution/freight delivery industries. Colleen is currently a Senior Consultant at Fortified Data.

All authors

All authors

Blogs

Can You See Who Forced a Plan

By

I had an excellent group of people in Gothenburg Sweden when I taught there...

Monday Monitor Tips–Finding CUs for My Instance

By

How can I quickly get a CU patch for a system that’s out of...

Why Data Analysts Love PostgreSQL (and You Will Too!)

By

Data analysis is all about wrangling massive datasets. To do that efficiently, you need...

Read the latest Blogs

Forums

GIT Configuration and Automated Release for Azure Data Factory

By Sucharita Das

Comments posted to this topic are about the item GIT Configuration and Automated Release...

workaround for problems that cant be try caught

By stan

hi a peer of mine recalls an error in an edi app that often...

How to commit transaction log during a large ETL process

By Lord Slaagh

Hello SSC! First, I would like to thank everyone who has responded to my...

Visit the forum

Question of the Day

Trigger Order III

I have created these triggers in SQL Server 2022: 

CREATE TRIGGER triggertest_tri_1 ON dbo.triggertest FOR INSERT
AS
PRINT 'one'
GO
CREATE TRIGGER triggertest_tri_2 ON dbo.triggertest FOR INSERT
AS
PRINT 'two'
GO
I want to be sure that the trigger with "1" runs first. I decide to run this: 
EXEC sp_settriggerorder@triggername = 'triggertest_tri_1', @order = 'first'
What happens?

See possible answers