July 19, 2003 at 12:00 am
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/sjones/whendoyoupullyourhairout.asp
October 15, 2003 at 1:32 am
Excellent!!
Concise and clear article about how to return the executing statement from the db system!
October 15, 2003 at 5:44 am
quote:
I'm sure that after reading about a few of my "In The Real World" adventures, there are more than a couple of you that are starting to doubt my abilities. I know, I know, I probably would too since it seems like I've had more than my share of disasters.
Good job Steve! In reference to the above comment, it's usually the developers' fault but why do the DBAs always have to prove it's them instead of the other way around?
BTW, I am a developer turned DBA turned developer so I can say these things.
Bryant E. Byrd, MCDBA
Sr. SQL Server DBA/Systems Analyst
Intellithought, Inc.
[font="Tahoma"]Bryant E. Byrd, BSSE MCDBA MCAD[/font]
Business Intelligence Administrator
MSBI Administration Blog
October 15, 2003 at 6:38 am
thanks steve, i know i'm not alone anymore. i too have concern for looking like i know what i'm doing, when i'm stumped. often i feel like i'm the only one without all the answers.
October 15, 2003 at 6:51 am
I had a similar instance where blocks were occurring all over the place. After digging through tons of stored procedure code and VB code, we finally found the answer. A trigger and been place on one of the main tables of the system. This trigger fired on every event. All it was doing was a huge select across several tables, including it's own table (don’t ask why). After further investigation, it was determined the trigger was not needed, someone had just left the code there!!! After removing the unneeded trigger, the database and application hummed very nicely.
October 15, 2003 at 7:41 am
Can you explain why this code did NOT "close the transaction". I see the Begin Trans and Commit, why would this code "hang"?
Thanks,
Thomas LeBlanc MCP
Thomas LeBlanc, MVP Data Platform Consultant
October 15, 2003 at 7:46 am
The first section of code does not have the commit transaction. The second one does.
Excellent article! My problem is I am the lone developer and DBA so if there is a problem I only have my self to blame.
Ross
October 15, 2003 at 10:08 am
Thanks, glad there are a few people who can appreciate my pain.
Steve Jones
http://www.sqlservercentral.com/columnists/sjones
The Best of SQL Server Central.com 2002 - http://www.sqlservercentral.com/bestof/
October 15, 2003 at 10:43 am
What I like about your Real Life stories is that you give the steps you followed. I've printed several of them for my own trouble-shooting reference.
-SQLBill
October 15, 2003 at 1:58 pm
Yeah Steve, I love the way you step through the Analysis process; the scenario you described is virtually identical to ones I've been through...over and over again.
Signature is NULL
October 15, 2003 at 5:44 pm
Nice. Maybe you'll do the dance thing at Pass.
Andy
October 16, 2003 at 9:33 am
Excellent article Steve!!
Carpe diem!
Carpe diem!
October 17, 2003 at 9:46 am
Thanks
Steve Jones
http://www.sqlservercentral.com/columnists/sjones
The Best of SQL Server Central.com 2002 - http://www.sqlservercentral.com/bestof/
October 15, 2004 at 6:10 am
Hi Steve,
Great article! Makes you almost imagine someone is breathing down your neck. However, I hope my new article, Top Ten Features of Enterprise Manager, can change your mind a bit on your comment, "Real DBAs use QA, not that EM pig". EM has it's good points but in the case of your article, QA is the only way to go!
All the best,
Dale
Author: An Introduction to SQL Server 2005 Management Studio
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply