SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


A SQL Server Issue? (Database Weekly May 11, 2009)


A SQL Server Issue? (Database Weekly May 11, 2009)

Author
Message
Steve Jones
Steve Jones
SSC Guru
SSC Guru (140K reputation)SSC Guru (140K reputation)SSC Guru (140K reputation)SSC Guru (140K reputation)SSC Guru (140K reputation)SSC Guru (140K reputation)SSC Guru (140K reputation)SSC Guru (140K reputation)

Group: Administrators
Points: 140082 Visits: 19413
Comments posted to this topic are about the item A SQL Server Issue? (Database Weekly May 11, 2009)

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Paul White
Paul White
SSC-Dedicated
SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)

Group: General Forum Members
Points: 33830 Visits: 11359
According to this:

http://sqlcat.com/faq/archive/2009/05/08/windows2008-r2-beta-download-runs-smoothly-now.aspx

...this was nothing to do with SQL Server, CPU spikes, page splitting or GUIDs. The site was simply configured for an expected 20% increase in traffic (and was prepared to handle a 100% increase) but in the event load went up by 500%...!

Given that information, direct from the SQL Server team, it's no wonder things slowed down a bit.

As always, making bold statements before the facts are known is liable to make the participants look a little silly...:-P

Cheers,

Paul



Paul White
SQLPerformance.com
SQLblog.com
@SQL_Kiwi
James Stover
James Stover
Right there with Babe
Right there with Babe (717 reputation)Right there with Babe (717 reputation)Right there with Babe (717 reputation)Right there with Babe (717 reputation)Right there with Babe (717 reputation)Right there with Babe (717 reputation)Right there with Babe (717 reputation)Right there with Babe (717 reputation)

Group: General Forum Members
Points: 717 Visits: 862
Uh oh, the dreaded clustered vs. non-clustered argument. Well, in this specific case, it might have been better to go with the non-clustered option. But it's easy to say that after the fact, isn't it?

To quote from one of my favorite TV shows EVER - "This has all happened before, and it will all happen again."

(Battlestar Galactica 2004, btw)


James Stover, McDBA

Paul White
Paul White
SSC-Dedicated
SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)

Group: General Forum Members
Points: 33830 Visits: 11359
James,

Have you read the article at the link I posted?

Paul



Paul White
SQLPerformance.com
SQLblog.com
@SQL_Kiwi
James Stover
James Stover
Right there with Babe
Right there with Babe (717 reputation)Right there with Babe (717 reputation)Right there with Babe (717 reputation)Right there with Babe (717 reputation)Right there with Babe (717 reputation)Right there with Babe (717 reputation)Right there with Babe (717 reputation)Right there with Babe (717 reputation)

Group: General Forum Members
Points: 717 Visits: 862
Paul White (5/10/2009)
James,

Have you read the article at the link I posted?

Paul


Er, no sorry. Read it just now. OK, so it was a capacity issue unrelated to SQL. Well, that's good news. Unfortunately, thanks to the lightning speed at which mis-information spreads on the internet, this issue will probably be "sticky" for SQL Server for a while.

Regarding the ZDNet blog, I quote:

"Ed Bott is an award-winning technology writer with more than two decades' experience writing for mainstream media outlets and online publications."

Well Ed, the SQLCAT team has posted an official explanation. Where is your official correction on the topic? Award-winning journalists publicly correct their mis-information.


James Stover, McDBA

Paul White
Paul White
SSC-Dedicated
SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)

Group: General Forum Members
Points: 33830 Visits: 11359
Hey James,

Yes it is spreading, but there is some fire-control too:

http://sqlblog.com/blogs/andrew_kelly/archive/2009/05/09/so-the-real-story-is.aspx

It will be interesting to see if Ed does post a correction.

Paul



Paul White
SQLPerformance.com
SQLblog.com
@SQL_Kiwi
Steve Jones
Steve Jones
SSC Guru
SSC Guru (140K reputation)SSC Guru (140K reputation)SSC Guru (140K reputation)SSC Guru (140K reputation)SSC Guru (140K reputation)SSC Guru (140K reputation)SSC Guru (140K reputation)SSC Guru (140K reputation)

Group: Administrators
Points: 140082 Visits: 19413
Paul,

Excellent link and thanks for posting.

I don't think it changes the point of the editorial: Microsoft should ensure the blame, or explanation, is the architecture and planning, not the platform.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Paul Randal
Paul Randal
SSCertifiable
SSCertifiable (7.8K reputation)SSCertifiable (7.8K reputation)SSCertifiable (7.8K reputation)SSCertifiable (7.8K reputation)SSCertifiable (7.8K reputation)SSCertifiable (7.8K reputation)SSCertifiable (7.8K reputation)SSCertifiable (7.8K reputation)

Group: General Forum Members
Points: 7826 Visits: 1719
Yes, it was a capacity planning issue because they hadn't tested the schema for that load. As soon as they rebuilt the clustered index to remove the fragmentation, things sped up. Not a SQL problem, a design and planning problem.

And the CAT team article didn't say anything about what it *wasn't* - only that it was a capacity planning issue. That's a nice catch-all for all kinds of performance problems...

Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
Steve Jones
Steve Jones
SSC Guru
SSC Guru (140K reputation)SSC Guru (140K reputation)SSC Guru (140K reputation)SSC Guru (140K reputation)SSC Guru (140K reputation)SSC Guru (140K reputation)SSC Guru (140K reputation)SSC Guru (140K reputation)

Group: Administrators
Points: 140082 Visits: 19413
I pinged the ZDNet writer. He is looking into it and will likely post an update.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Paul Randal
Paul Randal
SSCertifiable
SSCertifiable (7.8K reputation)SSCertifiable (7.8K reputation)SSCertifiable (7.8K reputation)SSCertifiable (7.8K reputation)SSCertifiable (7.8K reputation)SSCertifiable (7.8K reputation)SSCertifiable (7.8K reputation)SSCertifiable (7.8K reputation)

Group: General Forum Members
Points: 7826 Visits: 1719
And also, if it turns out that what was reported originally was BS, I did caveat my blog post by saying "Now, this is slight conjecture, as I don't know the exact schema, but it's the only thing that explains what's been divulged so far".

I'll be happy to hear a definitive statement that it had nothing to do with the unanticipated load on the schema and lack of frequent defrags.

Thanks

Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search