free geoip Yet Another SQL Server Management Studio Gripe - Jayson's Blog - jaysonKnight.com
jaysonKnight.com
Welcome to my corner of the internet
Jayson's Blog » Yet Another SQL Server Management Studio Gripe
Yet Another SQL Server Management Studio Gripe
I simply cannot believe all the issues I’m finding in SQL Server Management Studio (for other gripes see my SQL Server 2005 category).  The newest one is just plain dumb IMO (unless I’m doing something wrong).  Recently I needed to implement a quick and dirty trigger for a test on one of my SQL Server 2005 databases, so I fired up SSMS expecting there to be a context menu option when you right click a table (ala Enterprise Manager) to create it.  Nope, not there.  Alright fine, do it via raw DML statements in a query window…easy enough.  Execute the statement to create the trigger.  Now where the heck is it in object explorer?  Programmability/Database Triggers?  Not listed.  Server Objects/Triggers?  No way Jose, not there either.  The only way to find it is select * from sysobjects where xtype = ‘TR’, and even then there’s no way to modify it without explicitly dropping it/recreating it via DDL.  Perhaps my installation is mucked up somehow, but triggers are simply nowhere to be found in object explorer.  This is getting ridiculous.
Posted Fri, May 5 2006 4:26 PM by Jayson Knight
Filed under: ,

Comments

Jonas wrote re: Yet Another SQL Server Management Studio Gripe
on Fri, May 5 2006 4:14 PM
Hey, the triggers are in the object explorer under: Database - Tables - Table Name (expand the table node, and there's Columns, Keys, Constraints, Triggers, Indexes, Statistics).

HTH

Jonas
Jayson Knight wrote re: Yet Another SQL Server Management Studio Gripe
on Fri, May 5 2006 4:28 PM
Ah jeez, ok...I officially feel dumb. It's always the little things that trip me up! What are the other 2 trigger folders for then? I'm still getting used to SSMS, majority of my work is still done w/ SQL Server 2000.
Richard wrote re: Yet Another SQL Server Management Studio Gripe
on Sat, May 6 2006 10:41 AM
I'm also getting used to SSMS.  (This easy think is to blame the new software..lol..)

Question:  Have you been able to script out stored procs from SQL 2005 and run them on SQL 2000? (or 2000 -> 2005?)
Bob wrote re: Yet Another SQL Server Management Studio Gripe
on Sun, May 7 2006 9:37 AM
I agree the SQL 2005 tools can be frustrating, but it seems alot of the stuff has been moved to where it *should* be (like import/export data, before you could right click a table and choose this menu option, but then had to choose a table in the wizard anyhow. Now this option is only on the database level which is more intuitive for its behavior). I know this is painful since that doesnt always coiencide with where we are used to it being...
Erik Lane wrote re: Yet Another SQL Server Management Studio Gripe
on Mon, May 8 2006 11:18 AM
I'll just add to the list of people getting frustrated with SQL 2005.  I'm sure its great but man working with SQL 2000 for so long its hard to make the switch.  :-)
Sara wrote re: Yet Another SQL Server Management Studio Gripe
on Mon, May 8 2006 8:20 PM
Another reason I have yet to switch to 2005. 2000 still works just fine for what I do with it. I don't want to change if I don't have to.
petrus wrote re: Yet Another SQL Server Management Studio Gripe
on Thu, May 10 2007 7:47 AM

lol, Thanks for this post. It also took me a while ... and then just googled and found another community server member :)

Jayson Knight wrote re: Yet Another SQL Server Management Studio Gripe
on Thu, May 10 2007 1:40 PM

Ha, what's up Petrus?

petrus wrote re: Yet Another SQL Server Management Studio Gripe
on Fri, May 11 2007 3:14 AM

Thanks Jayson, everything is cool. How you are?

Add a Comment

(optional)  
(optional)
(required)  
Remember Me?

Copyright © :: JaysonKnight.com
External Content © :: Respective Authors

Terms of Service/Privacy Policy