Are the posted questions getting worse?

Question

Are the posted questions getting worse?

Viewing 15 posts - 22,426 through 22,440 (of 66,712 total)

You must be logged in to reply to this topic. Login to reply

SQLRNNR SSC Guru Points: 281334 More actions · Answer 1

GSquared (12/14/2010)
Brandie Tarvin (12/14/2010)
Days like this, I wonder why I even talk to you people. All that gutter-talk coming out of your mouths... My mom would wash all your mouths out with soap! 😛
(Where's my halo? Self-righteous doesn't work without my halo, darnit!)
😀
It's okay. You're not talking to us. You're typing at us.
Does that mean your mom's willing to wash my keyboard out with soap?
Or is like the mother with the mute kid, washed his hands out with soap...

My keyboard needs to be washed too!!

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 2

Craig Farrell (12/14/2010)
GilaMonster (12/14/2010)
Brandie Tarvin (12/14/2010)
(Where's my halo? Self-righteous doesn't work without my halo, darnit!)
How long did it take you to forge your own halo, in between the lightning strikes, Gail? And... is that... rust?

I'll have you know that is a divinely gifted mithral/true gold alloy. It does not do something so mundane as 'rust'

:hehe:

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

SQLRNNR SSC Guru Points: 281334 More actions · Answer 3

A Christmas fools joke for the office

http://www.thinkgeek.com/gadgets/electronic/ae83/

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

WayneS SSC Guru Points: 95460 More actions · Answer 4

Stefan Krzywicki (12/14/2010)
Wow. I was having problems with an older query taking too long, so I made what I thought was a little switch to begin making time improvements. I changed
FT
INNER JOIN (SELECT TypeID FROM AllTypes WHERE ParentType = 1) T
ON FT.TypeID = T.TypeID
to
WHERE FT.TypeID IN (SELECT TypeID FROM AllTypes WHERE ParentType = 1)
I thought I'd get a decent improvement, but the query went from 2 hours to 5 minutes! I had no idea it would be that dramatic. Thank you SQL Server Saturday where I first learned that concept.

Hmm, I usually take things from the WHERE clause to JOINS to make them run better. How does this run?:

FT

INNER JOIN AllTypes T

ON FT.TypeID = T.TypeID

AND ParentType = 1

Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes

If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!

Links:
For better assistance in answering your questions
Performance Problems
Common date/time routines
Understanding and Using APPLY Part 1 & Part 2

SQLRNNR SSC Guru Points: 281334 More actions · Answer 5

WayneS (12/14/2010)
Stefan Krzywicki (12/14/2010)
Wow. I was having problems with an older query taking too long, so I made what I thought was a little switch to begin making time improvements. I changed
FT
INNER JOIN (SELECT TypeID FROM AllTypes WHERE ParentType = 1) T
ON FT.TypeID = T.TypeID
to
WHERE FT.TypeID IN (SELECT TypeID FROM AllTypes WHERE ParentType = 1)
I thought I'd get a decent improvement, but the query went from 2 hours to 5 minutes! I had no idea it would be that dramatic. Thank you SQL Server Saturday where I first learned that concept.
Hmm, I usually take things from the WHERE clause to JOINS to make them run better. How does this run?:
FT
INNER JOIN AllTypes T
ON FT.TypeID = T.TypeID
AND ParentType = 1

Inquiring minds want to know.

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

Brandie Tarvin SSC Guru Points: 173068 More actions · Answer 6

CirquedeSQLeil (12/14/2010)
A Christmas fools joke for the office
http://www.thinkgeek.com/gadgets/electronic/ae83/

Wow. That is truly evil. I don't think that would be appreciated at my workplace.

Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

SQLRNNR SSC Guru Points: 281334 More actions · Answer 7

Brandie Tarvin (12/14/2010)
CirquedeSQLeil (12/14/2010)
A Christmas fools joke for the office
http://www.thinkgeek.com/gadgets/electronic/ae83/
Wow. That is truly evil. I don't think that would be appreciated at my workplace.

I got a co-worker with that this morning. He was stumped for about 5 minutes. Rebooted and was still having problems. Buahahaha. He finally found it - and the joke is still great hours later.

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

Sioban Krzywicki One Orange Chip Points: 27770 More actions · Answer 8

