How to Increase Query Speed by 3 Orders of Magnitude with no Indexes

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss Content Posted by Stephen Hirsch » How to Increase Query Speed by 3 Orders of...

88 posts, Page 9 of 9

«««5 6 7 8 9

How to Increase Query Speed by 3 Orders of Magnitude with no Indexes

Rate Topic

Display Mode

Topic Options

Author

Message

majorbloodnock

Posted Friday, July 16, 2010 4:59 AM

Ten Centuries

Group: General Forum Members
Last Login: Wednesday, May 01, 2013 9:44 AM
Points: 1,043, Visits: 2,943

boner28 (7/16/2010)

I can't believe I took the time to read this... or that you took the time to write it

I feel the same way about your post. Not the most constructive criticism in the thread.....

Semper in excretia, sumus solum profundum variat

Post #953750

Ron Hooijschuur

Posted Friday, July 16, 2010 11:54 AM

Forum Newbie

Group: General Forum Members
Last Login: Friday, July 16, 2010 1:32 PM
Points: 2, Visits: 10

I too find the title severely misleading. This is certainly not a "how to" guide. The conclusion is lacking also. The business requirement was changed from realtime to snapshot. A good business analyst would have flushed this out before development started.

Communication is always key in any IT project. Combining responsibilities (programmer and analyst) is not necessarily a good thing and may cause Sarbanes-Oxley compliancy issues.

Post #954065

Stephen Hirsch

Posted Friday, July 16, 2010 12:50 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, January 09, 2013 3:53 PM
Points: 127, Visits: 85

People, the title was purposely misleading. It was intended to get you to question your assumptions.

How in the world would combining the roles of analyst and programmer cause Sarbox problems? I worked in the clinical trial world for many years, under 21CFR Part 11, which is much stricter than Sarbox.

Post #954112

Ron Hooijschuur

Posted Friday, July 16, 2010 1:06 PM

Forum Newbie

Group: General Forum Members
Last Login: Friday, July 16, 2010 1:32 PM
Points: 2, Visits: 10

Segregation of duty: Programmers are not allowed access to production. Business Analyst require access to production for systems in scope.

Well, it got my attention alright. The content just didn't live up to the title's promise

Post #954124

Stephen Hirsch

Posted Friday, July 16, 2010 1:30 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, January 09, 2013 3:53 PM
Points: 127, Visits: 85

Ron Hooijschuur (7/16/2010)

Segregation of duty: Programmers are not allowed access to production. Business Analyst require access to production for systems in scope.

Is that from Sarbox directly? If so, then make someone a business analyst/programmer. Problem solved.

Either way, that's idiotic. Sounds like a sure fire way to accurately hit the wrong target.

Post #954146

boner28

Posted Friday, July 16, 2010 9:50 PM

Forum Newbie

Group: General Forum Members
Last Login: Sunday, January 20, 2013 9:52 PM
Points: 2, Visits: 14

Fair point! My comments were not constructive however after being confused for 20 hrs, tired and grumpy, ur article title led me to premature thoughts of sleeping in my own bed. I think you should edit the title and not annotate with descriptions such as genius. Your boss probably asked a thousand questions during spec and that should probably have been in the top five. From reading some of the comments, it's obvious it's been beneficial to some and appreciated by others but it barely exceeds common sense. Now I've slept though, I like the passion u write with and I'm sure you've got a lot more to contribute. Rick

Post #954289

Jeff Moden

Posted Friday, July 16, 2010 10:04 PM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 1:51 PM
Points: 32,906, Visits: 26,789

MikeAngelastro-571287 (7/14/2010)

I think that replies should avoid attacking the author of an article. That is not productive at all. The author took the initiative to share an experience. If you believe the author to be in error, reply with respect and include the logic behind your opinion. If you don't feel this way about it, please refrain from replying.

Man, do I ever agree with that! The author wasn't at fault for anything here. Lighten up folks.

--Jeff Moden

"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Post #954295

Daniel Bowlin

Posted Tuesday, July 20, 2010 6:49 AM

SSCrazy

Group: General Forum Members
Last Login: Today @ 8:49 AM
Points: 2,672, Visits: 2,417

I enjoyed the article. And it just goes to show, pay attention to everything, not just the code.

Post #955505

« Prev Topic | Next Topic »

88 posts, Page 9 of 9

«««5 6 7 8 9

Permissions