Can't see the triggers that I created in SQL Server Management Studio 2008

Sql ServerSql Server-2008

Sql Server Problem Overview

I created a simple trigger on Albums table. But that trigger is not visible in object explorer in programmability in triggers folder. I refreshed that folder as well as restarted the SSMS but still no luck. However i can see that trigger under that table in triggers folder. Is this a feature or a bug?

I am using SQL Server 2008.

Sql Server Solutions

Solution 1 - Sql Server

The triggers in Programmability is for database triggers (DDL Triggers). You can view the table triggers (DML Triggers) if you expand the table. For example, you are looking for triggers for table "students" Follow: expand "Tables"=> Expand "students"=> Here you will find DML triggers in Triggers Node.

Solution 2 - Sql Server

Here is where the Triggers for a specific table is located:

enter image description here

Solution 3 - Sql Server

If you still can't find it, it is likely because you specified

CREATE TRIGGER X
ON SERVER ALL

Specifying that it is deployed at the server level.

Expand server objects > Triggers

Solution 4 - Sql Server

Collapse the tab of the Database and then refresh(F5) and expand TableName > Triggers> and here are your triggers(That need to be executed first before getting automatically saved.).

Categories
Recommended Sql Server Solutions
Recommended Sql Server-2008 Solutions

Previous Solution:

eclipse not showing Avd manager window and android project

AndroidEclipseAvd

Next Solution:

What's the advantage of load() vs get() in Hibernate?

JavaHibernate

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionTCMView Question on Stackoverflow
Solution 1 - Sql ServerMikael ErikssonView Answer on Stackoverflow
Solution 2 - Sql ServerIsrael MarguliesView Answer on Stackoverflow
Solution 3 - Sql ServerAsherView Answer on Stackoverflow
Solution 4 - Sql ServerRicardo F.View Answer on Stackoverflow