WayneS (12/14/2010)
Stefan Krzywicki (12/14/2010)
Wow. I was having problems with an older query taking too long, so I made what I thought was a little switch to begin making time improvements. I changed
FT
INNER JOIN (SELECT TypeID FROM AllTypes WHERE ParentType = 1) T
ON FT.TypeID = T.TypeID
to
WHERE FT.TypeID IN (SELECT TypeID FROM AllTypes WHERE ParentType = 1)
I thought I'd get a decent improvement, but the query went from 2 hours to 5 minutes! I had no idea it would be that dramatic. Thank you SQL Server Saturday where I first learned that concept.
Hmm, I usually take things from the WHERE clause to JOINS to make them run better. How does this run?:
FT
INNER JOIN AllTypes T
ON FT.TypeID = T.TypeID
AND ParentType = 1

That was how I'd had it initially and went to the Subquery join to speed it up.

Unfortunately, it keeps getting slower and slower and I'm not sure why. I used to be able to run a third of a year at a time and it'd take an hour or so. Now it is taking 3 hours for a month.

The performance improvement I mentioned before isn't as great as I'd thought. That first time through was great, now it is taking quite a bit longer.

SQL Server had suggested performance improvements by adding an index to the destination table. I need to check that index for fragmentation. I also need to truncate the log again before it overwhelms the disk.

--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams

GSquared SSC Guru Points: 260824 More actions · Answer 9

Stefan Krzywicki (12/14/2010)
WayneS (12/14/2010)
Stefan Krzywicki (12/14/2010)
Wow. I was having problems with an older query taking too long, so I made what I thought was a little switch to begin making time improvements. I changed
FT
INNER JOIN (SELECT TypeID FROM AllTypes WHERE ParentType = 1) T
ON FT.TypeID = T.TypeID
to
WHERE FT.TypeID IN (SELECT TypeID FROM AllTypes WHERE ParentType = 1)
I thought I'd get a decent improvement, but the query went from 2 hours to 5 minutes! I had no idea it would be that dramatic. Thank you SQL Server Saturday where I first learned that concept.
Hmm, I usually take things from the WHERE clause to JOINS to make them run better. How does this run?:
FT
INNER JOIN AllTypes T
ON FT.TypeID = T.TypeID
AND ParentType = 1
That was how I'd had it initially and went to the Subquery join to speed it up.
Unfortunately, it keeps getting slower and slower and I'm not sure why. I used to be able to run a third of a year at a time and it'd take an hour or so. Now it is taking 3 hours for a month.
The performance improvement I mentioned before isn't as great as I'd thought. That first time through was great, now it is taking quite a bit longer.
SQL Server had suggested performance improvements by adding an index to the destination table. I need to check that index for fragmentation. I also need to truncate the log again before it overwhelms the disk.

Move it to one of the support forums, include the usual DDL and sample data, and we'll see what can be done with it.

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

SQLRNNR SSC Guru Points: 281334 More actions · Answer 10

GSquared (12/14/2010)
Stefan Krzywicki (12/14/2010)
WayneS (12/14/2010)
Stefan Krzywicki (12/14/2010)
Wow. I was having problems with an older query taking too long, so I made what I thought was a little switch to begin making time improvements. I changed
FT
INNER JOIN (SELECT TypeID FROM AllTypes WHERE ParentType = 1) T
ON FT.TypeID = T.TypeID
to
WHERE FT.TypeID IN (SELECT TypeID FROM AllTypes WHERE ParentType = 1)
I thought I'd get a decent improvement, but the query went from 2 hours to 5 minutes! I had no idea it would be that dramatic. Thank you SQL Server Saturday where I first learned that concept.
Hmm, I usually take things from the WHERE clause to JOINS to make them run better. How does this run?:
FT
INNER JOIN AllTypes T
ON FT.TypeID = T.TypeID
AND ParentType = 1
That was how I'd had it initially and went to the Subquery join to speed it up.
Unfortunately, it keeps getting slower and slower and I'm not sure why. I used to be able to run a third of a year at a time and it'd take an hour or so. Now it is taking 3 hours for a month.
The performance improvement I mentioned before isn't as great as I'd thought. That first time through was great, now it is taking quite a bit longer.
SQL Server had suggested performance improvements by adding an index to the destination table. I need to check that index for fragmentation. I also need to truncate the log again before it overwhelms the disk.
Move it to one of the support forums, include the usual DDL and sample data, and we'll see what can be done with it.

I second that notion

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

Jack Corbett SSC Guru Points: 184394 More actions · Answer 11

CirquedeSQLeil (12/14/2010)
GSquared (12/14/2010)
Stefan Krzywicki (12/14/2010)
WayneS (12/14/2010)
Stefan Krzywicki (12/14/2010)
Wow. I was having problems with an older query taking too long, so I made what I thought was a little switch to begin making time improvements. I changed
FT
INNER JOIN (SELECT TypeID FROM AllTypes WHERE ParentType = 1) T
ON FT.TypeID = T.TypeID
to
WHERE FT.TypeID IN (SELECT TypeID FROM AllTypes WHERE ParentType = 1)
I thought I'd get a decent improvement, but the query went from 2 hours to 5 minutes! I had no idea it would be that dramatic. Thank you SQL Server Saturday where I first learned that concept.
Hmm, I usually take things from the WHERE clause to JOINS to make them run better. How does this run?:
FT
INNER JOIN AllTypes T
ON FT.TypeID = T.TypeID
AND ParentType = 1
That was how I'd had it initially and went to the Subquery join to speed it up.
Unfortunately, it keeps getting slower and slower and I'm not sure why. I used to be able to run a third of a year at a time and it'd take an hour or so. Now it is taking 3 hours for a month.
The performance improvement I mentioned before isn't as great as I'd thought. That first time through was great, now it is taking quite a bit longer.
SQL Server had suggested performance improvements by adding an index to the destination table. I need to check that index for fragmentation. I also need to truncate the log again before it overwhelms the disk.
Move it to one of the support forums, include the usual DDL and sample data, and we'll see what can be done with it.
I second that notion

Count this as a third

Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question

SQLRNNR SSC Guru Points: 281334 More actions · Answer 12

Does this frighten anybody else?

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

Sioban Krzywicki One Orange Chip Points: 27770 More actions · Answer 13

GSquared (12/14/2010)
Stefan Krzywicki (12/14/2010)
WayneS (12/14/2010)
Stefan Krzywicki (12/14/2010)
Wow. I was having problems with an older query taking too long, so I made what I thought was a little switch to begin making time improvements. I changed
FT
INNER JOIN (SELECT TypeID FROM AllTypes WHERE ParentType = 1) T
ON FT.TypeID = T.TypeID
to
WHERE FT.TypeID IN (SELECT TypeID FROM AllTypes WHERE ParentType = 1)
I thought I'd get a decent improvement, but the query went from 2 hours to 5 minutes! I had no idea it would be that dramatic. Thank you SQL Server Saturday where I first learned that concept.
Hmm, I usually take things from the WHERE clause to JOINS to make them run better. How does this run?:
FT
INNER JOIN AllTypes T
ON FT.TypeID = T.TypeID
AND ParentType = 1
That was how I'd had it initially and went to the Subquery join to speed it up.
Unfortunately, it keeps getting slower and slower and I'm not sure why. I used to be able to run a third of a year at a time and it'd take an hour or so. Now it is taking 3 hours for a month.
The performance improvement I mentioned before isn't as great as I'd thought. That first time through was great, now it is taking quite a bit longer.
SQL Server had suggested performance improvements by adding an index to the destination table. I need to check that index for fragmentation. I also need to truncate the log again before it overwhelms the disk.
Move it to one of the support forums, include the usual DDL and sample data, and we'll see what can be done with it.

I might if the other things I want to try don't pan out. As a daily query all 4 of these queries still run fine running a few days worth of rollup information in 1 to 3 minutes each and that's before the change I mentioned above. It is when I'm trying to redo older information in bulk that I'm having the problem and noticing the slowdown so it is clearly a size problem in addition to whatever else is going on.

How much sample data would I need to provide?

--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams

GSquared SSC Guru Points: 260824 More actions · Answer 14

CirquedeSQLeil (12/14/2010)
Does this frighten anybody else?

A missing image file? Not sure that "frighten" is the right word for that...

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

Alvin Ramard SSC-Forever Points: 41190 More actions · Answer 15

CirquedeSQLeil (12/14/2010)
Does this frighten anybody else?

All I see is a red x, so, no, it doesn't frighten me. 😛

Alvin Ramard
Memphis PASS Chapter[/url]

All my SSC forum answers come with a money back guarantee. If you didn't like the answer then I'll gladly refund what you paid for it.

For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]